← Edge Notes
Founder Craft9 min read
Essay · founder craft

The strategy that fits on one page

Every company has a strategy document. Almost none of them are strategies. The one-page constraint isn't a formatting preference — it's a forcing function that exposes the decisions leadership has been avoiding. If it doesn't fit on one page, the choices haven't been made yet.

The document everyone has and almost nobody reads.

The strategy offsite ritual is familiar. Two days at a hotel or a retreat house with whiteboards and post-its. A facilitator, usually external. Three-year visions, ten-year ambitions. SWOT matrices. A slide deck with a market sizing slide that has a very large number with a dollar sign in front of it. Everyone leaves energised. The document gets filed and referenced once at the next all-hands before being quietly retired to a shared drive where it will never be opened again.

This is almost universal. It happens at Series A startups, at scale-ups, at the regional arms of multinationals with more budget than sense. The ritual is performed; the artifact is produced; nothing changes about how decisions get made on Monday morning.

The reason isn't that people are lazy. It's that most "strategy documents" are not strategies at all. They are ambition lists — well-formatted inventories of everything leadership hopes to accomplish, collated under sections called "pillars" and decorated with OKRs. They describe a desired future state. They do not describe a path. And critically, they do not describe what you have decided not to do.

What strategy actually means.

Strategy is the set of choices that creates an advantage in your chosen arena. The key word is choices — plural, specific, and mutually reinforcing. A goal says "become the market leader." A strategy says "we will become the market leader among logistics companies in Southeast Asia by being the only platform that integrates warehouse management with last-mile dispatch, and we will not serve e-commerce brands, retail chains, or any segment where that integration is not the core pain point." The second version is a strategy because it tells you what to say no to.

Richard Rumelt, whose book on strategy is the best thing written on the subject, describes the kernel of good strategy as: a diagnosis of the problem, a guiding policy that addresses it, and coherent actions that implement the policy. Notice that goals appear nowhere in this structure. Goals describe what you want. Strategy describes how you intend to create an asymmetric position. Plenty of companies have excellent goals and no strategy whatsoever.

The most revealing question to ask a founding team is not "what is your goal?" It is "what have you decided not to do?" Companies with genuine strategy can answer that question specifically and defensibly. Companies with ambition lists give a long pause followed by something like "well, we're focused on our core market for now." That's not a decision. That's a deferral.

Why roadmaps are not strategies.

Product roadmaps became the de facto strategy artifact for a certain generation of tech companies and never recovered. A roadmap answers one question: in what sequence are we building things? It is a project plan with a horizon. It is a useful document for coordination. It is not a strategy.

The confusion is understandable. A roadmap that reflects good strategic choices will look different from a roadmap that reflects bad ones. If your strategy is to win mid-market by being the fastest to deploy, your roadmap will be full of integrations, reduced setup friction, and onboarding tooling. If your strategy is to win enterprise by being the most customisable, your roadmap will be full of configuration APIs and professional services enablement. The roadmap is downstream of the strategy. Most teams treat it as if it is the strategy.

The result: you can have a perfectly well-sequenced roadmap that produces an incoherent product. Each quarter's work makes sense individually. None of it compounds into a defensible position. It happens at companies with strong engineering teams and capable PMs who are building exactly what users asked for — and still losing ground because the cumulative output doesn't make a compelling case for why a customer should pick them over anyone else.

Strategy is not the list of things you want to accomplish. It is the specific set of choices that makes those things possible — and makes the opposite choices impossible to execute simultaneously.

The one-page format that actually works.

Many formats exist. The one that most reliably produces the most useful output has five sections, none longer than three or four lines, all on a single page without reduction in font size.

The first section is the diagnosis: what is the specific problem in the market that you are in a position to solve? Not "companies need better data" — that's a category, not a diagnosis. Something like: "mid-sized logistics operators in SEA can't see their end-to-end cost per delivery because their warehouse and dispatch data live in separate systems with no shared ID scheme." Specific. Falsifiable. Yours to solve.

The second section is the customer: which specific customer has this problem urgently enough to pay and switch from their current solution? "Logistics operators" is not specific enough. "Freight forwarders with 15–80 warehouse staff who are currently running operations on a combination of WhatsApp, Excel, and one legacy WMS they hate" is specific enough. You should be able to describe the person who picks up the phone when you call.

The third section is the advantage: what will you compete on, and why are you better positioned than anyone else to compete on exactly this? Advantages are usually one of three things — a unique distribution edge, a proprietary data or network position, or a speed/cost edge that reflects something structural about how you're built. "We're better" is not an advantage. "We're the only platform where the founders spent five years running a freight forwarding operation and built this because they had the problem" is the seed of an advantage.

The fourth section is the moves: what are the two or three specific actions in the next twelve months that create or extend this advantage? Not goals. Not initiatives. Moves — decisions with teeth. "Close five reference customers in the 15–80 employee band before hiring any enterprise sales." "Build the WMS-dispatch ID bridge before adding any reporting features." These are strategy in action.

The fifth section is what you are choosing not to do. This is the hardest to write and the most important. It should hurt slightly to read it. If your "not doing" list is comfortable, you haven't made real choices. The things in this section should be things that someone in the room genuinely wanted to pursue and you said no to, together, on the record.

Why the constraint itself is the point.

One-page is not an aesthetic choice. It is a forcing function. The discipline of making something fit on one page requires the same intellectual work as making the strategic choices the company needs. You cannot list fifteen priorities on one page. You have to pick three. You cannot describe twelve customer segments in three lines. You have to name the one that matters most right now. The format does not allow you to hold multiple contradictory positions simultaneously, which is exactly what most strategy documents do.

A useful exercise for a founding team: hand them a one-page template on day one and make filling it in completely the deliverable. The most common failure mode is that teams arrive at the fifth section — the not-doing list — and cannot agree on what to put there. Not because they don't have ideas, but because committing to "we are not doing X" requires one person to lose the argument they've been running for six months. The one-page constraint surfaces these undecided fights. That's the point.

A twenty-page strategy deck can hide three unresolved disagreements between leadership in the gap between slide twelve and slide eighteen. A one-page document cannot. Every line has to be agreed. Every choice has to be shared. The document is only useful if the process of producing it was itself uncomfortable — if it forced resolution of things that had been left ambiguous on purpose.

Picture a CEO and a CPO staring at a half-filled one-page template for forty minutes, stuck on the customer section, because they hold fundamentally different views on who the primary customer is. Those forty minutes are worth more than most strategy offsites. They are not debating slide formatting. They are making a decision they have been avoiding for a year.

Frequently asked questions.

What is the difference between strategy and goals?

Goals describe what you want to achieve. Strategy describes which path you will take — and which paths you will not take. A goal says "double revenue." A strategy says "double revenue by winning mid-market SaaS customers in Southeast Asia, and not pursuing enterprise deals or consumer segments this year." The second version makes decisions. The first just states a wish. You need both, but confusing them produces plans that look bold and behave timidly.

Why do most company roadmaps fail as strategy?

Roadmaps are sequenced feature lists. They answer "what are we building?" not "why this and not something else?" A roadmap can be completely coherent as a list of work and still be strategically incoherent — if the features don't compound toward a defensible position, the roadmap is just a busy plan. Most roadmaps were never designed to answer the "why not" question, because that question forces a fight nobody wanted to have in the sprint planning meeting.

How long should a strategy document be?

One page. Not because strategy is simple, but because if you cannot express the core of your strategy on one page, you have not finished thinking. The work of making it one page is the same work as making the choices the strategy requires. A twenty-page strategy deck is usually evidence that leadership has not yet decided — the length is padding that obscures the unresolved questions.

What goes on a one-page strategy?

Five elements: the specific problem you have decided to solve, the specific customer you have decided to win, the advantage you will compete on and why you are positioned to hold it, the two or three moves in the next twelve months that create that advantage, and an explicit list of what you are choosing not to do. Everything else is execution planning, which is important but different.

Working on this?

If this is the problem on your desk, a 30-minute intro is the fastest way to find out whether I can help.

Request an intro →