Back to Skills

usability-testing

Help users conduct effective usability testing. Use when someone is planning user tests, designing prototype validation, preparing usability studies, or trying to understand why users struggle with their product.

1,133stars145forksUpdated 7/9/2026

Security Assessment

Safe(100/100)
Security Score100/100

About usability-testing

A practitioner's guide to running effective usability testing, distilled from frameworks and quotes contributed by 11 product leaders. Rather than prescribing a single method, it structures the work into four steps: clarify the goal (validating a concept, finding friction, or optimizing conversion), choose the right fidelity (Wizard of Oz, fake doors, prototypes, or production testing), design the test (recruiting, scenarios, what to observe), and plan for iteration so findings flow back into development. Core principles anchor each idea to a named leader. Itamar Gilad's "fake it before you build it" argues for fake-door, smoke, and Wizard of Oz tests, validating value propositions with human-powered facades before writing production code, and later for progressing through fish-fooding, dogfooding, and alphas to build confidence. Melanie Perkins notes that as few as 10 random people can reveal representative friction. Uri Levine urges watching users rather than only asking them, and probing "why" when they deviate from the expected path. Kristen Berman insists on testing multiple options relatively rather than a single design. Guillermo Rauch warns about creator bias and overrating one's own product. Judd Antin's Airbnb example, changing seven characters on a button that "felt scary," shows how micro-level copy fixes can move millions in conversion. Noah Weiss frames testing as a team sport, with PMs, engineers, designers, and researchers live-reacting to sessions in a shared Slack thread. The skill supplies clarifying questions to pose and a list of common mistakes to flag: testing only one design, building before validating, trusting internal intuition, ignoring micro-level issues, and testing in isolation. A deep-dive reference collects all 14 insights from the 11 guests. Suitable when planning user tests, designing prototype validation, preparing studies, or trying to understand why users struggle with a product.

FAQ

How many participants do I need?

Small samples work well; the guide cites finding 10 random people online who give astute, representative feedback that surfaces core product issues.

Should I test one design or several?

Always present multiple options and compare them relatively. Single-design testing is treated as ineffective for predicting behavior.

What does "fake it before you build it" mean?

Validate core value propositions with fake-door, smoke, or Wizard of Oz tests, facades where humans perform the automated task behind the scenes, before writing production code.

Why not just ask users what they think?

Direct observation reveals behaviors and needs that surveys miss. Watch what users actually do and ask "why" only when they deviate from the expected path.

Who should attend usability sessions?

Make it a team sport. Have PMs, engineers, designers, and the researcher observe and live-react together, for example in a shared Slack thread, to build shared understanding.

All Files

2 files
references/guest-insights.md9.9 KB
View
SKILL.md4.4 KB
View

Install usability-testing

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill