Product design skills

usability-testing

Use when planning or conducting usability tests — writing test scripts, defining tasks, selecting participants, analysing findings, and turning observations into design actions

Category
Testing and evaluation
Status
Recommended
Use when
  • plan a usability test
  • write a usability test script
  • how many participants do I need for testing
  • analyse usability test findings
  • turn usability findings into design fixes
Works on
  • A working prototype or build to test
  • The core tasks/jobs from the design brief
Produces
  • Task scenarios and a full test script
  • Task success-rate table classified by outcome
  • Severity-ranked findings with design actions
  • Ship / iterate / rethink recommendation
Works with
Claude Code, Codex, Cursor, OpenCode, Amp, Gemini CLI, GitHub Copilot, VS Code, Claude.ai
Tags
usability-testing, severity, qualitative, user-research
Source
Owl-Listener/designpowers by MC Dean · MIT
Related skills
synthetic-user-testingdesign-critiqueresearch-planningsilver-evaluateux-research-workflow

Instructions from SKILL.md

Usability Testing

Testing with real people is how you find out if the design works — not by looking at it, but by watching someone use it.

When to Use

  • After design-builder produces a working prototype
  • Before declaring a design complete
  • When the design-critic flags persona coverage gaps
  • When assumptions about user behaviour need evidence

Process

Step 1: Define What You're Testing

Write 3-5 task scenarios that map to the core jobs in the brief. Each task:

  • Starts with a realistic trigger — "You just bought a new plant and want to add it to the app"
  • Has a clear success condition — "The plant appears in your list with a watering schedule"
  • Does not tell the user how — never say "tap the + button"

Step 2: Select Participants

Recruit 5-8 participants. At minimum include:

  • 1 person who uses a screen reader
  • 1 person over 60
  • 1 person who is not a native speaker of the interface language
  • 1 person with low tech confidence

Reference inclusive-personas for the ability spectrum.

Step 3: Choose Method

MethodWhen to useMinimum participants
Moderated think-aloudNew flows, complex interactions5
Unmoderated remoteSimple tasks, large sample8-12
Guerrilla (hallway)POC validation, time-constrained3-5
Accessibility audit with AT usersAfter build, before ship2-3

Step 4: Write the Test Script

  1. Welcome — explain what you're testing (the design, not them)
  2. Background — 2-3 questions about their relationship to the problem
  3. Tasks — present each scenario one at a time, observe silently
  4. Debrief — "What was hardest?" "What would you change?"

Never help during a task. Silence is data.

Step 5: Analyse Findings

Classify outcomes per task:

  • Completed easily — no hesitation, no errors
  • Completed with difficulty — hesitation or errors but recovered
  • Failed — could not complete
  • Completed wrong — thought they succeeded but didn't

Severity: Critical (blocks 2+ participants), Major (significant difficulty), Minor (noticed but not impeding).

Step 6: Turn Findings Into Actions

Every finding becomes a design action: "[Severity] [What happened] → [Design action] → [Which agent handles it]"

What You Deliver

  • Task success rates table
  • Ranked findings by severity
  • Design actions with agent assignments
  • Recommendation: iterate / ship / rethink

Integration

  • Informed by: inclusive-personas, design-discovery
  • Feeds into: design-lead, design-builder, design-strategist

Supporting files

One more file in this skill's folder. Markdown opens as a page, other text files open as source, and anything else downloads as it is.

Next to SKILL.md1

On this page