Most user journeys fail long before the interface

What a designer receives is a versionglossary×VersionA version is a specific iteration of software or a product at a point in time.Open glossary term→ of the journey that has already been agreed — influenced by internal processesglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→, systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ limitations, compliance requirements, and commercial priorities. At that point, design is expected to make it work.

A journey gets mapped out with good 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→. Each team contributes what they need, legal adds requirements, operations adds steps, product adds featuresglossary×FeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term→, 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.

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 layoutglossary×LayoutLayout is the arrangement of elements on a page or screen, determining how content is organised and presented. It influences readability, usability, and overall experience.Open glossary term→ 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 decision pointsglossary×Decision PointA decision point is a moment in a user journey where a user must choose between actions that affect what happens next.Open glossary term→ upfront because the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ required those choices early, not because users needed them there. 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→ could be refined, but the friction was already built into the structure.

This is usually where journeys start to fail. Not at the point of interactionglossary×InteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term→, 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.

You can improve clarityglossary×ClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term→, 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 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→ becomes much easier to design because it's supporting something that already makes sense.

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.