What UX is and isn’t

It was the kind of product that would photograph well and hold up in a design review.

But as soon as you started using it, things began to unravel.

Journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ took longer than expected. Decisions appeared at the wrong points. The flowglossary×DelightMoments that exceed user expectations.Open glossary term→ felt like it had been built around internal processesglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ rather than what the user was actually trying to achieve. Nothing was obviously broken, but nothing felt easy either. It required more effort than it should have, and that’s always where users start to disengage.

That’s usually where the problem sits.

UX isn’t about how something looks, it’s about how it behaves when someone tries to use it.

In most of the work I’ve been involved in, the biggest issues haven’t come from visual design. They’ve come from how things have been structured underneath. Different teams owning different parts of the journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→, legacy systemsglossary×Legacy SystemA legacy system is an outdated system that is still in use, often due to its critical role.Open glossary term→ shaping the flowglossary×DelightMoments that exceed user expectations.Open glossary term→, compliance and business rules layered on top over time. None of those things are wrong in isolation, but when they all surface directly in the experience, the result is friction.

The user ends up navigating the organisation instead of completing their task.

You see the same patternglossary×PatternA reusable solution to a common design problem.Open glossary term→ across very different industries.

At Co-op Bank, years of ageing infrastructureglossary×InfrastructureInfrastructure refers to the underlying systems and resources that support applications and services.Open glossary term→ and incremental changeglossary×Incremental ChangeIncremental change is the process of making small, continuous improvements over time.Open glossary term→ had created journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ that technically worked, but felt heavy and unintuitive for customers.

Across the NHS, the problem existed at a much larger scale, with hundreds of sites, inconsistent structures, and different teams all approaching content and journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ in their own way.

With Travelbag, the issue showed up in a different form. Users were comfortable browsing, but when it came to committing to a high-value purchase like a holiday, hesitation crept in because the experience didn’t do enough to buildglossary×BuildA build is the process of compiling and packaging code into a runnable application.Open glossary term→ trustglossary×TrustUser confidence that a product, service, or organisation will do what it promises.Open glossary term→ at the right moments.

Different contextsglossary×ContextThe surrounding conditions that shape behaviour and decisions.Open glossary term→, same underlying issue. The experience wasn’t structured in a way that supported the user.

Where UX tends to get misunderstood is in when it’s applied.

It’s often brought in after the key decisions have already been made, once journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ are defined and systemsglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ are in place, with a brief to improve what’s there. At that point, the scope naturally shifts towards refinementglossary×RefinementRefinement is the process of preparing and clarifying backlog items before development.Open glossary term→. You can make things clearer, simplify interactions, and remove some friction, but you’re still working within a structure that may be fundamentally flawed.

That’s why UX sometimes gets reduced to surface-level improvements. Not because that’s what it is, but because that’s the point at which it’s introduced.

The real impact comes earlier, before the shape of the experience has been locked in.

That’s where you can step back and look at what’s actually happening. Why the journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ exists in its current form, what the user is being asked to do, and whether that effort is necessary. It’s where you can challenge assumptions, simplify flowsglossary×DelightMoments that exceed user expectations.Open glossary term→, and remove unnecessary steps before they become embedded in the product.

On the NHS work, that meant moving away from simply improving content and instead rebuilding the structure and information architectureservice×Information ArchitectureImprove navigation, content structure, and findability so users can understand where things are and how to move through them.Open service→ from the ground up.

At Co-op, it meant working within the constraintsglossary×ConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term→ 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→ while reshaping journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ so they felt more intuitive and less demanding for customers who were not naturally digital-first.

With Travelbag, it meant recognising that users weren’t just completing a transaction, they were making a significant financial decision, and the experience needed to support that with clarityglossary×ClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term→ and reassurance at the right points.

In each case, the value didn’t come from how things looked. It came from how they were rethought.

This is where the distinction becomes important.

This isn’t about making something visually appealing or producing deliverables for the sake of processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→. It’s about understanding how an experience holds together, where it starts to create effort, and how that effort can be reduced or removed entirely.

UI plays an important role in that. It helps create clarityglossary×ClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term→, buildsglossary×BuildA build is the process of compiling and packaging code into a runnable application.Open glossary term→ trustglossary×TrustUser confidence that a product, service, or organisation will do what it promises.Open glossary term→, and makes interactions feel considered. But it can only do so much. If the structure underneath is confused or overly complex, the interface can’t compensate for it. The result is something that looks polished but still feels harder to use than it should. If you want to see how that plays out in practice, look at the case studies or the services work.