Strategy on a page

Strategy on a page is a single-sheet document that states an agreed strategy in full: the goal, the few priorities that serve it, the measures that prove it, and the owners. It communicates a decision already made; it does not make one.

The format exists because long plans go unread. A 60-slide deck gets approved, filed, and quietly ignored by the people whose weekly choices decide whether it happens.

One page forces a choice. If a priority can’t fit, it probably isn’t a priority, and the argument about what to cut is the most useful meeting in the planning year.

Length is the tell. If a strategy needs forty pages to explain itself, the choices inside it probably haven’t been made yet — the document is still doing the arguing.

Treat it as an output, not a method. The thinking happens elsewhere; the page is how strategy implementation reaches the people who have to carry it.

Key takeaways

• The page is an artefact, not a planning technique — it records a decision rather than making one.
• Everything fits on one sheet: goal, priorities, measures, owners and the time horizon.
• It is a communications tool first, which is why the wording matters more than the graphics.
• It is republished when the strategy changes, not quietly edited between reviews.

How it works

A strategy on a page compresses an approved strategy into five blocks: why the organisation exists, where it is heading, the handful of priorities that get it there, how success will be measured, and who owns each priority. Everything else is supporting detail.

Designers of the page usually work backwards. They draft the measures first, because a priority nobody can measure tends to be an aspiration wearing a verb.

Layout follows the reader. A board wants the goal and the risk picture; a delivery team wants the priorities and the owners. Most organisations publish one version and resist making departmental variants.

Wording does most of the work. “Grow in Asia” tells nobody anything; “win 20 mid-market clients in the Philippines by December” tells a sales lead what Monday looks like.

Version control matters more than it sounds. Date the page, number the version, and publish every change openly, so nobody is still working from last year’s priorities.

The page also acts as a filter for the roadmaps underneath it. A product strategy roadmap or a data strategy roadmap that supports no priority on the page is a candidate for cancellation.

Distribution is the step teams skip. A page that lives in a shared drive changes nothing — it belongs in the internal communications strategy and on the wall of every operating site.

Examples

Public bodies and manufacturers have published one-page strategies for decades, and the format travels well into outsourcing, where a client and a provider need the same single reference. Three concrete cases show the range.

Australia’s National Indigenous Australians Agency publishes one. Its Corporate Plan 2024–25 renders the whole strategy as a Plan on a Page with vision and purpose at the centre.

Key activities and performance measures sit in the middle ring. Operating environment, partnerships, capabilities and risk management run around the outside as the enabling factors.

Manufacturing got there first. The Lean Enterprise Institute describes the Toyota-pioneered A3 report as getting the problem, the analysis, the corrective actions and the action plan down on a single sheet of large paper.

Outsourcing accounts use a client-facing version. A BPO running a 300-seat programme will post a one-pager naming the service goal, the delivery priorities, the service levels and the account owner on each side.

Both parties sign it. That single step stops the quarterly business review turning into a debate about what was agreed at the start.

Technology functions do the same for a single domain. A one-page summary of a cloud strategy roadmap or an AI adoption strategy keeps a programme honest about what it refused to fund this year.

Related terms

These terms sit close to strategy on a page. Some describe the planning work that happens before the sheet is drafted, some are the longer documents it summarises, and one is the delivery system it hands off to.

• Strategy implementation: the delivery work the page is meant to trigger.
• Internal communications strategy: the plan for getting the page in front of staff.
• Product strategy roadmap: a longer sequenced document the one-pager summarises.
• Cloud strategy roadmap: the domain-level plan behind a single technology priority.
• Account expansion strategy: a commercial plan that often earns its own one-page version.

FAQ

The common questions are practical ones: how literal the single page has to be, what gets cut, how often it is reissued, and whether a shared version makes sense between a client and an outsourcing provider.

Does it have to be literally one page?

Yes, and the constraint is the point. The moment a second page is allowed, the discipline that makes the format useful disappears.

What gets cut first?

Initiatives, not priorities. A one-pager names the few outcomes that matter and leaves the project list to the roadmaps and plans beneath it.

How often should it be reissued?

Once a year with the plan, plus a reissue whenever a priority or owner genuinely changes. Silent edits destroy trust in the page, so version and date it.

Who should write it?

The leader who owns the strategy, with help on wording — not the design team. If an executive can’t draft it, the strategy probably isn’t settled yet.

Can a client and provider share one page?

They should. A joint one-pager stating shared goals, service levels and named owners removes most of the ambiguity that sours outsourcing relationships in year two.

How is it different from a roadmap?

A roadmap sequences work over time and names dates. A one-page strategy states the goal and the priorities, then leaves the sequencing to the roadmaps underneath it.

For a sharper view of the delivery partners behind your plan, browse provider profiles and pricing on Outsource Accelerator.