═══════════════════════════════════════════════════════════════
DISCOVERY WAYPOINT — USABILITY TEST PLAN
Usability test plan | 60–90 min to design | 3–8 people | Difficulty: Low
discoverywaypoint.com/techniques/usability-test-plan-workshop-lightweight
═══════════════════════════════════════════════════════════════

TEST OVERVIEW
  Study name: ___________________________________________
  Product / prototype being tested: _____________________
  Test dates: ___________________________________________
  Moderator(s): _________________________________________
  Note-taker(s): ________________________________________
  Number of sessions planned: ___________________________

─ STEP 1: OBJECTIVES  [0–15 min] ───────────────────────────────
  What decisions will this test inform?
  1. _______________________________________________________
  2. _______________________________________________________
  3. _______________________________________________________

  What we are NOT trying to learn (scope boundary):
  _________________________________________________________

─ STEP 2: PARTICIPANT PROFILE ──────────────────────────────────
  Primary participant criteria:
  ├ Role / context: _______________________________________
  ├ Experience level with [product / domain]: _____________
  ├ Must have: ____________________________________________
  └ Must NOT have: ________________________________________

  Number of participants: ________________________________
  Recruitment lead: ______________________________________
  Recruit by: ____________________________________________

─ STEP 3: TASKS + SCRIPT  [15–45 min] ──────────────────────────
  Task prompts must be realistic and not reveal the answer.

  INTRO SCRIPT
  "Thanks for joining. I want to be clear — I'm testing the
  [product/prototype], not you. There are no wrong answers.
  Please think aloud as you work. Tell me what you're looking
  at, thinking, and feeling. You can stop at any time."

  [If recording]: "Do you consent to being recorded? [Y / N]"

  TASK 1
  Scenario: ______________________________________________
  Task prompt (read exactly): ____________________________
  _________________________________________________________
  ⚠ Check: Does this prompt tell them where to go or what to click? Rewrite it if so.
  Time allowed: ___  Success = ___________________________
  Observe for: __________________________________________

  TASK 2
  Scenario: ______________________________________________
  Task prompt: ___________________________________________
  _________________________________________________________
  Time allowed: ___  Success = ___________________________
  Observe for: __________________________________________

  TASK 3
  Scenario: ______________________________________________
  Task prompt: ___________________________________________
  _________________________________________________________
  Time allowed: ___  Success = ___________________________
  Observe for: __________________________________________

  TASK 4 (if time allows)
  Task prompt: ___________________________________________
  Time allowed: ___  Observe for: ________________________

  CLOSING QUESTIONS
  "What was most confusing or frustrating?"
  "If you could change one thing, what would it be?"
  "Is there anything else you'd want to tell us?"

─ STEP 4: SUCCESS CRITERIA  [45–70 min] ─────────────────────────
  Define observable pass/fail before the sessions start.

  Task 1 success: ________________________________________
  Task 1 failure signal: _________________________________

  Task 2 success: ________________________________________
  Task 2 failure signal: _________________________________

  Task 3 success: ________________________________________
  Task 3 failure signal: _________________________________

  Severity rating for usability issues:
  Critical (3): Blocks task completion
  Major (2): Significantly slows progress or causes errors
  Minor (1): Causes confusion but task still completed

─ STEP 5: LOGISTICS  [70–90 min] ───────────────────────────────
  Session length: _____ min  |  Break between sessions: _____
  Platform / tool: _______________  |  Recording: Y / N
  Prototype link / access: ______________________________

  Observer instructions:
  - Observers do NOT speak during sessions
  - Debrief immediately after each session (10 min max)

  Synthesis plan:
  - Note-taking format: _________________________________
  - Synthesis session date: _____________________________
  - Who attends synthesis: _______________________________

─ OBSERVATION NOTE SHEET — use per session ───────────────────────
  Participant #: ___  Date: _______  Moderator: ____________

  Task        | Completed? | Time    | Issues observed (severity)
  ____________| Y / N      | _______ | ___________________________
  ____________| Y / N      | _______ | ___________________________
  ____________| Y / N      | _______ | ___________________________

  Most memorable quote: "___________________________________"
  Biggest surprise: _______________________________________
  Top issue to fix: _______________________________________

───────────────────────────────────────────────────────────────
QUALITY CHECK
───────────────────────────────────────────────────────────────
  ☐ Task prompts do not reveal where to click or what to look for
  ☐ Success criteria are observable (not subjective)
  ☐ Severity levels are defined before sessions start
  ☐ Synthesis session is scheduled
  ☐ All sessions are within the prototype's working scope

Full facilitation guide: discoverywaypoint.com/techniques/usability-test-plan-workshop-lightweight
Discovery Waypoint — discoverywaypoint.com