The product strategy one-pager: if it doesn't fit on a page, you don't have one

Most product strategy documents are twenty slides and describe a direction nobody could disagree with. That’s the tell: a strategy that nobody could argue with isn’t one, because a strategy is a choice, and a choice has a loser.

The page limit isn’t an aesthetic preference. It’s a forcing function. Twenty slides give you room to include everything, and including everything is how you avoid deciding.

What goes on the page

1. What we’re optimising for, in one sentence

One thing. Not “growth and retention and enterprise readiness” — the conjunction is where strategies go to die, because it gives every team permission to pick whichever clause justifies what they wanted to do.

If you genuinely can’t reduce it to one, the honest version is a ranked list of two, with the second explicitly subordinate.

2. Why this and not the obvious alternative

Name the alternative you rejected and why. This is the section that separates a strategy from a plan, and it’s the one most commonly missing.

If you can’t name a credible alternative, you haven’t made a choice — you’ve described the default.

3. The three bets

For each: what we believe, what we’ll do about it, and what would make us stop.

That third element is the one that gets dropped, and dropping it is what allows a failing bet to run for a year. A bet with no stopping condition isn’t a bet, it’s a commitment.

4. What we’re explicitly not doing

With names attached where relevant — the customer segment, the competitor feature, the platform. Unstated non-goals creep back within a quarter, usually via someone who wasn’t in the room and reasonably assumed it was still open.

This section is what makes the page useful in an argument six months later.

5. What has to be true

The assumptions the whole thing rests on. If one of these turns out to be false, the strategy changes rather than the execution getting blamed.

Three or four is right. This is also your early-warning system: assign each one a way you’d find out.

What doesn’t go on it

The roadmap. Different document, different lifespan. A strategy that contains a feature list gets edited every time the feature list changes, and then it’s a plan.

Market analysis. Do the work, keep it elsewhere, reference it. The page is the conclusion, not the evidence.

The tests

Would a competitor’s strategy look different? If you’d be happy for your strategy to describe your main competitor too, it isn’t a strategy — it’s a description of the category.

Can a team use it to say no? Hand it to someone and ask them to reject a plausible-sounding request using only the page. If they can’t, it won’t do the job you wrote it for.

Does anyone disagree? Circulate it and watch. Universal agreement usually means it’s too vague to argue with. Someone senior being uncomfortable is a better signal than everyone nodding.

Writing it

Ninety minutes, not a workshop series. Draft it alone first — committee drafting produces the conjunctions.

Then take it to the three people most likely to disagree, separately, and ask them to attack it. What survives is the strategy; what doesn’t survive would have collapsed later and more expensively.

Give it a review date on the page itself. Six months is reasonable for most companies, three for anything early. A strategy with no review date silently becomes permanent, and the review is where you check whether the “what has to be true” section still holds.

When you can’t write it

If the page won’t come, one of three things is usually true, and it’s worth naming which:

• You don’t understand the business well enough yet. Another two weeks of conversations is cheaper than a quarter spent on the wrong bet. This is the normal answer in a new role, and it’s what the first thirty days are for.
• There’s no agreement above you. Then writing it is genuinely useful — as a provocation. A wrong one-pager circulated gets corrected fast; the absence of one gets tolerated indefinitely.
• You’re avoiding the non-goals section. Very common, and the section is the whole point. If naming what you won’t do feels politically expensive, that’s a measure of how badly the page is needed.

---

The one-pager is also the artefact I’d most recommend if you’re building the case for a step up: it’s a compact demonstration of judgement, which is what a promotion committee is looking for and what a roadmap can’t show. Writing one and having someone senior attack it is a large part of what coaching sessions end up being.