Why Tech Transformations Fail (Hint: It's Not the Tech)

I've spent years around large-scale technical transformations – from data warehouse work to cloud and digital programs across government and enterprise. Many of these tech transformations fail, but they almost never fail due to technology. They fail because the business didn't transform with it.

Many of these programs are well thought out and designed transformations. There's a plan for the technical work, a roadmap, maybe even a change plan to help people adjust to new tech. But there's rarely a coordinating plan for how the business and human systems will actually operate in the new world.

Organisations don't decide to transform their technology for technology's sake – there's a business outcome needed somewhere. Cost reduction, faster time to market, better citizen services, innovation capability. Yet when the new platform goes live, the humans are still operating in the old world, with old processes, old decision rights, old risk postures, and old measures of success.

Then come the uncomfortable questions: Why aren't teams using the new platform? Why are decisions still being escalated the old way? Why didn't we get the savings and productivity gains we expected? Why are we still talking about the same problems we said the transformation would solve?

The Carbon-Based Problem

A customer told me a couple of years ago that her problems were never the tech – they were carbon based. The humans haven't moved. I've never forgotten that line because it captures something we all know but rarely address with the same rigour we bring to technical planning.

We underestimate how much behaviour, identity, and power structures are embedded in "how we've always done things." That legacy mainframe isn't just technology - it's also the thirty-year career of your most senior engineer. That manual approval process isn't just inefficient - it's also how middle management maintains visibility and control. That quarterly release cycle isn't just slow - it's also how governance feels confident they've managed risk. When you change the technology, you're changing people's roles, their expertise, their sense of competence, sometimes their power base. No wonder they don't leap onto the new platform with enthusiasm.

We can't drop modern cloud architecture into a legacy decision culture and expect magic. We can't fund software, ignore capability building and expect outcomes. We can't announce agility, keep the same governance structures and expect the org to be more agile. And we really cannot ask an organisation for innovation while punishing risk or failure.

Three Transformations, Not One

Transformation isn't simply a tech upgrade. It's actually three parallel transformations that need to happen together: technical, operational, and cultural. Most organisations plan meticulously for the first, give lip service to the second, and completely ignore the third.

The technical transformation is what we're good at. We architect, we migrate, we validate, we test. We have methodologies and frameworks and proven approaches. This is the part that usually works.

The operational transformation is where it starts to get messy. This is about redesigning how work actually gets done. If you're moving to cloud, what happens to your change approval board that was designed for physical infrastructure changes? If you're adopting agile delivery, what happens to your project governance that requires stage gates and signed-off requirements documents? If you're implementing DevOps, what happens to the separation between development and operations teams that your org chart is built around? Too often, we implement new technology but keep the old operating model, then wonder why we're not getting the productivity gains or speed to market we expected.

The cultural and leadership transformation is the one we talk about least and need most. This is about fundamentally changing how decisions get made, how risk is assessed, how success is measured, and where power sits. If we say we want agility but keep decision-making locked at the top, we haven't actually changed. If we say we want to be data-driven but continue to run meetings based on hierarchy or the loudest voice, we're still operating in the old culture. If we ask for innovation but punish any failure, we've just added a new buzzword to the same old risk-averse environment.

What Changing With the Tech Actually Looks Like

So what does it mean to actually transform alongside the technology? Here's what I've seen work in the transformations that deliver real business outcomes:

Decision rights move with the architecture. When you shift to distributed cloud services and product teams, decision-making needs to shift too. The teams closest to the work need authority to make choices about their technology stack, their approach, their priorities. Yes, within guardrails. Yes, with appropriate governance. But if every decision still needs to go up three levels for approval, your new cloud architecture is just different  infrastructure running old ways of working.

Risk management evolves from prevention to resilience. Legacy IT cultures often treat every outage as a failure of process that needs more controls. Cloud-native cultures expect things to fail and build resilience instead. That's not just a technical shift - it's a leadership shift. It means executives who are comfortable with "we had an outage, we learned from it, we're better now" instead of "who can we blame?" It means governance that asks "how did we recover?" not just "how did we prevent?"

Success metrics change from activity to outcomes. I've seen organisations migrate to cloud and still measure success by utilisation rates and uptime percentages instead of time to market, customer satisfaction, or cost of delivering value. If your measures don't change, your behaviour won't either. The new platform becomes just a new place to do old work.

Capability building is funded like infrastructure. In the transformations that didn’t work,  they spent millions on technology and almost nothing on helping people build new skills, understand new ways of working, or change their day-to-day practices. The assumption was that if you trained people on the new tools, they'd figure out the rest. They didn't. Capability building isn't training. It's coaching, it's experimentation time, it's permission to learn through doing, it's creating space for people to develop competence in new ways of working. It costs money and time, and it's as critical as the technical investment.

The Leadership Work Nobody Wants to Do

Here's the uncomfortable truth: most executives are more comfortable talking about cloud architecture than about changing their own decision-making patterns. It's easier to fund a technical roadmap than to confront the fact that your governance model is designed for a world that no longer exists. It's more comfortable to announce that we're now agile than to actually distribute authority and live with the discomfort of not controlling everything.

The work of cultural transformation is hard, slow, and often invisible until it's done. You can't Gantt chart your way through changing how people relate to risk. You can't dashboard your way to a new decision culture. You have to model it, reward it, have difficult conversations when people revert to old patterns, and accept that it will be messy for a while.

But without this work, your technology transformation will underdeliver. You'll get new infrastructure running old ways of working. You'll get modern platforms with legacy mindsets. You'll get the cost without the value.

Making It Real

I love a good transformation – I love when customers get the business outcome they needed from their cloud transformation, when the effort and cost drive real change. It’s why I go to work every day. Technology is constantly changing and evolutions can be quick. People and organisations are simply not as quick to change. We need to address that with at least some of the rigour of our technical plans.

That means when you're planning your next transformation, budget time and money for the operational and cultural work, not just the technical work. Create space for people to learn new ways of working, not just new tools. Change your measures of success to match your new operating model. Move decision rights to match your new architecture. And most importantly, start the leadership transformation at the top. If executives aren't willing to change how they operate, nobody else will either.

The technology will work. The question is whether your organisation will work with it.