Why most digital transformation starts in the wrong place

New platformsglossary×PlatformA platform is a system or environment that enables users, services, or applications to interact, build, or operate.Open glossary term→ get introduced, interfacesglossary×InterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term→ are redesigned, and there's a lot of visible activity. On paper, it reads as momentum. In practice, very little has changed.

The mistake is framing transformationglossary×TransformationTransformation is a fundamental change in how a system, organisation, or experience operates, often involving structure, processes, and behaviour.Open glossary term→ as a technology exercise. Upgrade the platformglossary×PlatformA platform is a system or environment that enables users, services, or applications to interact, build, or operate.Open glossary term→, rebuild the interfaceglossary×InterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term→, migrate the data — and the experience will improve as a result. But the experience isn't produced by the technology. It's produced by how everything fits together: the journeys, the processes, and the decisions that sit behind what the user is being asked to do. If those things aren't examined, you don't get transformation. You get a newer version of the same problems.

At Co-op Bank, years of legacy systemsglossary×Legacy SystemA legacy system is an outdated system that is still in use, often due to its critical role.Open glossary term→ and incremental changesglossary×Incremental ChangeIncremental change is the process of making small, continuous improvements over time.Open glossary term→ had shaped how journeys worked in ways that were invisible from the inside but immediately felt from the outside. Customers were navigating processesglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ that made internal sense but carried unnecessary weight. Rebuilding the interface wouldn't have changed that. The structure itself needed rethinking, step by step, within real constraints.

The NHS presented the same issue at a different scale. Hundreds of sites, multiple departments, inconsistent regional approaches, and no coherent structure tying it together. Previous consolidation attempts had failed — not because the intentglossary×Search IntentSearch intent is the underlying goal or purpose behind a user’s query, such as finding information, making a purchase, or navigating to a specific site.Open glossary term→ was wrong, but because they started with the platformglossary×PlatformA platform is a system or environment that enables users, services, or applications to interact, build, or operate.Open glossary term→ and inherited all the inconsistencies already baked in. What worked instead was stepping back, understanding how people actually used the servicesglossary×ServiceA service is a component or function that performs a specific task within a system.Open glossary term→, and rebuilding the architecture from the ground up before any technology decisions were made.

Most programmes start with solutions rather than problems. There's an assumption that the existing structure is broadly correct and just needs modernising — that the issue is presentation, not architectureglossary×ArchitectureArchitecture refers to the structure and organisation of a system, including how components interact and are designed.Open glossary term→. In most cases, that assumption is exactly where the trouble starts.

When transformationglossary×TransformationTransformation is a fundamental change in how a system, organisation, or experience operates, often involving structure, processes, and behaviour.Open glossary term→ works, it begins with understanding: what users are actually trying to do, where they struggle, and why. It looks at how journeys are shaped across systemsglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→, teams, and processesglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→, and questions whether those journeys need to exist in that form at all. The outcomes that follow — shorter journeys, clearer decisions, less effort from the user — don't come from new technology. They come from rethinking how the experience works.

Technology still plays a critical role, but it should enable the experience, not define it. When the structure is right first, technology becomes easier to implement because it's supporting something that already makes sense. When it's the other way around, teams spend months working around constraintsglossary×ConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term→ that were avoidable.

Approaching transformationglossary×TransformationTransformation is a fundamental change in how a system, organisation, or experience operates, often involving structure, processes, and behaviour.Open glossary term→ from the experience backwards consistently produces better results. Understand how things work today, where frictionglossary×FrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term→ is coming from, what needs to change. From there, design and technology decisions become significantly more straightforward.

Transformationglossary×TransformationTransformation is a fundamental change in how a system, organisation, or experience operates, often involving structure, processes, and behaviour.Open glossary term→ 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.