The gap between strategy and execution

Organisations invest significantly in the design of transformation. Strategy workshops, diagnostic reports, operating model reviews, and programme business cases — all of this work contributes to plans that are typically articulate, well-reasoned, and genuinely compelling as documents.

The implementation record, however, tells a more sobering story. A substantial proportion of transformation programmes fail to deliver their intended outcomes. Not because the strategy was wrong, but because the distance between what was designed and what was actually implemented was too great to bridge with the approaches that were deployed.

Understanding why transformation stalls at implementation requires looking at the conditions that are in place when execution begins — and at the specific patterns that distinguish programmes that deliver from those that fall short.

The mobilisation problem

The first and most consistent point of failure in transformation is mobilisation — the period between the sign-off of a programme plan and the establishment of effective delivery momentum.

Mobilisation is consistently underestimated in both time and complexity. The assumption is often that the work of implementation begins when the plan is approved. In reality, a significant body of enabling work needs to happen before meaningful progress can be made — establishing governance, allocating resources, securing the operational capacity of the people who will do the work alongside their day jobs, resolving the dependencies that the plan identified but did not fully address.

Programmes that rush through mobilisation to demonstrate early delivery progress typically pay a significant price in the implementation phase. The foundations that were not properly laid — the unclear accountabilities, the unresolved dependencies, the governance structures that are not yet functioning — create friction that compounds as the programme proceeds.

Capacity and the day job problem

Transformation is almost universally delivered by people who have another job to do. The operational leaders and subject matter experts who are needed to drive implementation are also responsible for running the business they are being asked to transform. The tension between these two demands is one of the most reliably destructive forces in any major change programme.

When business-as-usual pressure intensifies — when a client emergency, a financial period close, or an operational incident demands management attention — it is almost always the transformation work that yields. This is rational in the short term. It is systematically damaging to the programme over time.

Organisations that manage this tension most effectively make deliberate, visible choices about capacity. They are explicit about the time commitment that effective participation in the transformation requires. They create protected capacity for the people in the most critical delivery roles, rather than assuming those people will find the time. And they design the programme around the real capacity constraints of the organisation rather than the theoretical capacity implied by a resource allocation on a Gantt chart.

The change management gap

Many transformation programmes are designed with a strong analytical and process focus and a correspondingly weaker focus on the people and behaviour dimensions of change. The logic of the change — why it makes sense, what it will improve, how it will work — is well-developed. The work of actually shifting how people behave, what they prioritise, and how they interact with new processes and systems receives considerably less rigorous attention.

This imbalance is one of the most common reasons that transformation fails to embed. New processes that are technically well-designed but that have not been adopted by the people they were designed for do not improve performance. New systems that have been implemented but not embedded into how teams actually work generate costs without benefits. Structural changes that have been made on paper but that have not been followed by a genuine shift in operating practice leave the organisation's performance largely unchanged.

Effective change management in transformation is not primarily a communications and training exercise — though both have their place. It is a sustained effort to understand the specific behaviours that the transformation requires, identify the specific barriers to those behaviours in the current environment, and design targeted interventions that address those barriers. That work requires proximity to the people who will be expected to change, and a willingness to adapt the approach when the initial design proves insufficient.

Governance that loses the thread

Programme governance structures are designed to provide oversight, resolve issues, and maintain strategic alignment as implementation proceeds. In many programmes, the governance that was established at the outset gradually loses its grip on the programme as implementation complexity increases.

The steering committee that was convened monthly to provide strategic direction begins to function as a reporting forum — receiving updates on progress against plan without exercising genuine oversight of whether the plan itself remains fit for purpose. Programme issues escalate into governance meetings but are not resolved there, returning to the delivery team without the decision or direction they require. Senior sponsors whose engagement was assured during the approval process become less available as the programme competes with other priorities for their attention.

When governance loses the thread, the programme loses the strategic direction and decision-making support that complex implementation requires. Delivery teams make their own interpretations of contested questions. Trade-offs that should be resolved at the senior level are resolved at a level without adequate authority. The programme gradually diverges from the strategic intent it was designed to serve.

Sustaining momentum

Transformation programmes that sustain momentum share a set of conditions that are not always present in those that stall. They have senior sponsors who remain genuinely engaged in the programme — not just informed of it. They have a governance structure that is actively used to resolve issues rather than to receive reports. They have dedicated delivery capacity that is protected from the routine demands of business-as-usual. And they have a programme leadership team that is willing to name problems honestly and respond to them decisively rather than managing the narrative while allowing the underlying issues to compound.

The gap between a transformation programme that delivers and one that stalls is often not a gap in the quality of the plan. It is a gap in the quality of the conditions established for implementation — and in the commitment to maintaining those conditions through the difficulty and ambiguity that any genuine transformation will encounter.