Work it through: Running Annual Planning
Annual planning as a chain of decisions instead of a writing exercise: surface the assumptions, make the real choices including what to stop, draw the logic on one page, then commit to numbers that report back every quarter.
Seven steps, in the order the playbook gives them. Your work stays in this browser until you save it to a file.
Your ducks
Start with what the people believe, what the paperwork says and what actually happens. The issues where your ducks disagree are the ones to carry into the homework.
You have not filled in the ducks sheet yet.
The homework
What has to be found before any of the four frameworks is worth running. Put a name and a date against each one, and tick it when you have it in your hands.
The ducks
For SWOT Analysis
For Playing to Win (Strategy Choice Cascade)
For Strategy Maps
For Objectives and Key Results (OKRs)
Step 1 of 4: SWOT Analysis
Open with SWOT precisely because it is quick and everyone knows it. The value at this stage is getting the team's conflicting, unstated assumptions onto a single page before the real decisions start. Keep each quadrant short and evidenced, and pay attention to the pairings: strengths against opportunities show where to attack, weaknesses against threats show where you are genuinely exposed. Treat anything unevidenced as a hypothesis. A strengths list that filled up easily usually means the bar was set at 'things we do'.
Watch forSWOT is the warm-up act, and the trap is mistaking it for the strategy; a full grid is a shared picture, nothing more.
0 of 4 blocks filled
Step 2 of 4: Playing to Win (Strategy Choice Cascade)
This is where planning becomes choosing. Five linked questions: winning aspiration, where to play, how to win, what capabilities, what management systems. The middle pair does the heavy lifting, and the two must be decided together, since a where without a how is a wish. Look hard for the words 'we will not'. In my experience an annual plan without a stop-doing list is a to-do list wearing a suit, and the calendar will treat it accordingly.
Watch forWatch for an aspiration everyone applauds sitting on capabilities nobody has funded; that is a poster, and posters do not compete.
0 of 5 steps filled · 0 of 4 inputs in hand
What comes out, and how to read it
A one-page cascade of five nested choices, each consistent with and reinforcing the others, plus the shortlist of conditions that would have to be true for the strategy to win and the measures that watch them.
- Read where-to-play and how-to-win first and as a pair; they do the heavy lifting, and the other three boxes exist to motivate, enable and sustain them.
- Test coherence in both directions: an inspiring aspiration with unfunded capabilities is a poster, and strong capabilities serving no stated advantage are overhead.
- Look for the words 'we will not'. A cascade without exclusions has not made choices.
- Check that at least one tracked condition could realistically fail; a strategy whose assumptions are all safe is describing the past.
Step 3 of 4: Strategy Maps
The choices now need to travel. A strategy map puts the whole logic on one page: the capabilities you will build, the processes they enable, the customer outcomes those deliver, and the financial results that follow, with the cause-and-effect arrows drawn in where they can be challenged. Drawing the arrows is the point. An objective with no arrow leaving it is a hobby, and it is far cheaper to discover that in the planning room than in next year's accounts.
Watch forThe top band is an effect; if your plan's first move is 'grow revenue', the map is upside down.
0 of 6 steps filled · 0 of 5 inputs in hand
What comes out, and how to read it
A one-page causal model of the strategy: objectives in four stacked perspectives connected by explicit bottom-up cause-and-effect arrows, ready to be measured through a balanced scorecard and communicated across the organisation.
- Read the map bottom-up, the direction the arrows run: capabilities enable processes, processes deliver the customer value proposition, and customer outcomes produce the financial results. The top band is an effect, never a lever.
- Interrogate the arrows before the boxes. An objective with no arrow leaving it is a hobby; an arrow with no mechanism behind it is a hope; and the strategy is only as strong as its weakest defended link.
- Treat the whole map as a testable argument. When results contradict a link, the finding is strategic intelligence about the business, and redrawing the map is the system working.
Step 4 of 4: Objectives and Key Results (OKRs)
Finish by converting the choices into quarterly commitments: a handful of objectives, three to five measurable key results each, published where every team can see them. Publication is half the mechanism, because cross-team collisions surface in week two instead of at the deadline. Score honestly at the end of each cycle and read the misses for information. A perfect scorecard is a warning that the targets were set too low, which was Grove's view and is also mine.
Watch forResist giving every team OKRs for everything they do; business-as-usual does not need a stretch goal, and drowning the breakthrough work in routine metrics is how focus dies.
0 of 6 steps filled · 0 of 4 inputs in hand
What comes out, and how to read it
A published, measurable statement of what the organisation is trying to change this cycle, a live view of progress against it, and an end-of-cycle scorecard whose misses carry as much information as its hits.
- A perfect scorecard is a warning, not a triumph. Grove treated consistent full marks as evidence the targets were set too low, and the convention that 0.7 on a stretch key result is success exists to protect ambition.
- Read the misses for information. A 0.3 with a clear account of why is worth more than a 0.9 nobody can explain, because it tells you something about the business you did not know in week one.
- Look at where OKRs originated. If everything flowed top-down, the alignment stage did not happen and next quarter's ownership problem is already visible.
The review date
Set the date you will come back and ask whether it worked. Put it in your diary; this site will not remind you.
Your work stays in this browser until you save it. The file is yours; load it here on any machine.