Menu

Strategy

Digital transformation is not about technology

Technology is often the most visible part of transformation, but it is rarely the part that defines whether the change actually works.

Why organisations go wrong when they frame transformation as a systems problem, and why the real work usually sits in process, alignment, and how the organisation actually operates.

18 July 20234 min read

In short

Why organisations go wrong when they frame transformation as a systems problem, and why the real work usually sits in process, alignment, and how the organisation actually operates.

Why technology feels like the obvious place to start

On the surface, that feels logical. Technology is visible. It's tangible. It looks like progress. But it's rarely where the real problem sits. Because technology is usually the symptom, not the cause.

In my experience, when organisations talk about needing , what they're often dealing with is something much deeper: fragmented , inconsistent ways of working, misalignment between teams, a lack of around ownership, decisions that have been layered over time without being properly resolved. Technology reflects those issues. It doesn't create them.

It is also the part with a budget line and a vendor attached. change, role and decision rights have no procurement route and no obvious owner, so the attaches itself to the component that can actually be bought.

The most visible part of transformation is usually the technology. The most important part is usually everything underneath it.

Why technology-led transformation keeps reproducing the same friction

When is framed as a technology problem, the solution naturally becomes a technology one. New are introduced with the expectation that they'll fix the experience. But those systems are still being used by the same organisation, with the same , the same constraints, the same underlying issues.

What tends to happen is that the complexity is simply moved. Instead of being spread across multiple , it becomes concentrated in a new one. The may look cleaner, the may be stronger, but the experience still carries the same friction. Journeys are still broken. Workflows are still inefficient. It feels new. But it behaves the same.

Configuration is where this becomes visible. A new arrives with sensible defaults, and over the implementation those defaults get adjusted, one reasonable at a time, until the reproduces the old process faithfully inside better software.

Key takeaway

Technology often exposes organisational problems, but replacing systems does not resolve the processes and decisions that created them.

What changes when transformation starts with understanding

What shifts things is starting somewhere else. Understanding how the organisation actually operates: how decisions are made, how work flows between teams, where the sits and why it exists, what users are trying to do and where the current experience breaks down. That's where begins. Because once those things are clear, technology becomes an enabler, not the driver.

This is also where are often misunderstood. They're frequently positioned as the barrier to progress, but in many cases they're simply exposing deeper issues. Replacing them without addressing those issues rarely delivers the expected outcome. It creates movement, but not necessarily improvement. The same reappear, just in a different place.

Mapping how work actually flows, rather than how it is documented, is usually the first uncomfortable step. The two diverge at every exception, and the exceptions are where the effort sits. A that works for eighty per cent of cases and is handled by email for the rest is not one process.

Why understanding is what makes transformation effective

The most effective are not the ones with the most advanced technology. They're the ones with the clearest understanding of how things work today, what needs to change, and how those changes will be adopted across the organisation. Technology plays a critical role in enabling that, but it's not where the transformation starts. It's where it's realised.

If you start with technology, you risk building something that looks modern but behaves exactly like what it replaced. If you start with understanding, you create the conditions for something genuinely better. is not about what you install. It's about what you change. Technology supports that change. It does not define it.

Adoption is the measure that gets least attention and predicts most. A nobody has fully moved onto means two ways of working now exist in parallel, which is more expensive than the situation before, and it usually shows up as a training problem when it is a one.

The honest question at the end of a programme is not what was delivered. It is what stopped: which was decommissioned, which step was removed, which decision now happens somewhere different. If nothing can be named, the organisation bought rather than changing.

Written by Andy Scott

Strategic design, UX and digital transformation thinking from real projects.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer