Fill in these first
- Product and what is being tested: [website, app or prototype and the flows in scope]
- Target participants: [profile]
- Session length: [minutes]
- Remote or in person: [format]
- Questions the team needs answered: [for example can new users complete sign-up, do people find the filter]
Task
Write a usability test script that observes what participants do, not what they say they would do.
Output format
- Screener: five questions to confirm a participant fits the profile, with the answer that qualifies.
- Introduction script for the moderator, under 120 words, explaining that the product is being tested, not the participant, and asking them to think aloud.
- Warm-up: two questions about their current habits.
- Tasks: five scenario tasks written as realistic situations, for example "You want to book a table for four this Saturday evening". For each task give: Scenario, Success criteria, Time limit, Neutral prompts if the participant is stuck.
- Post-task question after each task: a rating from 1 to 5 on ease.
- Wrap-up: three closing questions.
- Findings template table with columns: Task, Issue observed, Participants affected, Severity (critical, major, minor), Suggested fix.
Rules
- Tasks never use the exact words of buttons or menu labels in the product.
- Moderator prompts stay neutral, such as "What are you looking for?", and never point to the answer.
- Keep the total task time within seventy percent of the session length.






