For most user interview projects, 5 to 12 interviews will get you meaningful results, but the right number depends on what type of research you’re doing and how diverse your target audience is. A narrow usability study needs far fewer participants than broad discovery research exploring an unfamiliar problem space.
The 5-User Rule for Usability Testing
If you’re running a qualitative usability study, where you watch people try to complete tasks in a product or prototype, 5 participants is the standard recommendation. Nielsen Norman Group’s research shows that testing with 5 people uncovers almost as many usability problems as testing with a much larger group. The return on investment drops steeply after that fifth participant because you start hearing the same issues repeated rather than discovering new ones.
This number assumes you’re testing one type of user doing one set of tasks. If your product serves two or three distinct groups (say, buyers and sellers on a marketplace), plan for roughly 5 participants per group. Each segment brings its own behaviors, goals, and friction points, so you need a separate baseline for each.
Discovery Interviews Need More People
When your goal is generative research, the kind of open-ended interviewing where you’re exploring a problem, mapping needs, or understanding behaviors before you’ve built anything, you typically need more participants to reach what researchers call “saturation.” That’s the point where new interviews stop revealing new themes or insights.
How many interviews it takes to get there varies quite a bit:
- Narrow scope, similar participants (5 to 8): If you’re interviewing a well-defined group about a specific topic, like patients with a particular condition discussing their treatment experience, a small sample can be enough. The more homogeneous your audience and the tighter your research question, the faster patterns emerge.
- Moderate scope (10 to 15): For most product discovery work, somewhere in this range tends to hit saturation. One academic study found that saturation occurred after 12 interviews, though the researchers noted that 6 would have been sufficient if they only cared about the highest-level themes.
- Broad scope, diverse population (20 to 30): If you’re studying a wide-ranging experience across a diverse group, like how the general population navigates healthcare, you may need 20 to 30 interviews to capture 90 to 95 percent of all relevant needs. Marketing researchers studying customer needs for a consumer product landed on a similar range.
The practical advice: start with 5 or 6 interviews and analyze them as you go. If you’re still uncovering new themes and generating new codes after that batch, recruit a few more. Keep going until each new interview mostly confirms what you’ve already heard rather than surfacing something unexpected.
How Iterative Testing Changes the Math
If you’re testing and improving a design at the same time, a method called RITE (Rapid Iterative Testing and Evaluation) uses a different structure. You start with 3 participants, fix any obvious usability issues between sessions, then test with 2 more. If those 2 sessions reveal no new problems, you’re done at 5 total. If new issues surface, you add another round of 3 participants and repeat until the design stabilizes.
This approach works well when you can make quick changes to a prototype between sessions, like updating labels, moving buttons, or rewording instructions. Issues get sorted into categories: things with an obvious fix you can implement immediately, things that need more time to address, and things that need more data before you understand the root cause. The total participant count stays small because you’re solving problems as they appear rather than cataloging everything and redesigning after the study ends.
Factors That Push the Number Up or Down
Several things influence where you should land within these ranges. The diversity of your user base matters most. A B2B tool used by one type of specialist has a narrower range of behaviors than a consumer app used by millions of people with different backgrounds and goals. The more varied your audience, the more interviews you need to see the full picture.
The specificity of your research question also plays a role. “How do people feel about managing their finances?” will require more interviews than “What frustrates users about the transfer flow on our mobile app?” Broader questions produce more varied answers, which means more data is needed before patterns stabilize.
Your confidence requirements matter too. If you’re making a quick design decision that’s easy to reverse, 5 interviews giving you a directional signal may be plenty. If you’re informing a product strategy that will shape months of roadmap work, investing in 15 to 20 interviews gives you a more complete foundation.
A Practical Starting Framework
Rather than committing to a fixed number upfront, plan your research in waves. Schedule an initial batch of 5 or 6 interviews. After each session, do a quick debrief: what did you learn that was new? By the third or fourth interview, you’ll have a sense of whether themes are converging or still spreading out. If you’re still surprised by what you hear after 6, recruit another small batch. If the last two interviews mostly repeated earlier findings, you’ve likely reached saturation and can stop.
This rolling approach saves you from two common problems: stopping too early and missing important patterns, or scheduling 25 interviews when 10 would have been enough. It also lets you sharpen your interview questions between batches as your understanding of the problem deepens, which makes later interviews more productive than earlier ones.