UX and UI are not the same thing

I've been brought into projects where 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→ had clearly been through multiple rounds of refinementglossary×RefinementRefinement is the ongoing work of clarifying, breaking down, and sizing backlog items before they enter development. It is where ambiguity gets resolved while resolving it is still cheap.Open glossary term→. The typography was solid, spacing was consistent, everything felt considered. It looked like the hard work had been done. But as soon as you started using it, you could feel the gaps. Journeys that didn't quite flow. Decisions introduced at the wrong time. Steps that made sense internally, but not from the outside. The UI was doing its job. The UX wasn't.

The tell is that nobody can point at anything specifically wrong. Every screen survives review individually, because reviews look at screens individually. The problem only appears when you attempt the whole task in sequence, which is the one thing a design review rarely does.

UI is easier to see, and easier to react to. Stakeholdersglossary×StakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term→ can look at a screen and have an opinion straight away. It's tangible. It feels like progress. UX is different. It often involves things that aren't immediately visible: mapping journeys, understanding systemsglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→, aligning teams, working through constraintsglossary×ConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term→. It takes longer to show. It's harder to point at. So the work often leans towards UI, because that's where feedback is quickest.

This has a practical consequence for how the work gets planned. UI produces something to show at the end of every sprintglossary×SprintA sprint is a fixed time period where a team completes a set of planned work.Open glossary term→. UX often produces a decision, a removed step, or a reordered journey, none of which demo well. Teams measured on visible progress drift towards the work that photographs better.

It also affects who gets consulted. Everyone has an opinion about a colour and few people feel qualified to challenge a journey structure, so feedbackglossary×FeedbackFeedback is the system response that informs users about the result of their actions. It helps users understand what has happened and what to do next.Open glossary term→ concentrates where it is least consequential and the structural decisions go through unexamined.

At Co-op Bank, there were journeys that had been refined visually but still carried the weight of legacy processesglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ underneath. 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→ looked modern, but the experience still felt heavier than it needed to, particularly for customers who weren't naturally comfortable with digital banking.

Across the NHS, the issue showed up in how information was structured. Individual pages could be well designed, but if the underlying organisation wasn't consistent, users still struggled to find what they needed.

In eCommerce, flows that looked polished and on-brand didn't buildglossary×BuildA build is the process of compiling and packaging code into a runnable application.Open glossary term→ enough confidenceglossary×ConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term→ at the right points, leading users to hesitate or drop offglossary×Drop-offDrop-off refers to users leaving a journey before completing a desired action or reaching the next step.Open glossary term→ despite the quality of the interface. Different contexts, same underlying gap.

The projects that work best are the ones where that order is right. Understanding what the user is trying to achieve, how the journey should flow, what can be simplified or removed, and how decisions should be handled. Once that's in place, the UI becomes much easier to design because it's supporting something that already holds together.

UI plays a critical role in how a product is perceived. A well-executed 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→ 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→, improves comprehension, and makes interactions feel considered. But it's not the foundation. The strongest outcomes come from treating UX as the thing that shapes the experience, and UI as the thing that brings it to life. One defines how it works. The other defines how it looks. When those two are aligned, the product feels effortless. When they're not, you end up with something that looks right but doesn't quite work.

Getting the order right does not mean UX finishes before UI starts. It means the questions are answered in the right sequence: what the user is trying to do, then what the steps are, then what each screen has to carry, then how it looks. Those can overlap in time. They cannot swap places.