Skip to content
MIZA

Transformation8 min read

Transformation does not begin when the programme is launched

By the time a transformation has a name, a budget and a steering committee, the conditions that will decide its outcome are already in place. The question is whether anyone has looked at them.

What would leaders need to know about their organisation before approving the business case — and why is that the information they almost never have?

The launch is a milestone, not a starting point

Organisations tend to date a transformation from the moment it becomes visible: the announcement, the town hall, the first slide with a roadmap on it. That date is administratively convenient and analytically misleading. The behaviours that will slow the programme — unclear decision rights, functions that have learned not to trust each other, leaders who are already at capacity, a culture that rewards optimistic reporting — were all present before the programme existed.

What launch changes is exposure. Pressure is applied to a system that was already carrying friction, and the friction becomes visible as delay, rework and attrition. The programme is then blamed for revealing something it did not create.

McKinsey's analysis of transformation outcomes found that fewer than one-third of transformations both improved performance and sustained the improvement, and that the difference showed up early rather than late (McKinsey & Company, 2021). BCG's review of its historical sample reached a similar place from another direction: up to 75% of transformations fell short on time, value captured, or both (BCG, 2022).

What gets assessed, and what gets assumed

Before approval, most organisations assess the things that are already written down: financial case, technology dependencies, delivery sequence, resourcing. The human system is not assessed so much as assumed. It is assumed that leaders are aligned, that the middle of the organisation has capacity, that capability exists where the plan requires it, and that people will interpret the change roughly as intended.

Each of those assumptions is testable. Alignment can be examined by asking six executives, separately, what the transformation is for. Capacity can be examined by counting the change initiatives already landing on the same population. Capability can be examined against the specific work the new operating model requires, not against a generic competency framework. Interpretation can be examined by listening to how the last change is still being described.

None of this is exotic. It is simply work that has no natural owner before a programme exists — which is precisely why it does not happen.

The economics of finding out late

Correction is cheap while options are still open. A decision right that is ambiguous on a design document costs an hour to resolve; the same ambiguity discovered in month nine of implementation costs a reorganisation. This is not a novel observation in engineering, but organisations rarely apply it to their own human architecture.

The cost of transformation is not only programme spend. It is duplicated effort, low adoption, deferred decisions, regrettable attrition among exactly the people who understood the old system, and the leadership attention consumed by problems that were foreseeable.

Prosci's practitioner research has consistently associated strong change management with a higher likelihood of meeting objectives — its published benchmarking puts projects with excellent change management at seven times more likely to meet objectives (Prosci, 2023). The association is not proof of causation, and it should not be read as one. But it points at something organisations recognise: the human dimension is not a soft adjunct to delivery, it is a delivery variable.

Readiness is a diagnosis, not a survey

Readiness assessments often degrade into a pulse survey and a RAG rating. That produces a number, not an understanding. A useful diagnosis reads the system: where decisions actually get made versus where the chart says they do; which interfaces between functions generate the most rework; what the organisation has learned from previous change and what it therefore expects; where capability is genuinely thin rather than merely under-documented.

It also examines what should not change. Not everything that predates the strategy is friction. Organisations frequently dismantle the informal mechanisms that were holding delivery together, because those mechanisms were never on a diagram.

Deloitte's Human Capital Trends work reports that only 18% of UK respondents said their organisations manage change effectively (Deloitte, 2026). That is a striking level of self-assessed weakness in a capability most organisations claim to have.

Practical implications for leaders

  • Commission an organisational diagnosis before the business case is finalised, not after mobilisation.
  • Test executive alignment by asking leaders separately what the change is for — the variance is the finding.
  • Count the change already in flight against the same population before adding more.
  • Decide explicitly what will be protected, not only what will be altered.
  • Give readiness a named owner. Work without an owner does not happen before a programme exists.

Transformation does not begin when the programme is launched. It begins when someone decides to look honestly at the organisation that will have to carry it — and that decision is usually available far earlier, and far more cheaply, than it is taken.

Continue reading

Organisation

The organisation behind the strategy

Structure, decision rights and ways of working rarely appear in the strategy document. They decide whether it survives contact with reality.

Partner with MIZA

Start with the organisational question you need to answer.