The failure rate on digital transformation initiatives is well documented. Depending on which research you read, somewhere between 70–85% of large digital transformation programmes fail to deliver their stated objectives. Having been directly involved in a number of these — on the leadership side, the advisory side, and occasionally the uncomfortable post-mortem side — I've noticed the explanations in the room rarely match the explanations in the boardroom. Here are three patterns I've seen close up, with names and identifiers changed but the dynamics entirely intact.
Failure 1: The platform that no one owned
A multi-site hospitality business invested significantly in a new central technology platform — a single system that was supposed to bring together reservations, customer data, loyalty, and operations. The technology worked. The implementation ran broadly on time and on budget. And then, eighteen months later, half the estate was still running the old system alongside it and nobody could explain clearly what the new platform was actually for.
What went wrong: the programme had a technology owner but no business owner. There was a director of IT who owned the platform implementation. There was no one at executive level whose success metric was whether the business actually used it to do things differently.
Every time an operational challenge arose — and in a multi-site business, operational challenges arise constantly — the platform became the explanation rather than the solution. "The new system doesn't support that." "We'll have to wait until the platform is stable." The technology became an obstacle rather than an enabler because no one was accountable for bridging the gap between what the platform could do and what the business needed to do.
What a different outcome required: A named executive whose success was defined by business outcomes, not system uptime. Someone who sat on both sides of the table — technology capability and operational need — and was empowered to make the difficult trade-offs between "perfect implementation" and "getting the organisation to change how it works."
"The technology was fine. The failure was that no one was accountable for the gap between what it could do and how the business actually worked."
Failure 2: The strategy that lived in the deck
A professional services firm hired a leading consultancy to develop a digital strategy. The output was thorough: a 120-slide presentation, a detailed roadmap, a prioritised initiative list, and a compelling narrative about the firm's digital future. The board approved it. The CEO presented it to the partners' meeting. It was well received.
Eighteen months later, almost nothing had changed. The strategy had been developed largely by the consulting team, with inputs from a handful of senior leaders. It reflected what a consulting firm understood about digital strategy, filtered through what a few senior partners were willing to say in interviews. It did not reflect how the firm actually won business, why partners behaved the way they did, or what the real blockers to change were at operational level.
When implementation began, the resistance was immediate and effective. Partners who hadn't been genuinely involved in the strategy's development had no ownership of its conclusions. Initiatives that required partners to change how they managed client relationships — the most valuable change available — stalled at first contact with the partnership structure.
What a different outcome required: The strategy needed to be built with the people who would implement it, not presented to them. Not a consultation exercise, but genuine co-creation with the people whose behaviour needed to change. Slower to develop, significantly more durable to execute.
Failure 3: The urgent transformation that solved yesterday's problem
A retail business responded to a sharp decline in footfall by launching an e-commerce transformation programme. The programme was well-funded, executive-sponsored, and genuinely ambitious. Two years later they had a functional e-commerce operation. They had also spent two years catching up to where their competitors had been at the start of the programme, while those competitors had been building capabilities in personalisation, supply chain integration, and omnichannel experience that the transformation programme hadn't anticipated.
The failure here wasn't execution — the e-commerce capability was real. The failure was that the transformation was defined by the crisis in front of them rather than the competitive landscape ahead of them. The programme answered "how do we stop the bleeding?" when the more important question was "what does winning look like in three years and what do we need to build today to get there?"
By the time the platform launched, the competitive bar had moved. They were adequately competitive where they'd been failing, and still materially behind where the market was heading.
What a different outcome required: A clearer distinction between the immediate defensive move — build basic e-commerce capability — and the strategic ambition. The former needed to be fast and functional. The latter needed genuine foresight about where the category was going, not just where it had been. These are different projects requiring different timelines, different talent, and different success metrics.
The common thread
What connects these three failures isn't technology. In each case, the technology was either working or workable. The failures were organisational: unclear ownership, insufficient genuine buy-in from the people whose behaviour needed to change, and strategy defined by the present problem rather than the future opportunity.
The uncomfortable implication is that most digital transformation failures are leadership failures. Not failures of technical expertise or budget or timing — failures of the organisational capacity to pursue sustained, difficult change while simultaneously running a business. That's a harder problem to solve than buying a better platform. It's also the only problem worth solving.
Navigating a transformation that isn't moving the way it should?
Sometimes the most useful thing is a candid conversation with someone who's seen these patterns before. Let's talk →
