Skip to content
Skills Library
Design & UX · Testing

usability-testing

/usability-testing

Watch real users attempt real tasks to find where a design fails, with few participants and honest tasks. Use when validating a design or diagnosing why users struggle, before or after building.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Watch real users attempt real tasks to find where a design fails, with few participants and honest tasks. Use when validating a design or diagnosing why users struggle, before or after building.

Original author description

Watch real users attempt real tasks to find where a design fails, with few participants and honest tasks. Use when validating a design or diagnosing why users struggle, before or after building.

How it works

  1. Method
  2. Boundaries
Original SKILL.md headings · 52 lines, 424 words
SKILL.md preview
---
name: usability-testing
description: Watch real users attempt real tasks to find where a design fails, with few participants and honest tasks. Use when validating a design or diagnosing why users struggle, before or after building.
---

# Usability testing

You cannot see your own design's flaws; you know what everything means and
where everything is. Usability testing replaces that blindness with
evidence: watch real users try to do real tasks, and the problems reveal
themselves. A handful of sessions finds most of what is wrong.

## Method

1. **Test with few users, often.** Around five participants surface the
   large majority of usability problems; you do not need statistical
   samples to find that people cannot find the button. Prefer frequent
   small rounds (test, fix, test again) over one big study (see
   wireframing-prototyping: test early on cheap artifacts).
2. **Give tasks, not a tour.** Ask participants to accomplish a realistic
   goal ("sign up and invite a teammate"), then watch. Do not demo or
   explain; the test is whether they can do it without you. A leading task
   ("click the blue Invite button") tests nothing.
3. **Watch what they do, discount what they say.** Behavior is truth;
   opinions are noise. Where they hesitate, misclick, backtrack, or give
   up is the finding, regardless of whether they later say they "liked
   it". People are polite and are poor predictors of their own behavior
   (see customer-interviews' same lesson).
4. **Ask them to think aloud, and stay quiet otherwise.** Have them
   narrate what they are trying, expecting, and confused by, so you hear
   the mental model. Then resist the urge to help or explain when they
   struggle: the struggle is the data. Silence is hard and essential.
5. **Test at the right fidelity and stage.** A paper or clickable
   prototype tests structure and flow before building (cheapest fixes; see
   wireframing-prototyping); the real product tests the true experience.
   Test before you build to avoid building the wrong thing, and after to
   catch what only reality reveals.
6. **Turn observations into prioritized fixes.** Collect where users
   struggled, cluster the recurring issues, and rank by severity (how
   badly it blocks the task, how many hit it). Fix the blockers first, and
   retest to confirm the fix worked and did not create a new problem (see
   the loop in ml-error-analysis, applied to UX).

## Boundaries

- Usability testing finds problems in a design that exists (or is
  prototyped); it does not tell you what to build, which is discovery's
  job (see product-discovery, customer-interviews). The two are different
  research.
- Small-n qualitative testing reveals problems, not their frequency in the
  population; pair it with analytics (funnels, drop-off) for the magnitudes
  (see user-activation).
- A clean usability test does not guarantee accessibility; test with
  assistive technology and diverse users too (see accessibility-review,
  screen-reader-testing).

Versions

RepositoryScoreLicence
This page · Amey-Thakur/AI-SKILLS100MIT
rampstackco/claude-skills100MIT
owl-listener/designpowers90MIT
jacob-balslev/skill-graph90Apache-2.0

Database snapshot: 13.11.2026 · package version f2efcbb555fe (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90usability-test
    Use to validate that a design actually works for real people — when a flow is built or prototyped and you need to know if users can do the job. Watch them attempt real tasks, stay silent, and let behavior (not opinion) surface the problems.
  • 100ux-heuristic
    Conduct heuristic evaluation of user interfaces using Nielsen's 10 usability principles. Use this skill when the user needs to audit a website, app, or interface for usability issues, prioritize UX improvements, or conduct a quick expert review without user testing — even if…
  • 90testing-product-usability
    Use when testing product usability is required during ux work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
  • 100v1-reviewing-usability
    Use when reviewing a UI, product flow, prototype, or form for usability and user-error risk. Triggers on "review this UI", "usability review", or "confusing interaction".
  • 90ux-analysis
    Finds real usability problems in a running UI and proves each one before it is reported. Walks the user's tasks step by step, captures screenshots, runs machine checks, has two independent helpers evaluate (heuristics and cognitive walkthrough), maps any data you hand over to…
  • 90usability-test-plan
    Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use `test-scenario` (prototyping-testing).

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.