Guides
Strategy

A product strategy framework that isn't just a list of goals

Most documents labeled "product strategy" are a list of goals and a roadmap, which is not a strategy. A real strategy names the core challenge and chooses how to beat it. Richard Rumelt's kernel gives you the skeleton, diagnosis, guiding policy, coherent action, and operators layer on how to sort bets and where to concentrate. Below is the framework, cited, plus the tension between planning it and just finding the one thing that matters.

Why this matters. Founders reach for a product strategy framework when the roadmap has become a wishlist and every stakeholder wants their pet feature. The fix isn't more prioritization; it's a strategy that says what you're not doing.

Ask Gavel, free

No signup for your first answer. See a real cited response before you decide.

The short answer

Rumelt's kernel: the three parts of a real strategy

If your strategy doc doesn't contain all three, it's a goals list. The kernel is the minimum viable strategy.

  1. 1

    Diagnosis

    Name the core challenge honestly. What's actually in the way? Most bad strategy skips this and jumps to aspirations.

  2. 2

    Guiding policy

    The overall approach you'll take to address the diagnosis, the choice that rules some options out.

  3. 3

    Coherent actions

    A set of steps that reinforce each other and follow from the policy, not a scattershot list of unrelated initiatives.

The cited playbook

How operators build product strategy

A quarter of OKRs is not a strategy. Here is how strategists and operators structure the real thing, each step linked to a named source.

  1. 1

    Start with a diagnosis, not a goal

    Good strategy has a kernel: a clear diagnosis of the core challenge, a guiding policy to address it, and coherent actions that carry it out. Skip the diagnosis and you get a wishlist of goals that sounds ambitious and guides nothing.

    Richard Rumelt · Good Strategy Bad Strategy
  2. 2

    Sort your bets into the 4Bs

    Categorize strategic investments into buckets, brilliant basics that keep the core strong, big bets that could change the trajectory, and the maintenance work in between, so the portfolio is deliberate instead of whatever shouted loudest this quarter.

    Anuj Rathi · 4Bs Framework for Product Strategy
  3. 3

    Concentrate on the one constraint

    Strategy is allocating limited resources against unlimited options, so find the single constraint that limits growth and put your coherent actions there. A strategy that tries to improve everything at once improves nothing decisively.

    Alex Hormozi · Identifying and Solving Business Constraints
  4. 4

    Make distribution part of the strategy

    Building is increasingly commoditized, so a product strategy that ignores how you'll reach customers is half a strategy. Treat owned distribution, the audience and channels you control, as a first-class part of the plan, not a go-to-market afterthought.

    Greg Isenberg · Distribution as Moat

Where experts disagree

Where operators disagree: plan the strategy or find the constraint?

Richard Rumelt

treats strategy as deliberate design: diagnose the challenge, set a guiding policy, and orchestrate coherent actions top-down. The work is the thinking, done before the doing.

Alex Hormozi

is wary of elaborate strategy decks. Find the single constraint limiting growth right now, attack it, and let the next constraint reveal itself. Strategy emerges from removing bottlenecks, not from planning.

ChatGPT averages this into 'have a clear strategy and stay agile.' Gavel shows you both stances so you can match the amount of planning to your stage and uncertainty.

FAQ

Product strategy questions, answered

What is a product strategy framework?

It's a structure for deciding how your product wins, not just what it'll build. A strong one, like Rumelt's kernel, forces a diagnosis of the core challenge, a guiding policy, and coherent actions, so the roadmap follows from a real choice instead of a wishlist.

What's the difference between product strategy and a roadmap?

Strategy is the choice of how you'll win and what you'll say no to; the roadmap is the sequence of things you'll build to execute it. A roadmap without a strategy is just a list. Strategy comes first and constrains what earns a place on the roadmap.

What is Rumelt's good strategy kernel?

It's the three inseparable parts of any real strategy: a diagnosis that names the core challenge, a guiding policy that chooses an overall approach, and coherent actions that carry it out. Missing any one of the three is the signature of bad strategy.

Do I need a strategy framework, or should I just focus?

That's the debate. A framework prevents a roadmap from becoming a wishlist; the counter-view says most strategy decks are procrastination and you should just find the one constraint and attack it. Early on, lean toward the constraint; as you scale, the deliberate kernel earns its keep.

Can ChatGPT write my product strategy?

It can produce a strategy-shaped document, but without your real diagnosis, constraint, and distribution it defaults to generic ambitions dressed as strategy. That diagnosis is the context Gavel asks for, then grounds the answer in named operators.

Bring your actual numbers. Get a cited answer you can defend.

Try Gavel free

Keep exploring