Strategy on a Page: A Template That Carries the Why

Five priorities and a customer on the phone

Picture a regional operations manager at a food distributor. Taped beside her monitor is the company's strategy on a page: a vision line, five priorities with icons (Customer First, Operational Excellence, Profitable Growth, Our People, Digital), and a row of targets. It was handed out at the kickoff in January. It looks good.

In March her largest restaurant group asks for a custom delivery window: 5 a.m., three days a week, on a route that does not run then. It would cost margin and a driver's overtime. Customer First says yes. Profitable Growth says no. She reads the page twice, then forwards the request to her vice president. So do eleven other managers that month.

The page did not fail because it was wrong. It failed because it gave her the conclusions and none of the reasoning. A strategy on a page is a one-sheet summary of the choices a strategy makes, the few priorities that carry them out and how progress will be measured. The version with context adds three things: what changed to force the choices, what the company decided to give up, and rules for breaking ties between priorities. Those three are what let a manager decide a case the page never mentions.

That is the thesis of this page. Priorities tell people what matters. Only the reasons tell them what to do when two things that matter collide, which describes most decisions that reach a manager's desk.

Priorities tell people what to do. The why tells them what to do when the priorities run out.

Borrowed from the Army: intent, not instructions

US Army doctrine has worked on this problem for a long time, because its plans meet reality fast. Its 2019 mission command publication, ADP 6-0, defines the commander's intent as “a clear and concise expression of the purpose of the operation and the desired military end state that supports mission command, provides focus to the staff, and helps subordinate and supporting commanders act to achieve the commander’s desired results without further orders, even when the operation does not unfold as planned” ¹.

Read the last clause again: without further orders, even when the operation does not unfold as planned. That is the job a strategy on a page should do and almost never does. The doctrine is specific about how. The intent explains the broader purpose so subordinates can see “what is expected of them, what constraints apply, and, most importantly, why the mission is being conducted” ¹. It is short: “If it is longer than a brief paragraph it is probably too long” ¹. And it is written for people well below the author: “Soldiers two echelons down should easily remember and clearly understand the commander’s intent” ¹.

The business version of the failure has a name too. Chip and Dan Heath argue that many sensible strategies fail to drive action because executives write them in sweeping, general language: the executives know the concrete detail behind each abstraction, and the front line hears only the abstraction ². “Customer First” meant something precise to the people who argued it out over three offsites. To the manager with the 5 a.m. request it means nothing she can act on.

David Collis and Michael Rukstad put the stakes plainly: most executives cannot state the objective, scope and advantage of their business simply, and “If they can't, neither can anyone else” ³. The context version of the page is how you make sure someone else can.

The template

Nine fields, one side of one sheet. The prompt is the question each field must answer for a manager who was not in the room. If the leadership team cannot fill a field, that gap is the finding.

Fields 3 to 6 are the choices and measures. If you already have a strategic plan, they come from its first page, unchanged. That page is written so next year's leadership team can grade the plan. This one is written so a manager two levels down can use it this afternoon. Fields 1, 2, 7 and 8 make the difference.

A filled-in example

The company is invented. Watch what fields 1, 2 and 8 do to the 5 a.m. request from the opening.

Now run the 5 a.m. request through it. The account is an independent restaurant, the intent says be the supplier it would least want to lose, and the first tie-break rule says choose reliability over margin and flag the cost. The manager can say yes herself and send her VP the overtime figure. Had the new window delayed other restaurants on the route, the second rule would have told her to decline, just as quickly.

Notice what made that possible. It was not a sharper priority. It was the intent (be the supplier a restaurant least wants to lose) and a tie-break rule written by people who saw the conflict coming.

How to write it

1. Start from choices the top team has already agreedThe page communicates a strategy; it does not settle one. Donald Sull and colleagues found that two-thirds of the top executives were on the same page in just 27% of the companies they studied ⁴. Before drafting, ask each member of the top team to write the priorities down independently, and compare.
2. Write field 1 in your customers' termsDescribe what changed as a manager would see it: lost accounts, a new competitor's truck at the loading dock, a cost that doubled. Leave the market-share charts for the full plan.
3. Write the intent last, then cut itDraft field 2 after the others, when you know what it has to hold together. Then cut it to one short paragraph, the length the Army sets for its own intent statements ¹.
4. Give every priority a reasonAdd “so that” to each priority and finish the sentence. Sull and colleagues argue that strategic priorities should be forward-looking and action-oriented, and suggest testing them by “asking middle managers what they would stop doing based on the priorities” ⁴. A priority with no reason gives that test nothing to work with.
5. Mine last quarter for the tie-breaksCollect five real decisions that were escalated in the past quarter because two goals conflicted. Write a rule that would have settled each. Keep the two to four that recur.
6. Test it two levels downGive the draft to three managers two levels below the top team and three real cases. Ask what they would decide and why. If their answers differ from the top team's, fix the page, not the managers.
7. Date it and name an ownerA page with no date stays on walls long after the strategy has moved. Put the issue date and the next review on the page, and name who answers questions.

Weak and strong, line by line

Every weak line could sit on any company's page. Every strong one would look wrong on a competitor's. Swap in a rival's logo and see whether anything stops making sense.

The case against putting the reasons on the page

• “Context invites relitigating.” Explain why you chose, and people will argue with the reasons. True, and better now than in month nine, when the argument shows up as quiet non-compliance. The page states the reasons; it does not reopen the decision. The doctrine draws the same line: during execution, the intent “establishes the limits within which a subordinate may exercise initiative” ¹. Reasons widen what people can decide. They do not make the decision optional.
• “It will leak to competitors.” Leave out what should never hang on a wall: target prices, acquisition plans, sites under review. A competitor that learns you have chosen reliability over price learns little it could not see from your trucks. A page so guarded that your own managers cannot use it is the larger and more certain risk.
• “Tie-break rules turn judgment into a rulebook.” They would, if there were thirty. Two to four rules for the collisions you can already predict leave every other case to judgment, now informed by the intent. Sull and colleagues warn that many leadership teams “agree on vague abstractions that everyone can get on board with” ⁴. A tie-break rule is the opposite: it is the sentence that shows which abstraction actually wins.

The deeper objection is unspoken. Writing the tie-breaks forces the top team to settle conflicts some members would rather leave open, because an open conflict lets each executive read the page their own way. That is the best argument for writing them. If the top team cannot agree on field 8, the managers below them will settle it differently in every region, and nobody will call it a strategy problem.

One page per level, nested

In a large company, one page cannot tell a plant manager in Ohio and a product lead in Bangalore what changes for them. The answer is a page for each unit, nested inside the one above. ADP 6-0 says each commander's intent “nests within the commander’s intent two levels up” ¹. For a business unit, its fields 2 and 8 must be readable against the corporate page, and any conflict is resolved before either is issued.

• Rewrite fields 5 to 8 for the unit. The unit's priorities each name the corporate priority they serve.
• Collect the unit pages before issuing them. Read all the tie-break rules side by side. Two units that settle the same conflict in opposite ways will meet each other at a customer.
• Retire old pages out loud. When the strategy changes, say which page is replaced. A wall with three generations of priorities teaches people that none of them matter.

Then test whether the pages work. Sull, Sull and Yoder found that only 28% of the executives and middle managers responsible for executing strategy, across 124 organizations, could list three of their company's strategic priorities ⁵. Their data also showed agreement falling from 51% within top teams to 22% one level below ⁵. The strategic alignment check runs a version of their listing test. For the meetings that carry the page down to the front line, use the strategy cascade kit.

Before you print it

• A manager who missed every offsite could explain field 1 to their team in two minutes.
• The intent is one short paragraph and still makes sense if every priority below it changed.
• Field 4 names something that someone senior wanted to keep.
• Every priority ends with a reason, and no more than five are listed.
• The tie-break rules settle at least two conflicts that were escalated last quarter.
• Three managers two levels down, given three real cases, decided them the way the top team would.

The wall in that regional office will hold whatever you print. A list of priorities makes a good poster. A page that says why, what was given up and which goal wins a tie makes a manager who no longer needs to forward the email.

Questions

What is a strategy on a page?

A strategy on a page is a one-sheet summary of the choices a strategy makes, the three to five priorities that carry them out and the measures that track progress. The most useful versions also state what changed to force the choices, what the company is giving up and how to break ties between priorities, so managers can apply it to cases it does not name.

What should a strategy on a page template include?

Nine fields: what changed, the intent (the end state and why it matters), where you focus and how you win, what you are giving up, three to five priorities each with a reason, measures with baselines and targets, one line per team on what changes, two to four tie-break rules, and an owner with issue and review dates.

How is a strategy on a page different from a one-page strategic plan?

A one-page strategic plan is written so the leadership team can grade the strategy later: objectives, choices, assumptions and measures. A strategy on a page uses the same choices but is written for people who were not in the room. It adds the reasons, the trade-offs and tie-break rules, so a manager two levels down can make decisions with it.

What is commander's intent and why does it matter for strategy?

In US Army doctrine, the commander's intent is a short statement of an operation's purpose and end state that helps subordinates act without further orders when the plan stops fitting. A strategy on a page needs the same: a purpose that lets managers decide when priorities conflict.

Where to go next

• Strategic Plan Template: One Page of Choices, Then the Full Plan
• Communicating Strategy So People Can Act on It
• Strategic Situation One-Pager
• Cascading Objectives
• Playing-to-Win Cascade