UX

Most user journeys fail long before the interface

By the time most journeys reach design, they’ve already been shaped.

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

15 January 20265 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 lands in front of a designer is rarely a blank canvas. It’s a of the that has already been agreed, often influenced by internal , system limitations, compliance requirements, and commercial priorities.

At that point, design is expected to make it work.

I’ve seen this happen across a lot of different projects.

A is mapped out in a room, usually with good intent. Each team contributes what they need, legal adds requirements, operations adds steps, product adds , and gradually something that started out 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.

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 had grown to the point where users were being asked for information that wasn’t needed until much later, simply because it made things easier internally. The design could improve , clarify inputs, and guide users more effectively, but it couldn’t remove the underlying issue that too much was being asked too soon.

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

Where journeys really start to fail

This is usually where 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.

By the time that reaches the , the damage has already been done.

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

That’s why design alone can only take things so far.

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 and reshaping it.

I’ve seen the impact of addressing this earlier.

On some projects, simply stepping back and reworking the , removing steps, reordering decisions, or shifting where certain actions happen has had a bigger effect than any visual redesign. become shorter, easier to follow, and require less effort from the user.

Once that structure is right, the becomes much easier to design because it’s supporting something that already makes sense.

Where UX has the most value

This is where UX has the most value.

Not at the point where screens are being produced, but at the point where 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.

Because if a 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 look convincing enough that the problem takes longer to spot.

And that’s usually when it becomes more expensive to fix.

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