Run a Strategy Blocks sprint to craft a 2-year product strategy

Strategy Blocks: Why Most Product Strategy Docs Fail — and What Replaces Them

Most product strategy documents read like a mission statement with a roadmap bolted on. They do not help teams decide what *not* to build, and they rarely survive first contact with a quarterly review. Reforge's Product Strategy Stack notes that the most common failure in PM orgs is confusing a prioritized feature list with actual strategy — a pattern that leaves every quarter's review arguing over the same tradeoffs from scratch.

Why "strategy" keeps collapsing into a roadmap

Michael Porter's 1996 HBR essay "What Is Strategy?" argued that strategy is the "disciplined choice to deploy scarce resources for maximum impact" — not a list of projects. In practice, teams skip that choice. Marty Cagan's SVPG essay on product strategy makes the same point: most "strategies" are really a compilation of feature requests ranked by the loudest stakeholder. Atlassian's product strategy guide puts the operational cost plainly — without a strategy layer between mission and roadmap, teams cannot explain *why* they are working on any given project, which blocks downstream prioritization and stakeholder alignment.

Strategy Blocks forces the missing step — picking 3 to 5 strategic pillars and an equal list of what will not be focused on — and builds alignment into the process rather than treating it as a last-step sell.

How the Run a Strategy Blocks sprint to craft a 2-year product strategy Prompt Works

The prompt walks an AI through all five phases of the framework and produces usable artifacts at each step:

• Preparation (3-5 weeks): leadership interviews, behavioral + UXR meta-analysis, competitive/comparables analysis, user observation for empathy.
• Strategy sprint (1 week): 50-150 problems → 10-15 clusters → 4-dimension scoring (impact, certainty, clarity of levers, uniqueness of levers) → top 3 pillars → 2-year winning aspiration as a future headline.
• Design sprint (1 week): illustrative concepts that make the pillars legible, following the Google Ventures Design Sprint pattern.
• Document writing (1-2 weeks): combine all inputs into a single leader-ready brief.
• Rollout (2-3 weeks): gatekeeper 1:1s → stakeholder group review → team roadshows → roadmap empowerment.

The scoring rubric is the load-bearing piece. Forcing every opportunity area through four dimensions prevents the most common failure mode: picking a pillar because someone senior is excited about it.

When to Use It

• You are a new product leader inheriting an unclear strategy and have 8-12 weeks to produce one.
• Teams are shipping features but cannot articulate the larger bet.
• A CEO or board has asked for a 2-year strategy that is more than a roadmap.
• You are preparing for a major funding milestone and need a defensible narrative.
• You need to explicitly *stop* doing something and need political cover for the cut.

Common Pitfalls

• Skipping leadership interviews — the single most frequently omitted step, and the one that surfaces the "pet ideas" you will have to address anyway.
• Over-polishing the share-out deck — substance over style. The deck is fuel, not a deliverable; polish wastes the week you need for the actual sprint.
• Tinkering with pillars during roadshows — roadshows are for clarity adjustments only. If you re-litigate pillars every time someone pushes back, the process has failed.

Sources

• What Is Strategy? — Michael Porter, Harvard Business Review, 1996
• Product Strategy Overview — Marty Cagan, Silicon Valley Product Group
• The Product Strategy Stack — Reforge
• What is product strategy? — Atlassian
• The Design Sprint — Google Ventures