UX vs UI: the difference that decides who to hire
design · 2026-10-16 · 4 min
the difference is simple until someone draws a venn diagram. then it becomes a job title argument.
UX decides what happens. UI decides how it looks while it happens.
a booking flow is UX: which steps, in what order, what happens when the slot is taken. the calendar, the button, the confirmation screen are UI: the surface of those decisions.
a concrete example
two versions of the same form.
UX problem: the form asks for a phone number, an address and a VAT number before the person knows whether you serve their area. the order is wrong; the person leaves.
UI problem: the labels are 11px grey on white, the button is the same colour as the background, the error message appears below the fold. the order is fine; the surface is unreadable.
you can fix the UI in an afternoon. the UX problem needs a decision about what the form is for.
what each one owns
- UX — research, the job, the information architecture, the flow, the words, the states, the success and failure messages.
- UI — layout, type, colour, spacing, components, motion, the visual system that keeps it consistent.
the words sit in the middle, which is why "ux writer" exists and why most small sites fail there: nobody owns the sentences.
what happens when you hire only one
only a UI designer: you get a beautiful site with a form nobody completes. only a UX person: you get a sensible flow drawn in boxes that nobody can build without inventing the visual language from scratch.
in a small project, one person often does both. ask which half is stronger, and look at the work: a UI-strong portfolio has screenshots; a UX-strong portfolio has before/after flows and a sentence about what changed.
how to read a portfolio in five minutes
- can you use the live site on a phone, right now? if not, it is a picture, not a project.
- does the case study say what the problem was, or only what the result looks like?
- is there a measurable change — fewer fields, fewer steps, a clearer offer — or only "modern look"?
- do the states exist: empty, error, loading, success? screenshot portfolios rarely show them.
the practical answer
for a brochure site, you need taste and structure, usually in one person. for a product with accounts and complex flows, separate them, and put UX first: the visual layer is cheaper to redo than an architecture.
what ux is is the definition i use. how to improve the ux of a site is the checklist.
faq
what is the difference between UX and UI?
UX is the set of decisions about what happens and in what order. UI is the visual and interactive surface that expresses those decisions. UX comes first; UI makes it usable and legible.
can one person do both?
yes, and in small projects it is often better. the risk is that the stronger half hides the weaker one. ask which half the person is stronger at and check the portfolio for the other.
which one should i fix first?
the structure. if the flow is wrong, a prettier surface makes the wrong thing more convincing. fix what the page asks people to do, then how it looks doing it.