The board has asked for a one-page strategy and I don't know where to start.

What to do when the board wants a one-page strategy and you don't know where to start

Steve Jobs. Apple. September nineteen ninety-seven.

Jobs is two months into his return to Apple as interim CEO. The company is shipping more than a dozen product lines — Performa, Power Macintosh, PowerBook, Newton, eMate, a printer division, a server line — and losing money on most of them. The product roadmap on the wall before he arrived runs to forty-something pages.

He calls the senior team into a boardroom. Walks up to the whiteboard. Draws a two by two.

Across the top: Consumer, Pro. Down the side: Desktop, Portable. Four cells.

He turns and says the company will ship one product in each cell. Four products. Everything else stops.

An engineer points out that Apple has good people working on the products Jobs has just deleted. Jobs's reply, in substance: those good people are working on the wrong products, and that's the problem he is here to fix.

By the end of the year, the dozen-plus product lines are four — iMac in the consumer-desktop cell, Power Mac G three in pro-desktop, the iBook prototype in consumer-portable, the PowerBook G three in pro-portable. Seventy per cent of what Apple was shipping in September nineteen ninety-seven is gone by the following spring. The Newton goes. The printer division goes. The clone licences go.

Apple's first profitable quarter in years lands in early nineteen ninety-eight.

The two-by-two isn't the strategy. It is the artefact that holds the strategy in place. Every product proposal that lands on Jobs's desk for the next decade has to fit a cell, or argue for a new one. Most don't.

A one-page strategy is sometimes one page because the page is a two by two with four boxes drawn on a whiteboard.

That was Cupertino, nineteen ninety-seven. Here's yours.

Tuesday afternoon.

The email from the board arrives just after lunch — the way these things always do. One page. Strategy. Next Friday.

You read it twice. You open a blank document. You type the word "Strategy" at the top and look at the cursor for a while. Then you minimise the document, make a coffee, and tell yourself you'll come back to it after the three pm meeting.

You won't. You'll open it again on Thursday night at half past ten and write the page in forty-five minutes, and it will be worse than if you'd written it on the Tuesday afternoon you're currently in.

"The board has asked for a one-page strategy and I don't know where to start."

The feeling is overwhelmed.

There's a reason this particular request lands harder than it should. A one-page strategy isn't a small deliverable. It's a compression problem. And compression is always harder than expansion, because it asks you to decide what doesn't belong before you've finished working out what does.

First work out whether the board wants a plan or reassurance

Before you write anything, work out which of two things the board is actually asking for. Because they look identical on the email, and they need different strategies.

When the board genuinely wants the plan

Choice one: the board wants the plan. A genuine, defensible direction they can point at in the next meeting. They will read the page. They will challenge the page. They will want to know why you think what you think. In that case the move is counter-intuitive — force the team to produce fifty bad ideas in ten minutes. Not ten good ones. Fifty awful ones, fast, without stopping to evaluate. The page of rubbish is the raw material the actual plan gets carved out of, and the agony of trying to write the good version first is the thing that's been stopping you all morning.

When the board really wants reassurance

Choice two: the board wants reassurance. The subtext of the request is "tell me we're not about to fall over." In that case the move is almost opposite. Draft a one-page strategy that lists only the fragile, over-optimised dependencies you're going to remove. No new initiatives. Just subtraction. Boards are rarely reassured by new ambition. They are almost always reassured by visible reduction of the things that could go wrong.

Getting the choice right matters. A plan written for a board that wanted reassurance will read as reckless. A reassurance document written for a board that wanted a plan will read as thin.

How to let the constraints write the strategy

Three tools, in sequence. Build the strategy upwards from constraint.

Compress an arguable vision onto a single page

The first is

Product Vision Board.

Roman Pichler, a product management consultant, formalised the Vision Board around twenty eleven as part of his work helping teams move from agile delivery to strategic direction. The canonical source is his twenty-sixteen book Strategize; the board itself has been freely available on his website since the original publication.

The reason the tool exists is that most teams asked for a one-page strategy don't have a vision. They have a list of ambitions, a stack of features, and a metric they've been told to hit. Whatever ends up on the page is a smoothing-over of those three.

The unique insight is that compression is the work, not a preliminary to it. A vision that won't fit on one page isn't a vision yet — it's a set of ambitions that haven't been edited.

What you get is a vision the team can argue against, the board can read in two minutes, and the engineers can build toward. Argument-ready, evidence-anchored, single-page.

So. How to run it.

Setup. A whiteboard with five named regions. Two hours, the people who'd execute the vision in the room. No outsiders.

Users. Name them in a sentence. Not segments. Specific roles, with specific contexts. Mid-market product managers preparing quarterly reviews — not enterprise customers.

Needs. What do those users actually need? Not what we've assumed. The needs the team can defend with evidence go on the board; the assumed needs get marked as assumptions.

Product. What is this thing, in one sentence a non-specialist would understand? If the sentence breaks, the product isn't yet defined.

Goals. What does the business get from this? Revenue, retention, position. Two or three. More than three and the goals are unranked, which means none of them are.

Vision. The single sentence the previous four enable. The one a board member would read aloud at the end of the meeting and recognise as the answer to what is your product for?

The discipline is to fill the regions in that order. Filling vision first produces wishful thinking; filling users first produces strategy.

Make the logic from user to feature visible

The second is

Product Strategy Canvas.

The lineage on the Strategy Canvas is shared rather than singular — Roman Pichler, Dan Olsen, and Melissa Perri each have a version, and they all descend from the lean product movement of the early twenty-tens that emerged out of Eric Ries's Lean Startup work. The common element across the versions is the same.

The reason the tool exists is the gap between these are our users and this is what we're going to build. That gap is where most one-page strategies quietly die. The canvas exists to close it.

The unique insight is the connection itself, not the regions. Most one-page strategies hide the logical chain inside corporate language — the customer becomes a segment, the need becomes a value driver, the feature becomes a workstream. The canvas strips the language out and forces the connection to be visible.

What you get is a page where the board can trace the logic from user to feature without trusting you on it. If the chain breaks anywhere along the canvas, the strategy breaks there too — and you know to fix it before the meeting.

So. How to run it.

Users. Name them in the leftmost region. Specific. Defensible. Same discipline as the Vision Board.

Needs. What's the demonstrated need? Not the assumed need, not the need the deck implies. What evidence do you have that these specific users need this specific thing?

Solution. What are you going to ship? Concretely. Features, services, propositions. The output of the work.

Connect. This is the move that distinguishes the canvas from a regions-on-a-page exercise. Draw an explicit line from each need to each solution element. Where the lines cross cleanly, the strategy is intact. Where a solution element has no line back to a need, that element is a feature wishlist, not a strategy.

Sign-off. The page goes in front of the board. They read the lines. They challenge what doesn't connect. The challenge surfaces what's missing — which is exactly what the page exists to do.

Trace every deliverable back to a measurable goal

The third is

Impact Mapping.

Gojko Adzic, a software delivery consultant, formalised Impact Mapping in his twenty-twelve book of the same name, drawing on a longer behaviour-driven-development tradition.

The reason the tool exists is that most strategies present themselves as a list of features tied to a list of metrics — and the logical chain between the two is left implicit. The board has to trust the strategist; the strategist has to defend each feature individually. The map makes the chain explicit.

The unique insight is that the chain reads top-down like a mind map. If you can draw the four levels coherently, the strategy holds together. If you can't draw a level, the level isn't yet thought through. The drawing is the test.

What you get is a defensible visual artefact a senior reader can scrutinise without translation. The board can follow the chain from feature to goal without trusting your narrative on it.

So. How to run it.

Goal. Place the business outcome at the top of the map. Specific, measurable, time-bounded. Not grow revenue; grow ARR by twenty per cent in twelve months.

Actors. Below the goal, the people whose behaviour the goal depends on. Customers, prospects, internal teams, partners. Each named. Not the market.

Impacts. Below each actor, the change in their behaviour the goal needs. Not what you'll do for them; what they'll do that you currently don't see. Customers buy a second product within six months of the first. Sales reps include the new feature in three out of five demos.

Deliverables. Below each impact, the things you'll ship to make that impact more likely. The features. The work. The output.

The chain reads down: goal needs impacts, impacts need actors changing behaviour, behaviour change needs deliverables. If a deliverable doesn't trace back to a goal, the deliverable is on the wrong map.

That's the toolkit. We opened with a grid. Here's the phrase — the same move, in a different register.

A precedent: a strategy that is just four words

Carol Tomé. Ups. June twenty twenty.

Tomé becomes CEO of a company whose identity has been built over a century around being bigger — more parcels, more routes, more trucks, more volume. Six weeks in, on her first earnings call, she frames the strategic posture in four words: it's all about becoming better, not bigger. By her first Investor Day a year later, Better Not Bigger is the named strategic platform — three pillars beneath the phrase, five core company principles beneath the pillars, but the artefact at the top is the phrase itself.

The phrase is not a slogan. It is a test every deal at ups has to pass. Profitable volume — small and medium-sized businesses, healthcare, US domestic ground — in. Unprofitable volume — regardless of customer prestige — out.

The most visible application comes on the fourth-quarter twenty twenty-four earnings call, on the thirtieth of January twenty twenty-five. Ups announces it has reached an agreement in principle to reduce volume from Amazon — its largest customer, eleven point eight per cent of total ups revenue — by more than half by the second half of twenty twenty-six. Tomé's framing: "This was us. This was ups taking control of our destiny." And: "Amazon is our largest customer but it's not our most profitable customer. Its margin is very dilutive to the US domestic business."

The market reads it as exactly that visible. Ups stock drops fourteen per cent on the day — the worst single session of Tomé's tenure to that point.

A one-page strategy isn't always a grid. Sometimes it's a phrase, plus a willingness to absorb a bad day on the share price to prove you meant it. Tomé didn't have a Product Vision Board. She had four words — and the Amazon decision that proved the words were a strategy.

So. The question from this Playbook.

Could you describe your product strategy in three sentences to someone in the lift?

And would they be able to repeat it back — or just nod politely?