Usability test plan

# Usability test plan

**Product / prototype:**
**Version or link:**
**Facilitator:**
**Note-taker:**

## Goals
What do we need to learn? Tie each goal to a decision.
1.
2.

## Participants
- Number: 5 per distinct user group is a common starting point for finding major problems
- Criteria:
- Exclude: people who worked on the product, close friends of the team

## Format
- [ ] Moderated, in person
- [ ] Moderated, remote
- [ ] Unmoderated
- Device(s):
- Session length: 30 to 45 minutes

## Scenarios and tasks
Write scenarios as realistic situations without using the interface's own words.

| # | Scenario | Success criteria | Max time |
|---|---|---|---|
| 1 | You need a deep clean before your parents visit on Saturday. Book one for the morning. | Booking confirmed for Saturday morning without help | 5 min |
| 2 | | | |
| 3 | | | |

## Questions after each task
- How easy or difficult was that, on a scale of 1 (very difficult) to 7 (very easy)?
- What, if anything, was confusing?

## Closing questions
- What did you like most and least?
- Is there anything you expected to see that was missing?

## Metrics to record
- Task success (completed / completed with help / not completed)
- Time on task (optional)
- Errors and where they happened
- Ease rating

## Ethics
- [ ] Consent recorded
- [ ] Participants told we are testing the design, not them
- [ ] Recordings stored securely and deleted on:

## Pilot
Run one pilot session with a colleague and fix unclear tasks before real sessions.