plan-usability-test

Plans usability tests end-to-end following Nielsen Norman Group methodology with sample size and mode decisions.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill plan-usability-test-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-usability-test
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/plan-usability-test
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill plan-usability-test-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning a usability test involves defensible decisions about sample size, study mode, recruiting, and piloting that most teams get wrong — reporting fake percentages from 5 users, running one big study instead of iterating, or skipping the pilot. This Skill turns a research question into a complete, defensible test plan grounded in NN/g methodology. ## Core Features & Use Cases - Qual/quant fork and sample sizing: Decides between formative (5 users, 3–4 per divergent segment) and summative studies (~40 for task metrics, ~39 for eyetracking, ~15 for card sorts), with the discovery-curve math to defend small N. - Mode selection matrix: Chooses among moderated/unmoderated × remote/in-person with explicit validity rules, such as requiring moderation for fragile prototypes or "why" questions. - Mandatory pilot with fix-then-freeze: Enforces a dress-rehearsal pilot at least 2 days before the first session and locks the protocol afterward so sessions stay comparable. - Use Case: A designer needs to validate a beta booking flow before release. The Skill produces an 8-section plan: research questions, qualitative study type with an explicit "no metrics claimed" line, 5 participants plus one floater, moderated remote mode with rejected alternatives, task count, logistics, a scheduled pilot date, and stated limitations. ## Quick Start Plan a usability test for our checkout flow prototype and tell me how many participants I need and whether to run it moderated or unmoderated.

Frequently Asked Questions about plan-usability-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How many users do I need for a usability test?

For qualitative problem-finding with one homogeneous user group, 5 users uncover roughly 85% of problems in the tested scope. Divergent segments need 3–4 users each, while quantitative studies need about 40 participants for task metrics.

Is 5 users enough for usability testing?

Yes for qualitative studies, because the discovery curve shows diminishing returns after 5 users with an average 31% per-user problem discovery rate. It fails when segments are genuinely divergent or when stakeholders need statistically meaningful metrics.

Should I run a moderated or unmoderated usability test?

Choose moderated when you need to ask why mid-task, when the prototype might break, or when exploring. Choose unmoderated remote for stable UI, simple concrete tasks, and larger quantitative samples where cost matters.

Can I report success rates from a 5-user study?

No. Numbers from n=5 have margins of error so wide they are noise, so report observed problems with clips and quotes instead. If a metric is required, budget for roughly 40 participants in a separate quantitative study.

Why is a pilot session mandatory before usability testing?

A pilot validates task wording, session timing, screener accuracy, and technology before real participants are burned. After fixes, the protocol freezes so all sessions stay comparable, and pilot data only counts if nothing changed.

When should I not use this usability test planning skill?

Do not use it to write task scenarios, screeners, or run live sessions — those belong to dedicated skills. It also does not cover A/B test design, statistical interpretation, or long-term metric programs like SUS or HEART.