artifactResearch & behavior

Usability Test Task

A realistic, neutral activity given to a participant so researchers can observe whether and how a product supports a meaningful goal.

Download Markdown (.md)

01What it means

A usability test task states what a participant is trying to accomplish, usually through a short scenario that supplies credible context without revealing the interface path. Tasks translate research questions into observable behavior and define enough success criteria for consistent analysis.[1][2]

02Why it matters

Task wording shapes the behavior a usability study produces. Instructions that name buttons, disclose the answer, or ask participants to pretend implausibly can manufacture success or failure. Well-designed tasks focus attention on a real goal while leaving navigation, interpretation, and decisions to the participant.

03When to use it

Create tasks for moderated or unmoderated usability studies, benchmarks, comparative tests, and prototype evaluations. Choose representative, consequential activities and adjust realism, precision, and standardization to whether the study is diagnostic or quantitative.

04How it works

  1. Start from a research question, user goal, and realistic context rather than an interface feature.
  2. Write a concise scenario in participants' language without copying labels or describing the intended steps.
  3. Define the starting state, required data, completion state, and criteria for success or partial success.
  4. Pilot the task to find ambiguity, accidental clues, impossible setup, and prototype limitations.
  5. Use consistent delivery where comparison matters and document deviations during sessions.

05A practical example

Example

Instead of saying “Use Filters to select refundable morning flights,” a travel study says, “You need a flight to Berlin next Tuesday, must arrive before noon, and your plans may change. Find an option you would be comfortable booking.” The team observes how participants discover and interpret the relevant controls.

06Where it breaks

A scripted task cannot fully reproduce personal stakes, memory, account history, interruptions, or real consequences. Highly specific scenarios may not fit every participant, while vague ones produce incomparable behavior. Passing a set of tasks does not prove that the whole product is usable.

Common mistakes

  • Including interface labels or step-by-step instructions that reveal the path.
  • Writing a task the participant would never plausibly need or understand.
  • Changing task wording or success criteria across participants without recording the change.

07Sources

  1. Task Scenarios for Usability TestingNielsen Norman Group · Professional guidanceTask Scenarios for Usability Testing
  2. Writing Tasks for Quantitative and Qualitative Usability StudiesNielsen Norman Group · Professional guidanceWriting Tasks for Quantitative and Qualitative Usability Studies
View saved topics

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