Digital transformation has become one of the most used — and most misunderstood — phrases in business. Boards commission it. CEOs announce it. Consultants sell it. And yet, depending on whose research you read, somewhere between 70 and 85 percent of transformation programmes fail to deliver on their original objectives.
Having led technology transformation across financial services organisations for over two decades, I have seen both sides of that statistic. I have delivered programmes that genuinely changed how businesses operated. I have also watched well-intentioned initiatives collapse under the weight of their own ambition. The difference, almost without exception, comes down to four patterns that appear time and again — not as isolated problems, but as a predictable sequence of failure.
This is what I have learned. More importantly, this is how to avoid it.
The Technology-First Trap
The platform is chosen before the strategy is defined
A vendor makes a compelling pitch. A competitor has just announced a cloud migration. The board wants to be seen moving. Before anyone has asked what problem they are actually trying to solve, the organisation has signed a contract and begun implementation. The technology becomes the strategy — and that is where things start to unravel.
Strategy first, technology second. Always. Before any vendor conversation, define what a successful outcome looks like for the business in commercial terms. What decisions will be faster? What costs will reduce? What customer experience will improve? The technology should be selected because it best delivers those outcomes — not because it was presented persuasively at the right moment.
In financial services, I saw this pattern play out repeatedly with platform modernisation programmes. Institutions would select a platform based on market position or the latest industry hype, only to discover months later that the platform's assumptions about how a business should operate bore little resemblance to how their business actually worked. The result was not transformation. It was an expensive customisation project that left the organisation more constrained than before, and significantly lighter in the pocket.
The technology should answer the strategy. When the technology becomes the strategy, the programme is already in trouble.
The People Problem Nobody Talks About
Underestimating the people and culture dimension
Transformation budgets are allocated almost entirely to technology and project management. Change management, training, and cultural alignment are treated as line items to be trimmed when costs need to be cut. The result is that the technology works, but the people do not adopt it — or worse, actively resist it.
Treat the people change as the programme, not a workstream within it. Identify your most influential sceptics early and bring them inside the tent. They will either become your strongest advocates or surface the genuine problems before they become critical. Either way, you need to know what they think. Budget for it accordingly.
The most successful transformation I led was not the largest or the most technically complex. It was the one where we invested as much time in planning, communication and training as we did in the technology itself, with visible executive sponsorship from start to finish. The least successful? A technically excellent solution that became a very expensive trophy on the mantelpiece within 12 months of go-live, because nobody had done the hard work of bringing the business along for the journey.
The Metrics Problem
No clear definition of what success looks like
Organisations begin transformations with aspirational language: agility, innovation, digital-first. These are directions, not destinations. Without clear, measurable success criteria agreed at the outset, programmes drift. Scope expands to fill the available time and budget. And when the inevitable question comes — is this working? — nobody can give a straight answer.
Define success in numbers before you begin. Not "improved customer experience" but "reduced onboarding time from 14 days to 3." Not "greater operational efficiency" but "20 percent reduction in manual processing costs by end of year two." These metrics become your compass. If a decision does not move you toward them, it probably should not be in the programme.
The Scope Creep Spiral
Scope creep and budget overrun
Transformation programmes attract ideas. Every stakeholder sees an opportunity to fix something that has been bothering them for years. Without rigorous governance, the scope expands steadily — each addition individually justifiable, collectively devastating. Timelines slip. Budgets stretch. Confidence erodes. And eventually, a programme that began with clear purpose becomes a sprawling initiative that nobody can explain in a single sentence.
Establish a formal change control process from day one and stick to it. Every scope addition must be evaluated against the defined success metrics, costed properly, and approved at the appropriate level. More importantly, create a structured backlog for good ideas that are out of scope — people are far more willing to accept "not now" when they can see their idea is captured and will be revisited.
What Actually Works
The organisations I have seen execute transformation successfully share a small number of characteristics that have nothing to do with the technology they chose.
- A sponsor at board level who is visibly and consistently committed — not just at launch, but through the difficult middle phase when energy drops and problems surface
- A clear, commercially grounded definition of success that the entire leadership team can articulate without looking at a slide deck
- A governance structure with genuine authority to say no to scope additions and to escalate blockers quickly
- A change management approach that treats adoption as a programme outcome, not an afterthought
- Short delivery cycles with measurable outcomes, so the business can see progress and confidence is maintained
None of these are complicated. All of them require discipline — and that discipline has to come from the top. Technology leaders cannot impose it alone. The most important thing a CTO or transformation lead can do is ensure the business understands that transformation is a business programme, not a technology project. The technology is the enabler. The outcome is what matters.
Transformation is not something that happens to an organisation. It is something an organisation decides to do — and keeps deciding, every day, until it is done.
If your organisation is planning a transformation, or struggling with one already underway, I would be glad to have a straight conversation about it. Sometimes an experienced external perspective is the fastest way to identify where the real problem lies.
Is your transformation delivering what you expected?
I work with leadership teams to diagnose transformation programmes that have stalled, and to build the strategic foundations for those that are just beginning. No jargon, no sales pitch — just a direct conversation about your situation.
Start a Conversation