From Strategy to Delivery: The Handover That Never Happens
The most expensive twenty minutes
There is a moment in every strategy programme where the thinking stops and the doing starts. In most organisations that moment lasts about twenty minutes, consists of a slide pack being emailed to delivery leaders, and costs more than any other single event in the programme.
The strategy team knows why option B was rejected, which assumptions are load bearing, and which numbers are estimates rather than commitments. Almost none of that survives the handover. Delivery teams inherit conclusions without reasoning, then spend the next two quarters reconstructing it, usually incorrectly.
What a proper handover contains
The intent. One page describing the outcome the organisation is trying to create and why it matters now. Written so that a delivery lead can make a small trade off decision without asking anyone.
The decisions already made. A list of settled choices with the criteria used. This prevents relitigation and, just as importantly, tells delivery teams which questions are genuinely still open.
The assumptions. Every strategy rests on assumptions about price, demand, capability or timing. Name them, name who owns monitoring each one, and state what would need to change for the strategy to be revisited.
The measures. Lagging measures for the board and leading measures the delivery team can influence this quarter. Where a measure does not yet exist, say so and name who will build it.
The constraints. Budget, headcount, systems and regulatory limits. Delivery teams that discover a constraint late treat it as an obstacle. Teams that know it up front design around it.
The stop list. What the organisation will cease doing to release the capacity this work requires. This is the element most often omitted and the one that most reliably determines whether the plan is real.
Attend the handover
A written handover is necessary and not sufficient. The executive sponsor should attend a working session with the delivery leads, and should expect to be challenged. If a delivery lead says the timeline is not achievable with the named resources, that is the cheapest piece of information the programme will ever receive. Hearing it in month nine costs a great deal more.
Where StratDo® formalises this
DIRECT exists for precisely this purpose. It converts the output of DECIDE into intent and OKRs, so what leaves the strategy phase is not a conclusion but an instruction set that a delivery team can act on without supervision. DO then runs the work against that instruction set, and REFLECT feeds what was learned back into the next cycle.
Organisations that treat DIRECT as a formality get a document. Organisations that treat it as the transfer of accountability get delivery.
A simple test
Ask three delivery leads, separately, two questions: what outcome is your work meant to create, and what did we decide not to do? If the three answers do not broadly match, the handover has not happened yet, whatever the programme plan says.
Run the session again. It takes half a day and routinely saves a quarter.
Want to discuss these ideas for your organisation?
We work with senior leaders to turn strategic insight into measurable outcomes. Let's start a conversation.