Product Strategy
One-Pager.

Why one page

Strategy that takes 50 slides isn’t strategy — it’s a list. The discipline of one page forces a cascade: each choice constrains the next, and what doesn’t fit gets cut. If your strategy can’t survive a single sheet, the team can’t hold it in their head, and what people can’t hold, they can’t execute.

The 5-question cascade

Roger Martin’s Playing to Win framework asks five questions, in order. Each answer constrains the next. The cascade is the strategy — not the bullet points underneath.

Block 1 — Winning Aspiration

Not a vision. Not a tagline. A specific picture of what changes in the world if you succeed. The aspiration is forward-looking and customer-shaped, not company-shaped. “Be the leader in X” is not an aspiration — it’s a wish.

Test: Does it describe a different reality for the customer, not a different reality for you?

Example: “Every product team at a 20–200 person SaaS company makes prioritization decisions with evidence, not opinion. The phrase ‘the loudest customer wins’ disappears from product orgs.”

Block 2 — Where to Play

The harder choice in this block is what’s OUT. Most strategies fail here because the team refuses to declare anything off-limits. Geography, segment, channel, vertical, customer-of-customer (B2B2C), price band — each axis demands a choice.

Example — what’s IN: Series A–C SaaS companies, English-speaking markets, $5M–$50M ARR, product-led, 1–5 PMs, AI-native buyers.

Example — what’s OUT: Enterprise (1000+ employees), agencies, services firms, sub-$1M ARR pre-PMF teams, non-English. We will lose deals in these segments. That is the choice.

Block 3 — How to Win

Your unique value proposition — phrased as the one thing competitors will find hardest to copy. Two valid generic choices: cost leadership or differentiation. Most product companies live in differentiation, but few do the work to name what specifically they differentiate on.

Example: “We win because we’re the only product intelligence platform that lives where modern PMs work — inside their AI clients (Claude, Cursor, ChatGPT) via MCP. Competitors built dashboards; we built a brain. Replicating MCP-first architecture requires rebuilding their data layer; they won’t.”

Block 4 — Capabilities

List the 3–5 capabilities required to deliver How to Win. For each, mark build / partner / buy / gap. A capability gap is not a failure — it’s the next quarter’s hiring plan.

• Multi-channel signal ingestion — build (core moat).
• MCP server & AI client integrations — build (core moat).
• Evidence-grounded scoring (WSJF / RICE / OKR alignment) — build.
• SOC 2 Type II + enterprise readiness — partner with auditor; gap until Q3.
• Outbound sales motion — gap; PLG-only until $3M ARR.

Block 5 — Management Systems

The systems that keep you honest. Without these, the strategy decays into wall art within a quarter.

• Quarterly strategy review — full leadership team revisits the cascade. Capability gaps re-scored.
• Win/loss reviews — every $25k+ deal lost gets a written analysis tied to Where to Play / How to Win.
• Customer council (twice yearly) — 8–12 customers in the target segment. They tell us where we’re drifting.
• Hiring bar — every hire is scored against the capability list. No “just because they’re great” hires.
• The kill list — one feature, one segment, one channel cut every quarter. If you can’t cut, the strategy isn’t real.

Worked example — end to end

Strategy is choice

If those blanks make the team uncomfortable, good. The discomfort is the strategy doing its job.

Refresh cadence

• Annually — full cascade refresh. Re-question Aspiration and Where to Play. Two-day offsite minimum.
• Quarterly — capability check. What’s built, what’s gap, what’s the hiring plan? Half-day session.
• Mid-year — management systems review. Are the metrics measuring the right thing? Is the kill list real or theatrical?
• Trigger-based — a major competitor move, a category-redefining customer shift, or a 2x change in your own ARR triggers an out-of-cycle refresh.

Common strategy mistakes

• Vision-as-strategy — “Be the most loved tool in our space.” That’s a feeling, not a plan. No segment, no how, no capability. Wall art.
• Market-size-as-strategy — “The TAM is $40B.” Cool. Market size is a permission slip, not a strategy. The cascade asks how you win the slice you can serve.
• Feature-list-as-strategy — the 12-quarter Gantt chart. That’s a roadmap. A strategy says why those 12 quarters, not which ones.
• Never-says-no — if Where to Play has no “OUT” column, the rest is fiction. Strategy is constraint; constraint is the product of saying no.
• No execution loop — written, filed, never revisited. Without management systems, strategy is decoration. The loop is the strategy.