Protocol
Give the user a goal and keep your instructions out of the result
A tour proves that you can explain the interface.
When it fits
- You need to know whether people can use a service without coaching.
When to avoid it
- Small studies identify problems in chosen situations. They do not establish population-wide success rates or every accessibility requirement.
Why it matters
Set a realistic task and observe the participant’s attempt. Use neutral prompts and record where assistance occurs. A completed task after a rescue is useful evidence of a problem, not an unassisted success.
Steps
- Describe the desired outcome without naming the controls to use.
- Observe actions, errors and recovery before asking for opinions.
- Separate independent completion, assisted completion and non-completion in the findings.
An example
Ask a participant to resume an unfinished lesson. Do not tell them that it is hidden under History.
Check your result
Can someone reviewing the notes tell what the interface supported and what the moderator supplied?
Keep this limit in mind
- Small studies identify problems in chosen situations. They do not establish population-wide success rates or every accessibility requirement.
Evidence and sources
Supports
Moderated usability testing observes participants attempting relevant tasks with a service or prototype.
Facilitator assistance changes what an observed completion establishes.
Using moderated usability testing · Preparing tasks and conducting the session.