TL;DR: For qualitative usability testing, 5 users per audience segment uncovers roughly 85% of usability problems — the classic finding from Jakob Nielsen and Tom Landauer, based on an average problem-discovery rate of 31% per user. But "5 users" only holds when each problem is fairly easy to hit. For low-frequency issues, complex flows, or multiple distinct user groups you need more (9 users at a 20% discovery rate, 18 at 10%). For quantitative metrics — task-success rate, time-on-task, SUS benchmarking — you need 20–40 participants, not 5. The real rule isn't a number; it's match your sample to your goal. And when you need interview-level depth at survey-level scale, AI-moderated interviews let you reach 30–50 users in a week for a fraction of the cost.
The short answer
How many users you need depends entirely on what kind of answer you want:
- Finding usability problems (qualitative): 5 users per segment finds ~85% of issues. Run 2–3 small rounds instead of one big one.
- Measuring usability (quantitative): 20–40 users to get statistically meaningful task-success rates, completion times, or System Usability Scale scores.
- Multiple distinct audiences: 5 users per group — a B2B tool with admins, end users, and buyers needs ~15, not 5.
- Subtle or rare problems: 10–18+ users, because each individual user has a low chance of triggering the issue.
If you only remember one thing: the famous "5 users" number is a rule for discovering problems in a single, homogeneous group — not a universal answer for every research question.
Where the "5 users" rule comes from
The rule traces back to a 1993 study by Jakob Nielsen and Thomas Landauer, popularized in Nielsen's widely cited 2000 article "Why You Only Need to Test with 5 Users." They built a mathematical model showing that a qualitative test with 5 participants typically surfaces about 85% of the usability problems in an interface — and that the cost-benefit curve flattens fast after that. Testing a sixth, seventh, or eighth user mostly re-finds problems you've already seen.
The strategic takeaway was never "only ever test 5 people." It was "run more, smaller tests." Three rounds of 5 users — test, fix, re-test — beats one round of 15, because you catch and repair problems iteratively instead of documenting them all at once and shipping the same flawed design.
The formula behind 5 users (and why it breaks)
The model is simple: N = 1 − (1 − L)^n, where N is the proportion of problems found, n is the number of users, and L is the average probability that any single user encounters any given problem.
Nielsen and Landauer measured an average L of 31% across their projects. Plug that in and 5 users find ~85%. But L is an average — and it's the assumption that quietly breaks the rule:
- If L = 31%, 5 users find ~85%.
- If L = 20%, you need about 9 users to reach 85%.
- If L = 10% (subtle, low-frequency problems), you need roughly 18 users.
And the variance is real. In a landmark re-examination, researcher Laura Faulkner found that while 5 users averaged 85% problem detection, individual runs of 5 ranged from as low as 55% to as high as 95% depending on which 5 people you happened to recruit. With a single small sample, you might catch nearly everything — or miss nearly half. More users narrows that gap. This is the same diminishing-returns logic behind data saturation in qualitative research: you keep sampling until new sessions stop surfacing new themes.
Qualitative vs quantitative: two different sample sizes
This is where most "how many users" debates go wrong — people argue about a number without agreeing on the type of study.
Qualitative usability testing answers "what's broken and why?" You watch people attempt tasks, hear them think aloud, and find problems to fix. Here, 5 per group is genuinely efficient.
Quantitative usability testing answers "how usable is it, numerically?" — task-success rate, error rate, time-on-task, or a System Usability Scale score you can benchmark over time. Numbers need a bigger sample so a single outlier doesn't swing the result. The consensus range is 20–40 participants, with analysis typically reported at 90% confidence intervals. For context on what "good" looks like, a task-completion rate above 78% is considered above average, and many teams require ~80% success before calling a feature launch-ready. See our usability metrics guide for the full benchmark set.
Trying to compute a reliable task-success percentage from 5 users is like calling an election from 5 voters — the math simply isn't there.
How many users by research goal
| Your goal | Study type | Recommended sample |
|---|---|---|
| Find the obvious usability problems | Qualitative | 5 per segment |
| Catch subtle / low-frequency issues | Qualitative | 10–18 |
| Test multiple distinct user groups | Qualitative | 5 per group |
| Benchmark task-success / time-on-task | Quantitative | 20–40 |
| Compare two designs (A/B) | Quantitative | 20–50+ per variant |
| Continuous discovery / "why" behind behavior | Interviews | 15–30+ |
For the underlying method and a step-by-step plan, see the full usability testing guide and our moderated vs unmoderated research breakdown.
The hidden assumption that wrecks the 5-user rule: segments
The single most common way teams misapply "5 users" is by ignoring audience segmentation. The rule assumes one homogeneous user group. But if your product serves meaningfully different people — say, a B2B platform with administrators, daily end users, and economic buyers — each group hits different problems. Five admins tell you almost nothing about what confuses end users. You need 5 per distinct segment, which is why a serious study often lands at 15–20 even when each individual group only needs 5.
Why teams are rethinking sample size in 2026
The "5 users" rule was built for an era when every additional participant meant another scheduled session, another moderator hour, and another transcript to code by hand. The cost curve was steep, so 5 was pragmatic. That economic constraint is collapsing.
With AI-moderated interviews and usability sessions, the marginal cost of one more participant approaches zero. You can run 30, 40, or 50 sessions in parallel and have every transcript analyzed thematically the moment it finishes — so the trade-off that made 5 attractive (more users = more cost and more manual analysis) largely disappears. You get the qualitative depth of small-N testing and enough scale to trust the numbers.
How Koji changes the math
Koji is an AI-native customer research platform that runs AI-moderated voice and text interviews at scale. Instead of choosing between "5 users, fast" and "40 users, expensive," you get both:
- Depth at scale: Launch a study and have 30–50 people complete an AI-moderated session in days, each one probed with intelligent follow-ups — no moderator fatigue, no scheduling Tetris.
- Structured + open in one study: Combine all six structured question types — open_ended, scale, single_choice, multiple_choice, ranking, and yes_no — so you capture quantitative signals (a 0–10 ease rating, task success) and the qualitative "why" in the same session.
- Automatic thematic analysis: Every transcript is coded automatically, so a 40-person study takes the same analysis time as a 5-person one — minutes, not weeks.
- One-click reports: Go from raw sessions to a shareable insight report without manually tagging a single transcript.
The "5 users" rule was a smart workaround for an expensive process. In 2026, the smarter move is to size your sample to your actual question — and use AI-moderated interviews to make bigger, better-segmented studies as cheap and fast as the old 5-user test.
Ready to run usability research without the sample-size compromise?
Koji lets you go from question to insight in hours, not weeks — with no research expertise required and no moderator bias. Talk to enough of the right users to be confident, and let AI handle the moderation and analysis. Start with Koji and turn usability testing from a staffing problem into a one-click workflow.
Related reading: How Many Customer Interviews Do You Really Need? · Usability Testing: The Complete Guide for Product Teams (2026) · Best Usability Testing Tools in 2026
