Marcus Andrey Study
Ler em português Library

UX Foundations · Step 1 · 6 min read

What UX design is (and isn't)

User experience is everything a person goes through with a product or service, not only the screen. Where the term came from, how it differs from UI and usability, what UX designers actually do all week, and a first exercise you can do on the way home.

Four layers of a user experience: the interface people see, usability, the service around the screen, and the context of their day. Point at a layer and the ones above it lift to show how much sits under the screen. Illustration: Marcus Andrey, drawn with Hairline (MIT, Lucas Marques).

You've already judged hundreds of user experiences today. The door you pushed when it said pull. The app that remembered your address. The form that cleared everything when you made one mistake. User experience is the sum of moments like these: how it feels to try to get something done with a product or service. UX design is the work of making those moments go well, on purpose, for the people who actually use it.

What you'll be able to do after reading:

  • Explain what user experience means, in one sentence, with a source
  • Tell apart UX, UI and usability
  • Describe what a UX designer does in a typical week
  • Spot good and bad experiences around you, and say why

1. A definition you can quote

The most cited definition comes from Don Norman and Jakob Nielsen: "'User experience' encompasses all aspects of the end-user's interaction with the company, its services, and its products" (NN/g, The Definition of User Experience).

The international standard for human-centred design says something similar: user experience is the "user's perceptions and responses that result from the use and/or anticipated use of a system, product or service" (ISO 9241-210:2019). Note "anticipated": expectations count too, before anyone touches the product.

Norman coined the term for his group at Apple in 1993 (Nielsen, A 100-Year View of User Experience). In his own words: "I invented the term because I thought human interface and usability were too narrow" (Adaptive Path interview, 2007).


2. UX, UI and usability

UIUser interface

What people see and touch.

Screens, buttons, words, sounds
UsabilityUsability

Can they reach their goal well with it?

Effective, efficient, satisfying
UXUser experience

Everything around it, before, during and after.

Expectations, service, feelings, memory
UI is part of usability, and usability is part of the experience. Each one is wider than the one before. Diagram: Marcus Andrey, CC BY 4.0.

Norman and Nielsen give an example: a film database can have a perfect search interface and still be a poor experience if the film you want isn't in it. They call usability "a quality attribute of the UI" (NN/g). The ISO standard defines usability as the "extent to which a system, product or service can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use" (ISO 9241-11:2018). See Users, tasks and context for what each part of that sentence means.

A paved path through a park in Lisbon, and a worn dirt track cutting straight across the grass beside it.
A desire path in Belém, Lisbon: the paved path is what was designed; the worn track is what people actually do. UX design starts by noticing the second one. Photo: Metro Centric, Wikimedia Commons, CC BY 2.0.

3. What UX designers actually do

A week of UX work is less drawing than most people expect:

  • Understand: talk to people who use the product, watch them, read support tickets and data.
  • Frame: agree with the team what problem is worth solving, for whom, and how you'll know it worked.
  • Explore: sketch several solutions, not one, and compare them.
  • Prototype and test: make something people can try, and watch them try it.
  • Specify: describe the chosen design so developers can build it, states and edge cases included.
  • Follow through: check what was built, measure, and improve.

The next lesson, The design process, puts these in order. Who does what on a product team shows who does them with you.


4. What UX design isn't

  • Not only how it looks. Visual design matters, but a beautiful screen can still be a bad experience.
  • Not a step at the end. You can't "add UX" after the product is built, any more than you can add foundations after the house.
  • Not your own taste. Good UX decisions come from what people need and do, not from what the designer likes.
  • Not only screens. Emails, letters, phone calls, shop counters and waiting are all part of the experience.

5. A worked example: renewing a library book

Layer What happens What the designer would ask
Context A student remembers the due date at 11 pm, on a phone, on the bus When and where do people need this?
Service Renewal is allowed twice; fines start the next day What rules shape the experience?
Usability The renew button is three menus deep Can people find it and finish quickly?
Interface A small grey link, with no confirmation after tapping Does it show what happened?

Fixing only the interface (a bigger button) helps a little. Fixing the experience might mean a reminder two days before the due date, which removes the problem entirely.


6. Common mistakes

  • Using "UX" and "UI" as if they meant the same thing.
  • Starting with screens before knowing who the product is for.
  • Treating your own reaction as evidence of what users feel.
  • Forgetting the moments before and after the screen.

7. Vocabulary

Term Meaning
User experience (UX) Everything a person perceives and does around a product or service, before, during and after using it
User interface (UI) The part of a product people see and touch: screens, buttons, text, sounds
Usability How well specific people can reach specific goals with a product: effectively, efficiently and with satisfaction
Service The whole offer around the product: rules, people, other channels
Touchpoint Any moment where a person meets the product or company

8. Try it (no tools needed)

  1. On your way home, notice one thing that was easy and one that was frustrating (a ticket machine, an app, a shop).
  2. For each, write which layer the problem or success lives in: context, service, usability or interface.
  3. For the frustrating one, write one change at a different layer than the obvious one.

Reflection questions: Which experience today did you not notice because it simply worked? What would have to change in the service, not the screen, to fix the frustrating one?


9. If you already practise

  • Use the four layers in critiques: when feedback is "make the button bigger", ask which layer the real problem lives in.
  • The ISO definition's "anticipated use" is a useful argument for designing onboarding, marketing pages and expectations, not just the product.
  • Read NN/g's 2024 piece on what UX is not, and compare it with how your company uses the word (Kaplan, What Is User Experience (and What Is It Not)?).

Checklist

Learn more

Books, courses and videos to go deeper

The design process · Users, tasks and context · Who does what on a product team · Diverge and converge

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close