UX
UX and UI are not the same thing
At some point, almost every project blurs the line between UX and UI. That’s usually where things start to go wrong.
Why blurring UX and UI together usually leads to the wrong work being prioritised, and where the real impact tends to sit.
In short
Why blurring UX and UI together usually leads to the wrong work being prioritised, and where the real impact tends to sit.
Where the gap becomes obvious
Because while they work closely together, they’re solving very different problems.
I’ve been brought into projects where the glossaryInterfaceAn 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 glossaryRefinementRefinement is the process of preparing and clarifying backlog items before development.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.
glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term that didn’t quite glossaryDelightMoments that exceed user expectations.Open glossary term.
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 UI can be doing its job perfectly while the UX underneath still isn’t working.
Why UI gets the attention first
UI is easier to see, and easier to react to.
glossaryStakeholderA 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 glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term, understanding glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term, aligning teams, working through glossaryConstraintsConstraints 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 glossaryFeedbackFeedback 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 is quickest and progress is easiest to demonstrate.
How the gap shows up in real products
I’ve seen this play out in different ways across projects.
On work with the Co-op Bank, there were glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term that had been refined visually, but still carried the weight of legacy glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term underneath. The glossaryInterfaceAn 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.
And in eCommerce, I’ve seen glossaryDelightMoments that exceed user expectations.Open glossary term that looked polished and on-brand, but didn’t glossaryBuildA build is the process of compiling and packaging code into a runnable application.Open glossary term enough glossaryConfidenceConfidence 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 off despite the quality of the interface.
Different glossaryContextThe surrounding conditions that shape behaviour and decisions.Open glossary term, same underlying gap.
Key takeaway
Strong UI can improve the surface, but if the structure underneath is weak, the experience still breaks down.
Where things usually start to drift
Where things tend to drift is when UI becomes the focus too early.
There’s pressure to make things look right, to move into design, to create something tangible. But if the structure underneath hasn’t been worked through, the glossaryInterfaceAn 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 ends up carrying problems it can’t fully solve.
You can make something clearer. You can improve glossaryReadabilityHow easy content is to read and understand.Open glossary term. You can guide users more effectively.
But you can’t redesign your way out of a glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term that doesn’t make sense.
What good alignment looks like
The projects that work best are the ones where that order is right.
Understanding what the user is trying to achieve, how the glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term should glossaryDelightMoments that exceed user expectations.Open glossary term, 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.
That’s not to downplay UI.
A well-executed glossaryInterfaceAn 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 glossaryBuildA build is the process of compiling and packaging code into a runnable application.Open glossary term glossaryTrustUser confidence that a product, service, or organisation will do what it promises.Open glossary term, improves comprehension, and makes interactions feel considered. It plays a critical role in how a product is perceived.
But it’s not the foundation.
What this means in practice
In my experience, 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.
And users feel that difference straight away.