What Is UX?
User Experience (UX) is the discipline concerned with how a person feels when interacting with a product — digital or otherwise. The term was coined by Don Norman in the early 1990s at Apple, where he defined it as encompassing "all aspects of the end-user's interaction with the company, its services, and its products." This definition remains precise today: UX is not about how something looks. It is about whether using it feels logical, effortless, and satisfying.
In practice, UX work involves research, analysis, and structural design. A UX designer studies who the users are, what they are trying to accomplish, where they get confused, and how they mentally model a product. From this research, they derive information architecture — how content and functionality are organised — and user flows — the paths users take to complete tasks. They produce wireframes and prototypes to test these structures before any visual design is applied.
The Nielsen Norman Group, one of the most authoritative research institutions in the field, defines good UX as meeting "the exact needs of the customer, without fuss or bother." This simplicity of outcome conceals an enormous amount of analytical work. UX is fundamentally a research and problem-solving discipline, not a visual one.
What Is UI?
User Interface (UI) design is concerned with the visual and interactive layer of a digital product — everything the user sees and touches. This includes typography, colour, spacing, iconography, button states, animations, and the overall visual language of the interface. Where UX asks "Does this work?", UI asks "Does this look right, communicate clearly, and feel appropriate for the brand?"
A UI designer works within the structural framework that UX has established, giving it visual form. They apply a design system — a set of reusable components and style rules — to ensure visual consistency across the product. They make decisions about hierarchy: which elements draw the eye first, what feels primary versus secondary, how the visual design guides attention toward the actions that matter.
Good UI design is not decoration. It is functional communication. A well-designed button is one that users immediately understand as clickable, that communicates its state clearly (default, hover, active, disabled), and that fits naturally within the surrounding visual context. UI design that fails at any of these levels — even if it is aesthetically pleasing — is not good UI design.
Where They Overlap — and Where They Don't
The confusion between UX and UI arises partly because both disciplines produce visual outputs — wireframes, mockups, prototypes — and partly because many practitioners work across both. In smaller teams and agencies, the same person often carries out both UX and UI work. But the activities remain distinct even when performed by one person.
UX and UI overlap most in the interaction design layer: decisions about how interface elements respond to user input, how transitions and animations support navigation, and how feedback states (loading, error, success) are handled. Both disciplines have a stake in these decisions, because they sit at the intersection of structure and form.
Where they diverge: UX work is largely invisible in the final product. If it has been done well, users simply find the product intuitive — they do not notice the architecture behind it. UI work, by contrast, is entirely visible. It is the surface through which the UX is experienced. A product with strong UX and weak UI will feel functional but uninspired. A product with strong UI and weak UX will look impressive but frustrate users the moment they try to accomplish anything non-trivial.
Why the Distinction Matters for Your Project
When a client brief asks for "UX/UI design," it is worth establishing what is actually needed. Many digital projects skip genuine UX research in favour of jumping straight to visual design — a decision that typically results in a product that looks polished but is structured around assumptions rather than user behaviour. Reworking structure after visual design is complete is expensive. Reworking it after development is even more so.
The Interaction Design Foundation documents this pattern extensively: the cost of fixing a usability problem increases by an order of magnitude with each phase of the project. Discovering a structural problem in research costs almost nothing to address. Discovering it after launch costs significantly more — in development time, in lost conversions, and in user trust.
Commissioning UX and UI as a single undifferentiated service without asking how the agency approaches each is a meaningful risk. A clear brief should specify: what research will be conducted, how findings will inform structure, and at what stage visual design will begin. This sequence is not bureaucratic — it is how good digital products are built.
When Do You Need Which?
For simple marketing sites with limited interactivity, the UX requirements are relatively straightforward: clear navigation, logical page hierarchy, fast access to the most important actions. The structural decisions can be made quickly by an experienced designer without formal research. UI design carries more weight here — the visual impression is often what the user judges most.
For products with greater complexity — e-commerce platforms, applications, tools with multiple user roles, onboarding flows — UX becomes the dominant investment. Getting the structure wrong has direct consequences for task completion rates, conversion, and retention. Harvard Business Review research on design-led companies shows that those that invest in UX research outperform their sector peers in revenue growth by a factor of two. That premium is not from better aesthetics. It is from products that work better for users — and therefore deliver more business value.
In short: both matter. But they matter for different reasons, require different skills, and should occupy different phases of a project. Understanding the difference is the first step toward commissioning them effectively.