| name | product-strategy |
| description | Use when a PM or knowledge worker needs to write a product strategy or product vision on a single page. Triggers on "write our product strategy", "product vision", "where to play how to win", "strategy on a page", "what's our strategy", or turning a pile of goals into a coherent, trade-off-driven strategy grounded in Rumelt/Lafley fundamentals. |
| tier | guided |
| time | 90 min+ |
| inputs | the diagnosis: what's actually in your way |
| outputs | strategy/product-strategy.md |
Product Strategy
A real strategy is not a list of things you want. It's a coherent answer to a hard question: given our situation, where do we play, how do we win, and what are we deliberately NOT doing? This skill produces a one-page strategy that connects vision → diagnosis → bets, with the underlying logic that makes the pieces reinforce each other. If you can't say what you're giving up, you don't have a strategy yet.
Grounded in: Good Strategy Bad Strategy — Richard Rumelt: the kernel: diagnosis → guiding policy → coherent action (no goal-lists masquerading as strategy).
Go deeper (The Product Channel): The Ultimate Guide to Product Strategy
When to use this
- You're asked for "the product strategy" and what you have is a roadmap or a target
- Leadership wants a vision but the diagnosis underneath is missing
- The team is trying to win everywhere and spreading thin
- You need a crisp where-to-play / how-to-win to anchor prioritization and say no
- A new market, competitor, or platform shift forces a rethink
What a real strategy is (and isn't)
- IS: a diagnosis of the situation (the crux/challenge) + a guiding policy (where to play, how to win) + a coherent set of actions that follow from it (Rumelt's kernel)
- IS: a set of choices about where to compete and how to win there (Lafley/Martin)
- ISN'T: a list of goals or OKRs — those are what you want, not how you'll get it
- ISN'T: a roadmap — a sequence of features is execution, not strategy
- ISN'T: "grow 30%" — that's a target. A target without a how is a wish
- ISN'T: vision word-salad — inspiring language with no diagnosis underneath is decoration
- Must make trade-offs explicit: where you play implies where you DON'T. No trade-offs = no strategy.
Before you start (gather these)
Get these, or ask sharp questions until you have them — thin inputs produce a thin strategy:
- The situation: what's true about the market, customer, and competition right now? What changed?
- The company goal it serves: what does product strategy need to deliver for the business?
- The unique advantage: what can we do that rivals can't easily copy? (distribution, data, tech, brand, focus)
- The constraints: team size, runway, platform dependencies, regulatory, time horizon
- The crux: what's the single hardest obstacle between us and the goal? (If unclear, this is the first thing to pin down.)
If the advantage or the crux is vague, stop and interrogate it — a strategy built on "we're just better" or "we'll out-execute" is fiction.
Process
Ask before you write. Strategy starts with a diagnosis, and you cannot diagnose from the outside. Ask 2-4 questions and wait: "What's actually in the way — the honest version?" · "What have you already tried that didn't work?" · "What can you not change: budget, headcount, platform, timing?" · "What would you have to believe for this to be the right bet?" If memory/ and workspace/strategy/ already carry this, skip the questions and open with an explicit Assumptions block so they can correct it in one line.
- Write the diagnosis. Name the situation and the crux — the one critical challenge that, if solved, unlocks the goal. Be specific and uncomfortable. Strip away noise to the essential difficulty.
- Define the vision. Where are we going and why does it matter? The future state if we win. One or two sentences, concrete, not slogan-y. Keep the vision outcome-focused and defer the competitive mechanism to how-to-win — so the vision doesn't duplicate how-to-win.
- Where to play. Which segments, customers, use cases, geographies, channels? Equally important: which ones we're explicitly NOT serving. Narrow is a feature.
- How to win. The differentiated approach in your chosen arena — why you beat the alternatives there. Must tie directly to your unique advantage. "Better UX" isn't a how-to-win unless you can say why you can sustain it and others can't.
- Strategic pillars (3–4 coherent bets). The few big moves that operationalize where/how to win. Each pillar should be defensible on its own AND reinforce the others. More than four and you've lost focus. For each concentration bet, name an explicit decision gate / kill-criterion — e.g. "if metric X doesn't move by N quarters, revisit" — so the bet is reversible, not a blank check.
- Explicit non-goals. State what you're choosing NOT to do, NOT to build, NOT to chase — and why. This is where the trade-offs live and where the strategy earns credibility.
- Surface key risks / what-must-be-true. List the assumptions the strategy rests on — what has to be true for it to work — and what would break it. If a make-or-break assumption is untested, name it and how you'd check it early.
- Check coherence. Do the pieces fit? Diagnosis → vision → where/how → pillars should read as one logic chain. Do the pillars reinforce each other or pull apart? Does how-to-win actually exploit the advantage named in the diagnosis? No non-goal should be the simple restatement/inverse of a pillar — that's a trade-off you didn't actually make. If any link is weak, the strategy is a wish list — go fix it.
Output template
Copy-paste and fill. Keep it to one page — if it doesn't fit, you haven't made enough choices.
# Product Strategy — [Product / Team] — [Date]
## Vision
[Where we're going and why it matters — 1–2 sentences, concrete future state.]
## Success looks like
[The measurable outcome this strategy must produce — metric + threshold + horizon.
e.g. "week-2 retention 38% → 55% within 2 quarters." Not a goal in place of a how —
this is the result the bets below are accountable for.]
## Diagnosis (the challenge)
[The situation right now + the single crux that stands between us and the goal.
What changed? What's the hard truth most people are avoiding?]
## Where we play
[Segments / customers / use cases / channels we focus on — and which we don't.]
## How we win
[Our differentiated approach in that arena, tied to a unique advantage rivals
can't easily copy. Why we beat the alternatives here.]
## Strategic pillars (3–4)
1. [Pillar — the bet and what it operationalizes]
2. [Pillar]
3. [Pillar]
4. [Pillar — optional]
## What we're NOT doing
- [Deliberate non-goal — and the trade-off it represents]
- [Segment / feature / motion we're choosing to skip — and why]
## Why this is coherent (the logic)
[The through-line: how diagnosis → where/how → pillars reinforce each other.
Why these bets, together, are how we win this specific challenge.]
## Key risks
- [What has to be true for this to work — and what would break it]
Avoid (anti-patterns)
- Goals dressed as strategy — a stack of targets/OKRs with no "how." If there's no mechanism, it's not strategy.
- No trade-offs / win-everywhere — every segment, every persona, every use case. Trying to please all = a strategy that defends nothing.
- Roadmap in disguise — a Gantt chart or feature sequence labeled "strategy." Execution ≠ direction.
- Vision word-salad — lofty language ("delight customers everywhere") with no diagnosis or choice underneath.
- Advantage hand-waving — "we'll win on execution / quality / speed" with no reason it's defensible.
- Pillars that don't connect — 4 unrelated initiatives that could each be anyone's. Coherence is the test.
Tips
- The diagnosis is the hardest and most valuable part — spend the most time here. A sharp crux makes the rest fall out.
- If you can't name what you're sacrificing, you haven't chosen. Force a real non-goal.
- "Where to win" is a choice of battlefield; "how to win" is the weapon. You need both.
- Pressure-test each pillar: if a competitor read this, could they copy it tomorrow? If yes, it's not a moat.
- One page, on purpose. The constraint forces the choices that make it a strategy.
- Pair with a roadmap after — the strategy decides the bets; the roadmap sequences them.
