what UX is, once you remove the job titles

design · 2026-10-18 · 4 min

UX is one of those words that survived because it can mean anything, which is also why it explains nothing. here is the version i use when i build a site.

UX is the set of decisions that determine whether a person can do the thing they came to do, with the least amount of doubt.

not beauty. not "delight". doubt is the enemy: the doubt about where to click, what happens next, whether the form went through, whether the price includes VAT.

the three layers

  • the job — what the person is trying to accomplish, in their words. "find out if you do repairs on saturday" is a job. "explore our services" is a menu.
  • the structure — what exists, in what order, with what names. this is where most UX failures live, long before any colour is chosen.
  • the interface — the visible layer: layout, type, contrast, states, feedback. the part everyone calls "design".

you can have a beautiful interface on top of a broken structure. it will look like a good site and behave like a bad one.

the failure that costs the most

not the ugly button. the missing answer. a visitor arrives with three questions and the page answers one and a half. they do not complain; they leave, and the analytics calls it a bounce.

the second most expensive failure is the silent success: the form submits, the page says nothing, the person is not sure it worked, so they send it again or call to check. both cost you.

the five-minute test

open your site on a phone and try to do the thing a customer would do. then answer:

  • could i tell what this business does in five seconds?
  • is the main action visible without scrolling?
  • when i submit the form, do i know it worked?
  • is there any text i have to squint at?
  • if i go back, do i return to where i was?

four out of five "no" is not a taste problem. it is a UX problem, and it is fixable without a redesign.

UX is not a phase

the common mistake is treating UX as a workshop at the start, then handing a wireframe to someone who builds "the real thing". the decisions continue in the build: what happens on error, what the empty state says, how long the confirmation stays on screen. if the person building it does not own those decisions, the UX is whatever the framework does by default.

what it is worth

a site that removes doubt converts better at the same traffic. that is the whole business case. not "users love it" — fewer abandoned forms, fewer "did you get my message" calls, fewer people asking a question the page already answered.

ux vs ui is the next distinction. if you want the tactical version, the ux tactics i use on my own site is the list i actually run.

faq

what does UX mean in simple words?

the decisions that let a person do what they came to do without doubt: what exists, in what order, with what words, and what happens after they act.

is UX the same as usability?

usability is one part of it: can the thing be used. UX also includes whether the thing should exist, whether the words make sense, and whether the result feels trustworthy.

does a small business need a UX designer?

not necessarily a specialist. it needs someone who owns the decisions above, tests the site with a real person, and fixes what breaks. that can be the designer, the developer, or you.