Digital Transformation

Why most digital transformation starts in the wrong place

Most digital transformation programmes don’t fail because of technology. They fail because they start in the wrong place.

Why transformation so often starts with platforms and interfaces instead of fixing the structure of the experience itself.

28 March 20266 min read

What looks like progress often isn’t

New get introduced, new get designed, and there’s a lot of activity around moving things forward.

On paper, it looks like progress.

In reality, very little has actually changed.

The problem is that often gets framed as a technology exercise. Upgrade the , rebuild the , migrate the data, and the experience will improve as a result.

But the experience isn’t created by the technology. It’s created by how everything fits together.

The .

The .

The decisions that sit behind what the user is being asked to do.

If those things aren’t addressed, you don’t get . You just get a newer of the same problems.

If the journeys, processes and decisions behind the experience aren’t addressed, you don’t get transformation. You just get a newer version of the same problems.

The structure is usually the problem

I saw this clearly working with Co-op Bank, where years of and had shaped the way worked. There was a strong drive to modernise, but the real challenge wasn’t just the technology, it was how the experience had evolved around it.

Customers were navigating that made sense internally, but felt heavy and unintuitive from the outside. Simply rebuilding the wouldn’t have solved that. The structure itself needed to be rethought, step by step, within the of the existing systems.

A similar issue showed up at scale with the NHS.

Here, the problem wasn’t a single . It was hundreds of sites, multiple departments, different regional approaches, and no consistent structure tying it all together. Content was duplicated, outdated, and often didn’t meet or GDPR standards.

There had already been attempts to consolidate it. They hadn’t worked.

Not because the intent was wrong, but because the starting point was.

If you begin with the , you inherit all the inconsistencies that already exist. What we needed to do instead was step back, understand how people were actually using the , and rebuild the structure from the ground up. That meant redefining the , creating reusable templates, and aligning teams around a shared way of working before anything was rolled out.

The technology followed that thinking, not the other way around.

Where transformation usually goes off track

That’s usually where goes off track.

It starts with solutions instead of problems.

There’s an assumption that the current experience just needs to be modernised, rather than questioned. That the way things are structured is broadly correct, and the issue is how they’re presented or delivered.

But in most cases, the structure is exactly where the problem sits.

Key takeaway

Transformation tends to fail when it starts with platforms and interfaces instead of questioning how the experience is structured underneath.

What working transformation looks like

When works, it looks very different.

It starts by understanding what users are actually trying to do, where they struggle, and why. It looks at how are currently shaped, not just on the surface, but across , teams, and . And it challenges whether those journeys need to exist in that form at all.

That’s where the real changes happen.

Shorter .

Clearer decisions.

Less effort required from the user.

Those outcomes don’t come from new technology. They come from rethinking how the experience works.

Technology should follow the thinking

Technology still plays a critical role, but it should enable the experience, not define it.

If you get the structure right first, the technology becomes much easier to implement because it’s supporting something that already makes sense. If you get it the other way round, you end up constantly working around , trying to fix problems that have already been baked in.

This is why I tend to approach from the experience backwards.

Understanding how things work today, where the is coming from, and what needs to change to make it simpler, clearer, and more usable. From there, decisions around design and technology become much more straightforward.

Because isn’t about replacing what you have.

It’s about fixing what isn’t working.

And most of the time, that starts long before a single line of code is written.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20