Skip to content
100% left
01Intro
Portrait of Fahad Shakeel.
Fahad Shakeel · Senior Product Manager

Fahad Shakeel

Senior Product Manager. I build software products, mostly web and mobile, and I think about them as systems rather than screens.

I started out writing code and training models before moving into product, which is why I tend to ask what a thing costs to build before I ask how it should look.

I work remotely, usually with small cross-functional teams, and I care most about the part of the job where a vague problem becomes something concrete enough to argue about.

02What I Do

Ambiguity in, direction out.

I take problems that arrive as a vague feeling, something isn't working or someone wants something, and turn them into a thing a team can actually build.

Most of the job is subtraction. There is never a shortage of ideas; there is a shortage of agreement about which one matters this quarter and why. I spend my time narrowing that down until the next step is obvious to everyone in the room.

The rest is translation. Engineering, design, and the people paying for it all describe the same product in different languages. Keeping those descriptions pointed at one outcome is most of what shipping actually requires.

  1. 01

    Discovery

    Finding the real problem before committing anyone to a solution.

  2. 02

    Definition

    Turning a fuzzy ask into scope, sequence and a decision people can argue with.

  3. 03

    Delivery

    Keeping a cross-functional team moving without becoming the bottleneck.

  4. 04

    Measurement

    Deciding what would count as working, before the thing is built.

03Process

Slow is smooth, smooth is fast.

How a product gets from a sentence in a meeting to something people use.

Every stage below exists to kill a bad idea earlier than the next one would. The cost of being wrong rises steeply from left to right, so the work is front-loaded on purpose.

A five-stage product process: Ideation, Requirements, Definition, Build and Launch, where what is learned at launch feeds back into ideation.
  1. 01

    Ideation

    What is actually going on?

    • Frame the problem, not the feature
    • Talk to the people living with it
    • Map who wins and who loses
    • Write the one-line premise
  2. 02

    Requirements

    What must be true?

    • Separate needs from preferences
    • Surface constraints early
    • Name the riskiest assumption
    • Agree what is explicitly out
  3. 03

    Definition

    What are we building?

    • Flows before screens
    • Sequence by dependency and risk
    • Cut to a defensible v1
    • Define done, in writing
  4. 04

    Build

    Is it still the right thing?

    • Short cycles, visible progress
    • Decide fast, revisit cheaply
    • Protect the team from churn
    • Test against the premise
  5. 05

    Launch

    Did it work?

    • Ship to a slice first
    • Instrument before release
    • Watch behaviour, not opinions
    • Feed the result back into 01
05Projects

Built, shipped, learned from.

Independent product case studies.

Each one is a self-initiated exploration built to show product thinking, strategy and execution end to end. They draw on real work, so client specifics are withheld under NDA.

06Contact

Tell me what’s not working.

Fahad
Shakeel

Senior Product Manager