How to write a one-page strategy
Guide · Founder · 4 min read · last verified 2026-07-28
A one-page strategy is a single page that states three things: the diagnosis — what is actually going on in your market and your business — the choice you are making in response to it, and the first proof that would show the choice is working. That is the entire format. Everything else that typically fills a strategy document — mission language, initiative inventories, quarterly targets — either belongs in a different document or belongs nowhere.
We have argued elsewhere that strategy and planning are different disciplines; this piece is about the artifact. If the distinction piece answers "what is strategy," this one answers "what do I actually write down, and how do I know I wrote the right kind of thing."
Why the page limit is the point
Strategy documents tend to go unread for reasons that have little to do with their quality: they are long, they hedge, and by the middle they have usually become indistinguishable from an operating plan. Nobody rereads a sprawling deck before making a hard call. A single page gets read in minutes, remembered in outline, and quoted back in meetings — and that is the actual job of a written strategy: to make the same choice show up in the many small decisions you are not in the room for.
The limit is a forcing function, not a formatting preference. If your diagnosis fits in a paragraph, you probably understand your situation. If it keeps sprawling, the writing is telling you the thinking is unfinished — and it is far cheaper to discover that on a page than across a quarter of scattered execution.
Part one: the diagnosis
The diagnosis is a short, falsifiable account of your situation: what is happening in your market, where you sit in it, and what the central problem or opportunity is. It should rest on evidence you would defend in front of your most skeptical operator — measured position, observed competitor moves, what customers actually said when they bought or left — rather than on aspiration. This is where a platform like Magrios belongs in the writing process: when the diagnosis makes claims about visibility, competitive standing, or retention, those claims should trace back to something measured, not something remembered.
Two failures recur. The first is a diagnosis that is secretly a goal: "we need to grow faster" describes a desire, not a situation. The second is a diagnosis so generic that any company in the category could adopt it unchanged. A useful check: if a competitor could paste your diagnosis into their own page without edits, keep digging — you have not yet named the thing that is specifically true of you.
Part two: the choice
The choice is one or two sentences naming the direction you are committing to because of the diagnosis. It should be concrete enough that a new hire could use it to pick between two competing projects without asking anyone. "Win mid-market operations teams by going deeper into their daily workflow than anyone else" is a choice. "Delight customers with excellence" excludes nothing, so it decides nothing — the value of the sentence lives in the exclusion it implies, and the page should make that exclusion explicit rather than leaving it to inference.
Part three: the first proof
The first proof names the earliest observable signal that would suggest the choice is working — and, ideally, what you would expect to see if it is not. Not the end-state target, not the annual number: the first thing. This keeps the page connected to reality without turning it into a reporting surface. A growth report tells you what already happened; a growth plan commits to what you will do next; the one-pager stakes a prediction and invites the check.
The test: does it name what you will not do?
Here is the line between a strategy and everything that borrows the word. If the page contains no refusals — no segment you are declining, no channel you are deliberately leaving alone, no plausible product direction you are consciously not funding — then what you have written is a plan traveling under a grander title, and it will fail at the one job plans are structurally bad at: settling arguments. In practice the refusals are the hardest lines to write and the most quoted afterward. When a project gets killed in your company, this is the part of the page someone reads aloud.
What stays off the page
Targets with dates, task lists, owner columns, budget asks: all of it belongs in the plan that sits beneath the strategy and inherits its logic. The board version stays off the page too — a board deck and an operating review answer to different audiences, and the one-pager answers to neither; it is the reference document both should be consistent with.
Keeping the page alive
A one-pager earns its keep at decision points, so put it where decisions happen: at the top of planning meetings, as the context for prioritization calls, as the first document a new senior hire reads. Revise it when the diagnosis changes — new evidence, a market shift you can point to — and resist revising it when the mood changes. If the page changes every month, it was never a strategy. If it survives contact with a hard quarter unchanged and still feels true, you probably wrote a good one.