Menu

UX

Most user journeys fail long before the interface

By the time most journeys reach design, they've already been shaped by decisions that will limit what design can do.

Why journey problems usually start earlier than the screen, and why fixing the interface alone rarely solves them.

15 January 20264 min read

In short

Why journey problems usually start earlier than the screen, and why fixing the interface alone rarely solves them.

Where things actually go wrong

What a designer receives is a of the journey that has already been agreed, influenced by internal , limitations, compliance requirements, and commercial priorities. At that point, design is expected to make it work.

A journey gets mapped out with good . Each team contributes what they need, legal adds requirements, operations adds steps, product adds , and gradually something that started relatively simple becomes heavier. Not obviously broken, but carrying more than it should. By the time it reaches design, the question isn't what should this be. It's how do we improve what we've got.

That's a very different problem.

The accumulation is the problem, not any individual contribution. Legal asks for one confirmation. Operations needs one field. Product wants one qualifying question. Nobody added a burden, and the person at the end is now answering fourteen things to do something they thought would take a minute.

By the time a journey reaches design, the question usually isn't what should this be. It's how do we improve what we've got.

When the structure is already working against the user

In one project, a sign-up journey had grown to the point where users were being asked for information that wasn't needed until much later, simply because it was easier to collect it upfront internally. The design could improve and clarify inputs, but it couldn't change the fact that too much was being asked too soon.

In another, a booking flow introduced multiple upfront because the required those choices early, not because users needed them there. The could be refined, but the friction was already built into the structure.

Both examples share a shape worth recognising: the sequence follows what the organisation finds convenient to collect, rather than what the person is ready to give. Asked at the right moment, most of those questions are unremarkable. Asked before somebody has decided they want the thing, each one is a reason to stop.

Where journeys really start to fail

This is usually where journeys start to fail. Not at the point of , but at the point they are defined. When the focus shifts from what the user is trying to achieve to how the organisation needs things to work, the experience begins to carry unnecessary weight. Each additional step might be justified in isolation, but together they create something that feels harder than it should.

The moment worth attending to is the one where the journey is agreed rather than designed: often a workshop, often with no designer present, and usually recorded as a flow diagram that everyone treats as settled from then on.

Key takeaway

If the structure is already misaligned before design starts, interface improvements can only take the journey so far.

Why design can only do so much

You can improve , reduce confusion, and make the experience feel more coherent, but you're still working within a structure that may not support the user properly. It's the difference between refining a journey and reshaping it.

On some projects, simply stepping back and reworking the flow (removing steps, reordering decisions, shifting where certain actions happen) has had a bigger effect than any visual redesign. Journeys become shorter, easier to follow, and require less effort. Once that structure is right, the becomes much easier to design because it's supporting something that already makes sense.

The most valuable question at that stage is which of these steps could happen later, or not at all, or somewhere the user never sees. It is a structural question rather than a design one, and asking it early tends to be worth more than any amount of work on the screens that follow.

Where UX has the most value

Not at the point where screens are being produced, but at the point where journeys are being formed. Understanding what the user actually needs to do, what can be simplified, and what can be handled behind the scenes rather than pushed onto them.

If a journey is flawed at its core, no amount of design will fully fix it. At best, you make it feel slightly better. At worst, you make a broken journey look convincing enough that the problem takes longer to spot. And that's usually when it becomes more expensive to fix.

Getting into the room where journeys are shaped is largely a matter of timing rather than persuasion. Being present when the flow is first sketched costs an hour. Being handed it afterwards means every improvement has to be argued against a decision somebody has already communicated.

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