Product Strategy Document
A product strategy document is a written, dated, single-author memo that names (1) the customer problem you've chosen to solve, (2) the customers you've chosen to serve, (3) the customers you're explicitly NOT serving, and (4) the bets you're making about how you win. It sits between vision (10-year) and roadmap (1-year). Reforge teaches that strategy is fundamentally about choice — what you say no to. Lenny Rachitsky's archive of 50+ real strategy docs reveals a pattern: the great ones are 6–12 pages, written by one person, debated brutally, and revised quarterly. The mediocre ones are 60-page slide decks written by committee, signed by everyone, defended by no one.
The Trap
The trap is the consensus strategy doc — every stakeholder added their concern, every objection got a paragraph, every market got a 'we serve this segment too.' The result reads like a treaty, not a strategy. Strategy by committee selects for the lowest-risk option, which is almost always 'incrementally improve everything,' which is the absence of strategy. The second trap: confusing strategy with planning. A 200-line OKR doc is a plan. A strategy is the argument for WHY those OKRs and not the 50 other plausible ones.
What to Do
Make one person — usually the CPO or founder — the named author. Constrain to 6–12 pages. Force three explicit sections: 'who we serve,' 'who we don't serve,' and 'the bet.' Distribute as a memo (Bezos-style) with 30 min of silent reading at the start of a 90-min review. Surface dissent by asking each attendee for the 'one thing you'd change.' Revise quarterly. Date every version.
In Practice
Lenny Rachitsky published an analysis of how leading PMs at Stripe, Figma, and Notion structure their strategy docs. The shared pattern: ~8 pages, named author, explicit 'we don't serve' section, and a 'bets' section listing 3–5 testable hypotheses with kill criteria. Stripe's early strategy docs (per Patrick Collison) were notable for explicitly naming PayPal as the competitor and being honest about why Stripe was at a structural disadvantage on payment volume — and how API-first developer focus was the bet to overcome it. Source: Lenny's Newsletter, 'How top PMs write product strategy.'
Pro Tips
- 01
Reforge: 'A strategy doc that doesn't make at least one senior person uncomfortable hasn't made a real choice. Comfort is the smell of consensus.'
- 02
Add a 'kill criteria' section to each bet: 'we'll know this bet failed if X happens by Y date.' This converts the doc from aspirational to falsifiable.
- 03
Don't put the strategy in slides. Slides hide weak arguments behind bullets. Memos force the prose, and the prose exposes whether the thinking is actually there.
Myth vs Reality
Myth
“Strategy docs need executive polish”
Reality
The opposite. Polished docs invite ratification, not debate. Working docs with crossed-out sections and footnotes get better feedback because they signal 'this is open for revision.' Save the polish for the version that goes to the board, not the one that drives weekly decisions.
Myth
“A good strategy doc lasts a year”
Reality
A good strategy doc lasts a quarter. The bets you wrote in January are partially invalidated by April — that's healthy. A strategy doc that hasn't been revised in 12 months is either ignored or describing a world that no longer exists. The document is alive; print versions decay.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your CPO presents a 47-slide product strategy deck. Every regional VP added their input. Every feature area is represented. Every objection got a counter-slide. What's most likely true?
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Stripe
2011–2014
Patrick Collison authored Stripe's early product strategy memos personally. They were short (under 10 pages), named PayPal explicitly as the competitor, and were honest about Stripe's structural disadvantages — lower payment volume, no merchant base, no brand. The strategic bet was singular and explicit: developer-first API as the wedge. Every roadmap decision in those years could be traced to that bet. The company didn't try to also serve enterprise direct sales, didn't try to serve consumers, didn't try to be a wallet — choices that other payment companies struggled to make.
Doc Author
Single (Patrick Collison)
Doc Length
< 10 pages
Explicit 'Will Not' Choices
Multiple — consumers, enterprise wedge, wallet
Single authorship + brevity + explicit 'will not serve' sections produced a strategy that drove decisions for years. Committee-authored consensus would not have made the API-first bet — it would have hedged with an enterprise sales motion 'just in case.'
Hypothetical: A Series D PLG company
2023
A Series D PLG company produced a 73-page product strategy 'document' (actually a slide deck) over 5 months with 11 named contributors. It included every customer segment, every product line, every feature area, and a 'we will continue to evaluate' phrase 14 times. Six months later, when asked to make a roadmap trade-off (PLG self-serve vs. enterprise sales-led), no one could cite the strategy doc to settle the debate. The doc had become decorative.
Length
73 slides
Authors
11
'We Will Not' Statements
0
Roadmap Disputes Resolved by Doc
0
Length and number of authors are inversely correlated with strategic usefulness. This doc was a political artifact, not a decision tool.
Decision scenario
Consensus Strategy vs. Single-Author Memo
You're the new CPO of a 400-person SaaS company. The existing 'strategy' is a 60-page deck with sign-off from every C-level. The CEO supports refreshing it. You have 6 weeks before the annual planning kickoff and the political capital to push for a real change.
Current Strategy Doc Length
60 pages
Authors
8
Roadmap Disputes Resolved by Doc
≈ 0
Time Until Annual Planning
6 weeks
Decision 1
Your VP of Marketing wants to keep the consensus model — 'changing the format will create chaos before planning.' Your VP of Engineering is openly skeptical of strategy docs in general. The CEO is supportive but not vocal.
Iterate on the existing 60-page doc — preserve the structure, sharpen language, ship a v2 in 4 weeksReveal
Author an 8-page memo yourself with explicit 'we will not serve' and 'we are betting on' sections. Run a 90-min Bezos-style silent-read review with the C-team. Date it v1.0. Commit to quarterly revisions.✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Product Strategy Document into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Product Strategy Document into a live operating decision.
Use Product Strategy Document as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.