From strategy to execution: why institutions lose momentum

Almost every discussion of transformation opens with the same claim: that seventy per cent of transformations fail. It is repeated in board papers, conference keynotes and consulting proposals. It is also, on close inspection, unsupported.

The figure traces back to a 1993 book on business reengineering, where a range of fifty to seventy per cent was offered explicitly as an unscientific estimate. A peer-reviewed review published in the Journal of Change Management in 2011 examined five separate published instances of the seventy per cent claim and found none of them resting on valid empirical evidence. The number survived anyway, because it is memorable and because pessimism travels well.

This matters more than pedantry. A statistic that frames transformation as inherently doomed invites fatalism, and fatalism is expensive. It encourages leaders to treat delivery failure as weather rather than as design.

The measured evidence tells a more useful story. Successive global surveys applying a demanding two-part definition of success — that a transformation both improved performance and equipped the organisation to sustain the improvement — have found success rates clustering between roughly one in five and one in four. Digital transformations specifically scored lower still, at sixteen per cent in 2018.

So the base rate is genuinely low. But the same body of research contains a finding that is rarely quoted alongside it. In earlier McKinsey research, organisations reporting action across all five transformation stages — setting goals for both performance and organisational health, assessing capability honestly, designing the initiatives, executing them, and building mechanisms to sustain the change — reported a seventy-two per cent success rate.

The implication is more useful than the headline number: low average success is not inevitable. The completeness of the execution system matters.

The strategy is approved. Leadership aligns around the direction. The organisation launches initiatives, establishes steering committees and begins reporting progress. For a period, activity accelerates.

Then momentum starts to fade. Decisions take longer. Priorities multiply. Initiatives drift from their original intent. Accountability becomes less clear. Teams continue to report progress, but the organisation increasingly struggles to distinguish movement from motion.

This is one of the most persistent challenges in institutional transformation: the distance between deciding where to go and building an organisation capable of getting there.

A strong strategy answers fundamental questions. Where to play. What to prioritise. What capabilities to build. What to stop doing. What must become different for the institution to succeed.

But once those choices are made, a different discipline begins. Execution requires translating strategic intent into hundreds of decisions across structures, budgets, people, processes and day-to-day priorities.

That translation is where organisations struggle, and it struggles in four specific places. The budget, which determines what is actually resourced. The structure, which determines who is accountable. The calendar, which determines what leadership attends to. And consequence, which determines whether any of it is taken seriously.

When a strategy changes but those four layers do not, the institution has adopted a new destination without changing the machinery that determines how it moves. And when the strategy and the machinery point in different directions, the machinery usually wins.

There is a simple test of whether a strategy has been adopted rather than merely approved: compare this year’s resource allocation with last year’s. If the pattern is substantially unchanged, the strategy has not yet been funded, whatever the board minutes record.

This is not a rhetorical point. It is one of the better-evidenced findings in corporate strategy. Analysis of roughly 1,500 large companies across two decades found that most awarded each business in their portfolio a near-constant share of corporate capital, year after year. Allocation patterns were remarkably stable.

The performance consequence was significant. Companies that reallocated more dynamically delivered total shareholder returns of roughly ten per cent annually against approximately six per cent for more static reallocators. Compounded over twenty years, the more active reallocator ends up worth roughly twice as much.

The behavioural gap is stark. Around eighty-three per cent of senior executives identify shifting resources as the most important management lever for growth. Yet a third of companies move around one per cent of capital between businesses from one year to the next. Everyone knows. Almost nobody moves.

The reason is rarely analytical. Budgets are negotiated between people who will still be in the room next year, and last year’s allocation is the only number nobody has to justify. Inertia is not a failure of intelligence. It is the default output of a process where the burden of proof sits on change rather than continuity.

Transformation programmes are usually organised around projects: a digital initiative, a restructuring programme, a new commercial model, a cost transformation, a capability-building effort. Individually, each may be sensible. But strategies are rarely delivered by individual initiatives. They are delivered by the interaction between them.

A new operating model may depend on new capabilities. Those capabilities may require different recruitment and incentives. The commercial strategy may depend on technology that has not yet been funded. New decision rights may require governance changes that have not yet been implemented.

When these interdependencies are not actively managed, execution fragments. Every initiative can appear green while the transformation itself remains stuck — because each programme is reporting honestly on what it controls, and nobody is reporting on what sits between them.

This reporting paradox is diagnostic. If the portfolio dashboard is healthier than the outcome, the institution is measuring effort rather than progress, and the gaps are where value is leaking.

The challenge is not project management. It is enterprise orchestration. Someone must continually connect the strategy to the portfolio of change, identify dependencies, resolve competing priorities and ensure decisions in one part of the institution reinforce rather than undermine another.

Practically, that means maintaining a dependency register with the same seriousness as a risk register — and distinguishing between three kinds of dependency that behave very differently.

Another common source of lost momentum is collective accountability. When everything is everyone’s responsibility, very little truly belongs to anyone.

Transformation governance frequently creates layers of committees, working groups and programme structures intended to strengthen oversight. Yet additional governance does not automatically create greater accountability. Sometimes it does the opposite.

Issues move between forums. Decisions are escalated rather than made. Executives become sponsors of initiatives without genuinely owning outcomes. Programme teams become responsible for reporting progress while business leaders remain responsible for operations. The result is an uncomfortable space between the two.

Successful execution requires clarity on four questions: who owns the outcome, who has authority to decide, what success looks like in measurable terms, and what happens when progress falls behind. Those answers should be obvious throughout the organisation. If they are not, execution will slow.

The fourth question is the one most often left unanswered. An institution in which falling behind carries no consequence has not created accountability; it has created reporting.

More governance does not always create more accountability. Sometimes it creates places for accountability to hide.

Transformation is often treated as an extraordinary event alongside normal operations. That distinction is dangerous. If the strategy genuinely matters, executing it must become part of the way the institution is managed.

Leadership agendas should reflect strategic priorities. Capital allocation should follow them. Performance conversations should test them. Management information should show whether the organisation is progressing against them.

This creates an institutional rhythm: a recurring cycle through which priorities are reviewed, decisions are taken, resources are moved and accountability is reinforced. Without that rhythm, transformation depends on periodic bursts of leadership attention. With it, execution becomes part of the institution itself.

The design principle is that each cadence should have a different job. A weekly forum that reviews strategic performance is redundant; a quarterly forum that unblocks operational issues is too slow. When every meeting does everything, nothing gets decided anywhere in particular.

Large transformations also rarely stall because of one major unresolved question. They stall because of dozens of smaller ones: which project gets funding, who owns a new capability, whether a legacy initiative can be stopped, which customer segment takes priority, whether a role sits centrally or in the business.

A well-designed rhythm exists precisely to clear that backlog before it accumulates into drift.

Leadership teams frequently launch transformation on top of an organisation already operating near capacity. The same people responsible for delivering today’s results are asked to redesign tomorrow’s institution. Something eventually gives.

Transformation cannot be treated purely as an aspiration exercise. It requires explicit choices about capacity. Where will the organisation free up its strongest people? What work will stop? Where are external capabilities temporarily required? Which roles need to be strengthened permanently? How much management attention can realistically be devoted to change?

The most constrained resource is almost never capital. It is the attention of perhaps fifty people, and their calendars are a capital asset that is rarely accounted for as one. An institution that would never approve unfunded capital expenditure routinely approves unfunded management attention.

Transformation competes for scarce institutional resources just like any other strategic priority. If those resources are never explicitly allocated, execution becomes dependent on individual heroics. That may work temporarily. It is not an operating model.

Most institutions also have well-developed mechanisms for starting things and none for stopping them. A stop list — reviewed with the same seriousness as the investment list, and owned by the same forum — is among the cheapest interventions available and among the rarest.

Nor is the objective simply to create a better transformation office. Dashboards, reporting and governance are useful tools, but they are not the destination. The real test is whether strategic execution migrates into normal management systems, and whether the institution becomes better at translating choices into outcomes.

A particular version of this problem affects institutions whose mandates are measured in decades while their funding and leadership cycles are measured in years. National development programmes, sovereign investment vehicles, regulators and large public institutions all share this structure.

Three mismatches recur. Multi-year delivery commitments funded through annual appropriation cycles, so that programme continuity depends on a decision taken twelve months at a time. Leadership rotation faster than delivery timelines, so that the people who committed to an outcome are rarely the people held to it. And accountability defined at project level while the mandate is defined at portfolio level, so that everything can be delivered while nothing is achieved.

None of these is a failure of intent. They are structural features, and they respond to structural answers.

Multi-year commitment envelopes — where outer years are indicative rather than guaranteed but explicitly stated — allow delivery organisations to plan and contract sensibly without removing fiscal control. Portfolio-level reporting, in which the primary unit of account is the outcome rather than the project, prevents the green-dashboard paradox.

Decision service levels at ministerial or board level convert the most common source of delay into a managed metric. And a small permanent secretariat, insulated from leadership rotation, can hold the institutional memory of why choices were made.

The underlying principle is the same as in the corporate case. The institution must be built to move at the speed its mandate requires, not the speed its calendar happens to impose.