Roughly seven in ten transformations fail. Almost none of them fail on strategy. They fail on the joinery between the strategy and the delivery team — the linkage layer that translates intent into weekly operating decisions.
Why do so many transformations stall at the seam between strategy and delivery — and what closes the gap?
The reversal
The dominant narrative treats transformation failure as an execution problem downstream of a good strategy. Cross-industry research on transformation outcomes12 tells a more precise story: failure is concentrated at the linkage layer — the artefacts and cadences that translate a strategic decision into the specific operating decision an operations lead is making this Tuesday. Missing linkage produces a familiar pattern: the board reviews strategy quarterly, the delivery team reviews milestones weekly, and the two conversations never intersect. The remediation is not more strategy or more delivery discipline; it is the design of the joinery.
The insight stack
What actually moves the P&L
Convert strategic bets into named operating decisions
Every strategic bet must be translated into a specific set of operating decisions that will be made differently as a result — pricing bands moved, hiring priorities changed, supplier terms renegotiated, product roadmap resequenced. If a strategic bet does not name at least three operating decisions that will change inside the next quarter, it has not yet crossed the linkage layer. It is still a slide.
Assign each strategic outcome to a named owner outside the transformation office
Transformation offices are useful for programme discipline but structurally unsuited to owning outcomes. Outcomes belong to line-management owners who will still hold the accountability after the transformation office is dismantled. The linkage document names the outcome, the owner, and the operating cadence in which the outcome will be reviewed — separately from the programme milestone review.
Run a monthly linkage review distinct from strategy and delivery reviews
The linkage review does not debate strategy and does not track milestones. It asks a narrower question: are the operating decisions the strategy required actually being made, at the pace the strategy required, by the owner the strategy named? Monthly cadence catches drift before it becomes structural. Quarterly cadence, in almost every benchmark, does not.
Rehearse the linkage before the transformation launches
The linkage layer needs to be exercised before it carries live outcomes. A pre-launch rehearsal — one strategic bet, tracked through to the operating decision it produces, in an off-cycle test — surfaces the gaps in the joinery when they are still cheap to fix. Skipping the rehearsal is a common false economy that costs six-to-nine months of programme calendar to recover.
Retire linkage artefacts when the outcome moves into business-as-usual
The linkage layer is a scaffold, not a permanent fixture. When an outcome has been delivered and absorbed into the normal operating cadence, the linkage artefact is retired formally — otherwise the transformation office quietly persists as a shadow governance layer and the operating team never fully reclaims ownership. Retirement is a milestone worth celebrating and worth documenting.
Case example
A £180M financial services group closing a stalled transformation
The problem: an eighteen-month transformation programme had produced strong strategic clarity, credible workstreams, and a stalled P&L. The board reviewed strategy quarterly; the programme office reviewed milestones weekly. Not one of the strategic bets had a corresponding operating decision on the operations lead's weekly agenda. A linkage layer was installed retrospectively — each strategic bet translated into three-to-five operating decisions with named owners, a monthly linkage review distinct from the milestone review, and a decision-record system that captured whether the operating decisions were being made at the required pace. Six months later, three of the four strategic bets had moved from stalled to delivered against P&L, the programme office had been reduced by 40%, and the linkage review was formally rolled into the standard operating rhythm.
Mini-playbook
Six moves to install a working linkage layer
Translate every strategic bet into three-to-five named operating decisions.
Assign each outcome to a line-management owner, not to the transformation office.
Run a monthly linkage review distinct from strategy and milestone reviews.
Rehearse the linkage once, on a single bet, before formal launch.
Publish a decision-record for every operating decision the strategy required.
Retire linkage artefacts formally when outcomes are absorbed into business-as-usual.
How Strategy Labs installs this
Anchored to Transformation Roadmap
Strategy Labs installs the linkage layer inside CAE as a formal stage between the strategy artefact and the operating cadence. The seven-stage engagement lifecycle carries the joinery — strategic bet, operating decisions, named owner, review cadence, decision record — as first-class deliverables, not as programme-management by-products.
Baseline diagnostics, decision-latency analysis, and cadence-benchmarking run inside PDC, so the linkage layer is calibrated against primary evidence on how strategy actually reaches the operating floor in the specific organisation — not against generic transformation templates.
Frequently asked
Related questions executives ask
- Isn't linkage the transformation office's job?
- Only in the sense that the transformation office builds the scaffold. Ownership of outcomes must sit with line management from day one — otherwise the outcomes disappear when the office is disbanded.
- How many linkage artefacts is too many?
- One per strategic bet, each covering three-to-five operating decisions, is usually enough. Beyond eight or ten strategic bets, the transformation itself is over-scoped and needs re-sequencing before linkage work begins.
- When do we retire the linkage layer?
- When the outcome has been sustained in the normal operating cadence for two full quarters. Retirement earlier tends to reverse the outcome; retirement later leaves shadow governance that competes with business-as-usual.
Over to you
For your last strategic bet, which three operating decisions were supposed to change this quarter as a result — and how many of them actually moved?
Continue reading
More Transformation Systems briefings
Why do most transformation programmes fail in execution, not in design?
Most transformation programmes fail not because the strategy was wrong, but because the programme was a project list held together by a Gantt chart. Architecture, not activity, is what compounds.
Read briefingWhy does 'benefits tracking' consistently overstate transformation value?
Every transformation has a benefits tracker. Almost none has a value-realisation system. The gap is why most boards discover, two years in, that the reported £40M and the audited £11M are describing the same programme.
Read briefingIn what order should transformation capabilities actually be installed — and why does most sequencing get this wrong?
Every transformation roadmap has a list. Very few have a sequence. The list ranks capabilities by importance; the sequence ranks them by dependency — and the difference decides whether the programme compounds or stalls.
Read briefing
Discussion
(…)Comments are moderated before appearing. Your email is only used for moderation and is never shown publicly.
Loading discussion…