Skip to content
APDD
See my library

Discipline

UX design

Designs a product, system, or service around what the person perceives and feels before, during, and after using it, from the need behind it to the interface they touch.

In Spanish
Diseño UX
Origin
User-centered design (Norman and Draper, 1986) and usability engineering (Nielsen, 1993); the term spread from Apple, where Norman was “User Experience Architect” (Norman, Miller, and Henderson, 1995)

What it deals with

A product can work and still fail if the person finds it hard to understand. In Palm Beach (Florida), in 2000, a ballot with candidates on both sides of a single column of punch holes led more than 2,000 voters to choose another candidate by mistake (Wand et al., 2001).

Principles

  • Start from the need, not the screen

    Understand who will use it, for what, and in what situation. Someone booking a doctor’s appointment does not want an app: they want to see a doctor soon.

  • Design the whole journey

    The experience is the whole relationship with the organization, not just the interface. The appointment starts when they look for the clinic and continues with the reminder, the time change, and the arrival.

  • Go from abstract to concrete

    First decide which features are included and how they connect; then, where each button goes and how it looks. Choosing colors before knowing whether a calendar is needed is starting at the end.

  • Test early with people

    Watch real people use a sketch or a prototype, and look at what they do, not what they say. A paper prototype already shows whether patients can find how to change the time.

  • Iterate

    Fix what fails and test again: design improves in rounds. If nobody sees the button to change the time, move it and test again.

  • Work with other disciplines

    A good experience does not come from the design team alone. Online booking also depends on the clinic’s schedule and on the person at the front desk.

Applications in design

  • Use it like this

    Before drawing screens, clarify what the person is trying to achieve, what is stopping them, and at what point in the journey.

  • Avoid

    Confusing UX with the look of the interface: a beautiful screen can still be useless.

  • Don’t fall for it

    Having every screen work is not enough: if the reminder never arrives or the front desk cannot see the appointment, the experience still fails.

Especialidades

Specialty

UX strategy

Aligns the experience of a digital product with business goals before designing screens.

Specialty

Form design

Designs forms that people can fill in easily and without mistakes.

Specialty

Search design

Designs how people find what they are looking for in a product, from the search box to the results.

Models and concepts

  • ConceptDeceptive patterns (dark patterns)Designs that exploit how we decide to get you to do something you didn't want to.
  • ConceptProgressive disclosureShow the essentials first and keep advanced options for when someone asks for them.
  • ConceptJakob’s lawWe expect a site to work like the ones we already know, because we spend more time on them.
  • ConceptTesler’s lawEvery task has an amount of complexity that cannot be removed, only moved.
  • ModelHEART frameworkFive kinds of metrics to measure the experience of a digital product and know whether a change improves it.
  • ModelUser experience honeycombSeven facets of a good user experience, beyond whether the product is easy to use.
  • ModelDesign hierarchy of needsPyramids that ask you to meet a product's basics first (it works), then what makes it pleasant.

Methods and tools

  • MethodBenchmarkingComparing how others solve the same thing, to learn from their successes and mistakes.
  • MethodCard sortingAsking people to group cards to understand how they organize information.
  • ApproachUser-centered designDesigning systems around the tasks and abilities of the people who use them, testing early and often.
  • ApproachHuman-centered designDesigning from the needs, context and participation of the people who will use something.
  • MethodSurveyThe same questions to many people, to measure how many think or do something.
  • MethodDiary studyPeople record what they do and feel over days or weeks, as it happens.
  • ArtifactUser flowThe step-by-step path a person follows to complete a task in a product.
  • MethodFocus groupA moderated conversation with a small group to learn their opinions and how they influence each other.
  • MethodJourney mapA map of a person's path through a service, with what they do, use and feel at each step.
  • ApproachLean UXDesigning in short cycles of hypothesis, testing and learning, as a team and with little documentation.
  • MethodPersonasResearch-based characters that represent groups of users and their goals.
  • MethodPrototypingBuilding quick, incomplete versions of an idea to test it before developing it.
  • MethodUsability testingWatching real people attempt tasks with the product to find out where they get stuck.
  • ArtifactWireframeThe outline of a screen in boxes and lines, without final colors or images.
  • MethodContent auditListing all the content that exists and assessing each piece to decide what stays.
  • MethodTree testingChecks whether people can find things in a site's menu, using only the names and no design.
  • ApproachJobs to be doneUnderstanding what progress a person seeks in a situation and what they “hire” a product for.
  • MethodValue Proposition CanvasChecking whether what you offer responds to what a type of customer is trying to do, suffers and wants.
  • MethodKano modelClassifies a product's features by how they change the satisfaction of the people who use it.
  • ArtifactDesign systemThe set of shared components, rules, and criteria a team uses to build its interfaces.
  • MethodA/B testingShowing two versions to random groups and measuring which one works better.
  • ApproachValue sensitive designTaking into account the values of everyone affected throughout the design of a technology.
  • ApproachEAST frameworkTo change a behavior, make it easy, attractive, social and timely.
  • ApproachPrivacy by designProtecting personal data from the first sketch, with the most private option already set.

Authors and works

  1. 1985

    John D. Gould and Clayton Lewis

    Proposed three principles for designing easy-to-use systems: get to know users early, measure real use, and iterate.

  2. 1986

    Don Norman and Stephen Draper

    Brought together user-centered system design in a book, starting from the person’s needs rather than from technology.

  3. 1993

    Jakob Nielsen

    Described usability engineering, which measures and improves ease of use throughout development.

  4. 1995

    Don Norman, Jim Miller, and Austin Henderson

    Called Apple’s interface work “User Experience” and described the role of user experience architect.

  5. 1998

    Don Norman and Jakob Nielsen

    Explained that user experience covers the whole relationship with the company, its services, and its products, not just the interface.

  6. 2002

    Jesse James Garrett

    Organized the work into five planes, from strategy to the visual surface.

  7. 2020

    Jon Yablonski

    Brought together in Laws of UX principles from psychology that are useful for designing interfaces, such as Hick’s law or the Doherty threshold.

Sources

Original sources

Secondary sources

  • Norman, D., & Nielsen, J. (1998). The definition of user experience (UX). Nielsen Norman Group. View source: Norman, D., & Nielsen, J. (1998)
  • Yablonski, J. (2020). Laws of UX: Using psychology to design better products & services. O'Reilly Media. View source: Yablonski, J. (2020)
  • Goodman, E., Kuniavsky, M., & Moed, A. (2012). Observing the user experience: A practitioner’s guide to user research (2nd ed.). Morgan Kaufmann.
  • Spencer, D. (2009). Card sorting: Designing usable categories. Rosenfeld Media.

Last reviewed: