methodResearch & behavior

Usability Testing

Observing representative participants attempt realistic tasks to identify where an interface supports or obstructs successful use.

Download Markdown (.md)

01What it means

Usability testing evaluates a product or prototype by asking representative participants to attempt realistic tasks while researchers observe. Sessions may be moderated or unmoderated, remote or in person, and qualitative or quantitative. The central evidence is behavior: where people hesitate, misunderstand, recover, fail, or succeed—not whether they say they like the design.[1][2]

Behavioral evidence from realistic tasks Observe where representative participants succeed, hesitate, misunderstand, and recover
  1. 01Define questions + tasksAudience, critical journey, fidelity
  2. 02RecruitRelevant experience and constraints
  3. 03Run neutral scenariosPlausible goals without hidden instructions
  4. 04Observe behaviorAvoid rescuing too quickly
  5. 05Synthesize + reviseEvidence, severity, frequency, impact; test again

The central evidence is task behavior rather than whether participants say they like the design.

02Why it matters

A screen can look polished and still make essential tasks difficult. Usability testing exposes breakdowns before they become support tickets, abandonment, or safety risks. It gives teams concrete evidence for prioritizing changes and helps distinguish an interface problem from a training, content, policy, or expectation problem.

03When to use it

Use it throughout design: on sketches to compare interaction approaches, on prototypes to repair flows before development, and on live products to investigate persistent friction. It is especially valuable before launching high-frequency, high-risk, or business-critical tasks.

04How it works

  1. Identify target users, critical tasks, research questions, and the fidelity needed to answer them.
  2. Recruit participants whose experience and constraints match the intended audience.
  3. Write neutral task scenarios with plausible goals, success criteria, and no hidden instructions.
  4. Observe task behavior, ask participants to think aloud when appropriate, and avoid rescuing them too quickly.
  5. Synthesize issues by evidence, severity, frequency, and impact; revise the design and test again.

05A practical example

Example

A banking team tests a prototype for adding a transfer recipient. Four of six participants search under “Payments” while the feature sits under “Contacts,” and two abandon the task after a security warning appears to erase progress. The team moves the entry point, preserves form data through verification, and retests the revised flow before engineering handoff.

06Where it breaks

A test session is an artificial setting, and think-aloud narration can change behavior. Small qualitative studies find important issues but do not estimate their population frequency reliably. Prototype gaps may create false problems, facilitator behavior can bias outcomes, and testing cannot by itself establish product desirability, accessibility conformance, or long-term adoption.

Common mistakes

  • Testing vague opinions instead of giving participants realistic tasks.
  • Explaining the interface or leading participants as soon as they hesitate.
  • Reporting every stumble equally without judging task impact and evidence strength.

07Sources

  1. Usability (User) Testing 101Nielsen Norman Group · Professional guidanceUsability (User) Testing 101
  2. Using moderated usability testingUK Government Service Manual · Government guidanceUsing moderated usability testing
View saved topics

Start typing to search titles, definitions, categories, and frameworks.