Protocol

Give the user a goal and keep your instructions out of the result

A tour proves that you can explain the interface.

About 1 min read

Before you use it

Use when
  • You need to know whether people can use a service without coaching.

Keep this limit in mind

  • Small studies identify problems in chosen situations. They do not establish population-wide success rates or every accessibility requirement.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

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

  1. Describe the desired outcome without naming the controls to use.
  2. Observe actions, errors and recovery before asking for opinions.
  3. 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?

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingGive the user a goal and keep your instructions out of the result

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.

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details