The Cost of the Whiteboard: Protecting Delivery During Strategy Season

November has a particular rhythm in UK organisations. Delivery teams are closing out the year, finance is chasing commitments, and the diary begins to fill with sessions labelled strategy, planning and 2027. The intent is sound. The cost is rarely counted.

Planning is not free. It consumes the same finite hours as delivery, and those hours are usually taken from the people closest to the work. A planning tax is charged quietly, through preparation documents, away-days, review meetings and the rework that follows a decision nobody was authorised to make. Achievers should budget for that tax as deliberately as they budget for anything else.

The planning tax, defined

The planning tax is the delivery capacity absorbed by planning activity that does not itself deliver. It includes the obvious: the two-hour meeting, the half-day away-day, the pre-read. It also includes the less obvious: the afternoon spent rebuilding a timeline because a planning session changed a priority without changing the resources, or the senior person pulled into a workshop that could have been a one-page note.

A simple calculation makes the cost visible. Take the number of people in the room, multiply by the hours involved, and add preparation and follow-up. Ten people in a four-hour planning session, with two hours of preparation each, is sixty hours before anyone has written a single action. For a small team, that is a working week. It may still be worth spending, but it should be a choice rather than an accident.

The point is not that planning is waste. The point is that planning competes with delivery for the same constrained capacity. In the final quarter, when delivery commitments are at their most concrete, that competition is sharpest.

Cap the meetings, not the thinking

A planning budget is the simplest control. Give each team a fixed number of planning hours per person per week during the planning season, and treat that budget as spend. A reasonable starting point is no more than one day in ten of available time, held centrally by the team leader. Once the budget is used, further planning requests are deferred, delegated or resolved asynchronously.

This is not an argument against thinking ahead. It is an argument for making the thinking deliberate. A cap forces the question that open diaries avoid: which planning conversations are likely to change what we do, and which are simply reassuring? If a planning conversation needs more than its allocated time, it usually needs a smaller group or a clearer decision, not a larger diary.

Protect delivery first. Before planning slots are offered, diarise the delivery milestones that must be met in November and December. Those blocks are not flexible. Planning meetings fit around them, not the reverse. Publish the protected periods so that requests can be tested against them.

Who actually needs to be in the room

Planning meetings expand because attendance is used as a proxy for importance. It is not. Three roles are usually enough: the person who owns the decision, a representative of the delivery work that will be affected, and someone able to challenge the proposal on evidence. Everyone else can contribute before or after.

The useful test is consequence, not seniority. Who will have to change what they do if the decision goes one way rather than another? Who can commit resources? Who can say no? If a participant cannot answer any of those questions, their presence is probably observational. That is not a reason to exclude them from the process, but it is a reason to exclude them from the room.

For large teams, a planning surgery works better than an open invitation. The decision owner holds short slots, receives a pre-read, and gives a yes, no or not-yet. This reduces attendance without reducing input.

The test that separates a decision from a document

Before accepting or calling a planning session, ask three questions. What decision will be different at the end? Who will make it? What will we stop, start or resource differently? If the answers are vague, the session is likely to produce a document rather than a decision.

A document can be useful. It should not be disguised as a decision meeting. If the output is a proposal, ask for it in writing and review it in thirty minutes. If the output is a decision, name the decision owner and the options in advance. A planning session that cannot name its decision is a reading group with a budget.

This test also protects the people doing the delivering. They are often invited to planning sessions because they know how the work actually happens, but they are rarely given the authority to settle the trade-offs. The result is a meeting that consumes their time and returns the decision to them unresolved.

Make delivery protection visible

A planning budget works best when it is visible. Publish a short delivery protection agreement for the final quarter: the milestones that cannot move, the hours reserved for delivery, the days available for planning, and the named person who arbitrates conflicts. Keep it to one page.

Weekly review matters. Compare planning hours spent with the budget, and compare delivery progress with the protected milestones. If planning is overspending, escalate the cause rather than quietly absorbing it. If delivery is slipping, reduce planning activity before asking the team to absorb the difference. The aim is not to win an argument about meetings. It is to make the trade-off explicit.

A short checklist for November

• Set a planning budget per person or team, and hold it centrally.
• Protect delivery milestones before offering planning slots.
• Apply the decision test to every planning session.
• Limit attendance to the decision owner, a delivery representative and a challenger.
• Publish planning windows and protected delivery periods.
• Review planning spend and delivery progress weekly.

Planning matters. Next year's strategy will need attention, and the final quarter will need finishing. The risk is that the second is quietly funded by the first. Budgeting for planning does not make an organisation less ambitious. It makes the ambition honest about what it costs.