By Barry Lewington | Bushey

Ask any senior executive whether they have ever been involved in a transformation programme that did not deliver what it promised, and the room goes quiet in a very particular way. It is not because the answer is no, but because the answer is almost always yes, and what follows that admission is usually a complicated mix of frustration, residual embarrassment, and the kind of hard-won pragmatism that only comes from having lived through something that cost more than it should have.

I have had that conversation more times than I can count over the past two and a half decades. What strikes me is not the frequency of transformation failure. It is how consistent the underlying causes tend to be, regardless of the industry, the scale of the programme, or the quality of the people involved.

Research on transformation success rates has been consistent for years, and it does not make for comfortable reading. Depending on which study you reference, somewhere between 60 and 80 percent of major transformation programmes either fail outright or deliver outcomes significantly short of what was originally scoped and funded. In an environment where boards are approving nine-figure investments in technology and operating model change, those odds represent an enormous concentration of risk.

And the cost of failure is not simply financial, though the financial dimension is serious enough. Failed transformations consume management attention, drain the team’s morale, and in many cases set organisations back competitively by two or three years relative to where they would have been had the programme either succeeded or never started. There is also the reputational dimension. Internally, a high-profile failure changes the appetite for subsequent investment. Externally, customers and partners notice when promised capabilities do not materialise.

What is particularly striking right now is that the stakes have risen sharply. The transformations organisations are undertaking today are not simply system upgrades or process improvements, they are fundamental changes to operating models, driven by the convergence of cloud, AI, and a genuine rethinking of how work gets done. Get this right and the competitive advantage is significant. Get it wrong and the gap between you and those who did get it right may be very difficult to close.

So why do programmes drift?

In my experience, most transformation failures do not begin with a catastrophic event, they tend to begin with drift. A scope discussion that gets resolved ambiguously, or, a dependency that is identified late, or, a stakeholder whose concerns are noted but not genuinely addressed, or, a milestone that slips by two weeks and is quietly absorbed into the plan without any real assessment of the downstream consequences.

Each of these things, taken individually, seems manageable. Taken together, accumulated over six or twelve or eighteen months, they produce a programme that is visibly in trouble but where nobody can point to the single moment when things went wrong. The response at that point is usually to add resource, compress timelines, and push harder. Sometimes that works, but more often than not, it produces the same outputs faster, without addressing the underlying causes of the drift.

The organisations I have seen navigate large transformations successfully share a different approach. They treat the detection and resolution of emerging problems as a continuous discipline, not as something that happens at quarterly steering committee reviews. They build the capability to see clearly, and they act on what they see before problems compound.

So, what do the successful programmes do?

The differences between programmes that deliver and those that do not are rarely about the technology being implemented or the methodology being followed. They are about the quality of the oversight and assurance surrounding the programme.

Successful transformations have a clear and shared definition of what success looks like, articulated in outcomes that matter to the business, not just in delivery milestones. When scope discussions arise, and they always arise, there is a framework for making decisions that is grounded in that definition. The question is not ‘can we accommodate this change’ but ‘does this change serve the outcomes we committed to, and if it does, what does it displace?’

They also have genuine independence built into their assurance model. This is perhaps the most commonly underestimated factor. Delivery teams are, by nature, optimistic. They have to be. But that optimism, if it is the only lens through which a programme’s health is assessed, creates blind spots. An independent perspective, one that is not invested in the delivery narrative and is structured specifically to surface risk, provides information that the delivery team simply cannot provide about itself.

This is the thinking that underpins the work we do through our own AssureChange® at Bushey. Not as an audit function sitting outside the programme, passing judgement, but as an integrated assurance capability that gives leaders the clarity they need to make better decisions earlier. The distinction matters. Assurance that is purely retrospective tells you what went wrong. Assurance that is genuinely embedded tells you what is going wrong while there is still time to change course.

There is a governance dimension to this that I think deserves more attention than it typically receives. Boards approve transformation investments and receive regular updates on progress. What they less frequently receive is an honest, independent assessment of whether the programme is genuinely on track to deliver its intended outcomes. The two things are not the same.

Progress updates describe what has happened. Assurance answers a different question – given everything we know about where this programme is today, what is the realistic probability that it delivers what was promised, and what would need to be true for that probability to improve?

If your board is not receiving that second kind of information, you are governing transformation on incomplete data. That is a risk that sits squarely at board level, regardless of how capable the delivery team beneath it may be.

For organisations currently mid-programme and beginning to sense that familiar unease, the starting point is an honest diagnostic. Not a formal review designed to produce a report, but a structured conversation about the gap between where the programme says it is and where it actually is. That gap, quantified and understood, is the beginning of recovery.

For those at the start of a significant transformation, the investment worth making first is not in the technology or even in the delivery methodology. It is in the assurance model. Define how you will know, throughout the life of this programme, whether you are genuinely on track. Define who has the independence and the mandate to tell you when you are not.

The cost of transformation failure has never been higher. The good news is that the causes of failure are well understood and, with the right disciplines in place, largely preventable. The organisations that recognise this before the programme starts are the ones whose names appear in the success column.

Barry Lewington is a technology strategist and Managing Director at Bushey, working with organisations to align their technology investments with business outcomes. He has been writing and speaking about enterprise technology for over 25 years.

Bushey provides independent governance and assurance for technology transformation. Through structured oversight and disciplined programme control, we ensure outcomes are achieved with clarity, accountability, and confidence, supported by specialist capability across change, project leadership, AI, Cyber, Data Centre, and M&A services. Our focus is on aligning transformation to business objectives, applying proven frameworks, and enabling secure, resilient, and future-ready environments.

#ArtificialIntelligence #AIGovernance #ResponsibleAI #DigitalTransformation #AILeadership #EnterpriseAI #TechnologyStrategy #GovernanceRiskCompliance #BusinessTransformation #InnovationLeadership