Method guideUX Research

Usability Testing

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium

Time1-2 h je Session

ParticipantsBased on research question

FormatWorkshop + async

MaturityCanonical

Prepare plan

Prerequisite

What needs to be finished first

Complete firstBounded learning question

A task, use situation, and pending product decision are named.

A broad question produces vague tasks and hard-to-compare observations.

Complete firstTestable version

The product or prototype supports the flow and relevant access needs have been considered.

Technical gaps can masquerade as usability issues or hide real barriers.

Complete firstParticipation and data

Recruitment, consent, recording, and storage are resolved.

Without a safe setup, a session cannot be conducted responsibly.

Preparation

What needs to be ready before start

Materials

Learning question, neutral task scenarios, observable prototype or product, consent information, and observation grid.

People / roles

A moderator guides tasks; an observer records behavior. Participants fit the use situation under study.

Pre-read

Set the learning question, flows, product version, recruitment criteria, and decision context.

Time needed

About 45–90 minutes per session; plan preparation, recruitment, and analysis separately.

Setup

Prepare the test object, clarify privacy and consent, check technology, and pilot moderation.

Core question

The one question this method answers

Can relevant users complete their important tasks with the current design on their own?

Flow

Phases with goal, actions, output and pitfall

Usability testing examines how people complete a specific flow in a realistic use situation. Observed actions and obstacles identify opportunities for improvement. Findings apply to the use situation examined.

Test observation

Fictional teaching example

Keep task, behavior, evidence, and follow-up decision distinct.

Test observation
Observation row	Task	Observation	Evidence or context	Follow-up or change
Task observationRecord one observation from a concrete task.	Fictional task: Find a cordless drill for Saturday.	T1 compares the tool first, then separately searches for pickup time.	Fictional prototype version 0.4; availability and location appear on separate views.	Show location and pickup time together at reservation.
Review a findingSeparate observation, impact, and possible change.	Fictional task: Reserve a tool for a repair appointment.	T2 stops because no confirmed pickup window is visible.	One fictional individual case, not yet a pattern.	Check comprehension with more relevant participants.

1. Task
Task observation
Fictional task: Find a cordless drill for Saturday.
Review a finding
Fictional task: Reserve a tool for a repair appointment.
2. Observation
Task observation
T1 compares the tool first, then separately searches for pickup time.
Review a finding
T2 stops because no confirmed pickup window is visible.
3. Evidence or context
Task observation
Fictional prototype version 0.4; availability and location appear on separate views.
Review a finding
One fictional individual case, not yet a pattern.
4. Follow-up or change
Task observation
Show location and pickup time together at reservation.
Review a finding
Check comprehension with more relevant participants.

Keep evidence and interpretation distinguishable.

NN/G

1
Frame
Learning goal and flow
Goal
Choose a concrete task and the relevant interface.
Inputs for this step
- Write a learning question, bound the flow, and describe a real use goal.
Actions
- Define what a person wants to accomplish; bound the product area, device, and test version.
Output
Bounded test objective and task-level success criteria.
Bounded test objective and task-level success criteria.
Quality check
The question names observable behavior; the test version supports the task without artificial help.
Pitfall
Too many questions become mixed together. Choose one primary learning question and defer secondary questions to another round.
Timing: 20–40 minutes preparation
2
Prepare
Tasks and setup
Goal
Prepare scenarios, recruitment, session flow, and an observation grid.
Inputs for this step
- Bounded test objective and task-level success criteria.
Actions
- Write a neutral everyday situation, recruit for the research question, and clarify consent, recording, storage, and roles.
Output
Piloted test script and observation grid.
Piloted test script and observation grid.
Quality check
Scenarios reveal neither route nor desired answer; participation and recording are transparent.
Pitfall
A task names a button or expected route. Describe the person’s goal and remove solution hints.
Timing: 30–60 minutes preparation
3
Observe
Run sessions
Goal
Let the participant work through tasks and intervene only when needed.
Inputs for this step
- Piloted test script and observation grid.
Actions
- Explain that the product is being tested. Observe paths, pauses, backtracking, errors, and comments; separate behavior from interpretation.
Output
Contextual observation notes with session code and test version.
Contextual observation notes with session code and test version.
Quality check
The moderator does not hint at a solution; help, stops, and technical failures are marked.
Pitfall
The moderator rescues the task too soon. Wait and observe; ask a neutral follow-up about the decision path afterward.
Timing: 45–90 minutes per session
4
Synthesize
Synthesize issues
Goal
Compare evidence across tasks and sessions, then derive testable changes.
Inputs for this step
- Contextual observation notes with session code and test version.
Actions
- Group observations by task; separate issue, impact, and evidence, and prioritize changes by user consequence.
Output
Issue list with evidence, severity rationale, and retest decisions.
Issue list with evidence, severity rationale, and retest decisions.
Quality check
Severity is justified; the qualitative sample is not reported as a representative rate.
Pitfall
A single observation is generalized as universal user behavior. State reach and uncertainty; gather more evidence when the decision requires it.
Timing: Analysis time depends on scope

Artifact

What comes out at the end

Sketch: what the artifact looks like

Usability Testing · Moderated Task TestConnect tasks, prototype observation, frictions, and findings with severity

Form

Versioned test plan with tasks, observation notes, evidence, derived issues, and retest decisions.

Versioning / ownership

Version the test object, tasks, and date. Store recordings only with consent; pseudonymize statements and set deletion dates.

Tool alternatives

Prototype and scenario script
Observation grid with separate behavior and interpretation fields
Access-controlled storage using session codes

usability-testing-working-template.md

Plan tasks, individual sessions, and shared analysis.

Usability Testing: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

One focused test round Time: Multi-session research initiative; scope recruitment, sessions, and analysis to the learning question and knowledge gaps.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: Learning question, neutral task scenarios, observable prototype or product, consent information, and observation grid.
Roles: A moderator guides tasks; an observer records behavior. Participants fit the use situation under study.
Advance information: Set the learning question, flows, product version, recruitment criteria, and decision context.
Overall time needed: About 45–90 minutes per session; plan preparation, recruitment, and analysis separately.
Setup: Prepare the test object, clarify privacy and consent, check technology, and pilot moderation.

Prepare for the work steps

Frame: Learning goal and flow

Write a learning question, bound the flow, and describe a real use goal.

Prepare: Tasks and setup

Bounded test objective and task-level success criteria.

Observe: Run sessions

Piloted test script and observation grid.

Synthesize: Synthesize issues

Contextual observation notes with session code and test version.

Test observation

Observation row	Task	Observation	Evidence or context	Follow-up or change
Task observation
Review a finding

Task observation: Record one observation from a concrete task.
Review a finding: Separate observation, impact, and possible change.

Blank worksheet: add your own tasks and observations.

NN/G

Frame: Learning goal and flow

Expected artifact: Bounded test objective and task-level success criteria.

Bounded test objective and task-level success criteria.

Entry:

...

The question names observable behavior; the test version supports the task without artificial help.

Prepare: Tasks and setup

Expected artifact: Piloted test script and observation grid.

Piloted test script and observation grid.

Entry:

...

Scenarios reveal neither route nor desired answer; participation and recording are transparent.

Observe: Run sessions

Expected artifact: Contextual observation notes with session code and test version.

Contextual observation notes with session code and test version.

Entry:

...

The moderator does not hint at a solution; help, stops, and technical failures are marked.

Synthesize: Synthesize issues

Expected artifact: Issue list with evidence, severity rationale, and retest decisions.

Issue list with evidence, severity rationale, and retest decisions.

Entry:

...

Severity is justified; the qualitative sample is not reported as a representative rate.

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/usability-testing/run-sheet

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

usability-testing-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: borrowing a neighborhood tool

All details and observations are fictional. No test was conducted.

Learning question: Can someone find a cordless drill for Saturday and reserve it reliably?

Task: “You are repairing a shelf on Saturday and need a cordless drill. Find out whether you can get a suitable tool and what to do next.”

Observation T1: The participant opens a tool page, reads the availability note, then returns to search to compare locations and pickup times.

Interpretation: Availability and pickup are part of one decision.

Next step: Show location and available time next to reservation in the prototype and check it with a new round. One fictional observation says nothing about real users.

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Learning goal and flowToo many questions become mixed together.View in phase
Tasks and setupA task names a button or expected route.View in phase
Run sessionsThe moderator rescues the task too soon.View in phase
Synthesize issuesA single observation is generalized as universal user behavior.View in phase

Stop criteria

When to pause, resolve prerequisites, or choose another approach

The task gives away the route: rewrite it as a neutral scenario.

Participation, accessibility, or data use is unclear: resolve it before testing.

The interface cannot support the task: match the question to the prototype’s maturity.

Where to go next?

UX Research

Affinity Diagramming

Bundles observations from multiple sessions into shared problem patterns.

Operations

5 Whys

Traces a repeatedly observed failure back to its root cause.

View in playbookValidate Information ArchitectureMove from unclear navigation to tested structure, labels, and findability signals.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods

Test observation

1. Task

2. Observation

3. Evidence or context

4. Follow-up or change

Learning goal and flow

Tasks and setup

Run sessions

Synthesize issues

usability-testing-working-template.md

Usability Testing: Worksheet

Question

Desired outcome

Scope

Preparation for this scope

Method setup

Prepare for the work steps

Frame: Learning goal and flow

Prepare: Tasks and setup

Observe: Run sessions

Synthesize: Synthesize issues

Test observation

Frame: Learning goal and flow

Prepare: Tasks and setup

Observe: Run sessions

Synthesize: Synthesize issues

Open questions and next steps

usability-testing-beispiel.md

Fictional teaching example: borrowing a neighborhood tool

Learning goal and flow

Tasks and setup

Run sessions

Synthesize issues

Where to go next?

Finished the method guide?