How many participants do you need for interview research

•
5 min read

Learn how many participants you may need for interview research based on your goals, audience segments, study scope, and when patterns start repeating.
There is no perfect number of participants for every user interview study.
The right number depends on what you are trying to learn, who you need to learn from, how focused your research question is, and whether new conversations are still bringing in new information.
For user interview research, the goal is not to reach the biggest sample possible. The goal is to speak with enough relevant people to see useful patterns, understand differences, and support the decision your team needs to make.
Start with the research question
Before deciding how many people to interview, start with the question your team is trying to answer.
The narrower the research question and the more homogeneous the participants, the fewer interviews you may need to identify useful patterns.
For example, if you want to understand why new users are confused during one specific onboarding step, you may not need a large number of sessions to start seeing repeated themes.
But if you are exploring a new product direction across different markets, roles, or customer types, you will probably need more interviews to understand how those groups differ.
A simple way to think about it:
Narrow question, specific audience: fewer interviews may be enough
Broad question, multiple personas: plan for more sessions and treat each group separately
High-stakes decision: give yourself more room to validate patterns
The number of interviews should follow the research goal, audience, and level of variation we need to understand, rather than being decided as a fixed number from the beginning.
Think in segments, not just total participants
One common mistake is thinking only about the total number of interviews.
If all participants belong to the same audience, a smaller set of conversations can give your team a strong starting point. But if you are speaking with different types of users, the total number can become misleading.
For example, 12 interviews may sound like a lot. But if those 12 people are split across four very different customer groups, you only have three conversations per group.
That might be enough for early learning, but probably not enough to discover and compare patterns with confidence.
Instead of asking only “How many interviews do we need?”, ask:
How many audience groups are we researching?
Do these groups behave or decide differently?
Are we hearing enough from each group to spot patterns?
This helps your team avoid mixing different participant types into one unclear set of findings.
Look for patterns, gaps, and repetition
In user interview research, teams often look for the point where conversations start repeating similar themes. This is sometimes called saturation.
That does not mean every participant says the exact same thing. It means your team is no longer hearing many new themes, problems, expectations, or objections.
You might be getting close when:
the same needs keep appearing
participants describe similar frustrations
new sessions mostly confirm earlier patterns
your team can explain the main themes clearly
you are not finding major gaps in the audience you intended to study
You may need more sessions when:
each interview brings up something completely new
important audience groups are underrepresented
participants contradict each other in ways you do not understand yet
the topic is complex, sensitive, or highly contextual
the findings feel too thin to support the decision
A good interview plan should leave space to adjust. Start with a reasonable number, review what you are learning, then decide whether more sessions are needed.
A practical starting point
For many focused user interview studies, teams often begin with a small batch of conversations, then add more if the findings still feel incomplete.
You might start with 5 to 8 interviews for a specific audience and research question. If you are working across multiple segments, think about that number per segment rather than as the total study size.
This is not a rule. It is a practical starting point.
The more important question is whether your team has enough quality conversations to understand the topic, recognize meaningful patterns, and move forward without guessing.
Plan for no-shows and replacements
The number you recruit is not always the number of sessions you complete.
People cancel. Schedules change. Some participants may not be the right fit after all.
When planning user interviews, it helps to account for possible no-shows or replacements, especially if your timeline is tight or your audience is hard to recruit.
Screening questions can also help improve participant quality before the session, so your team spends more time speaking with people who match the research goal.
How Useberry Interviews supports interview planning
Useberry Interviews helps teams set up live user sessions, invite participants, manage bookings, add screeners, and keep each session connected to the study it came from.
That connected setup can make planning easier, especially when your team needs to manage participants, track session status, review recordings, and turn conversations into actionable insights afterward.
Instead of treating participant count as a fixed number, your team can plan around the research goal, monitor what you are learning, and keep every conversation organized in one workflow.
See how it works in Useberry: Explore Useberry Interviews
Continue exploring the Interviews Library
If this article helped you think through participant numbers, the next step is planning the study itself: the goal, audience, session structure, roles, and how findings will be used.
Back to the main guide: Useberry Interviews: A Complete Guide to Planning, Running, and Analyzing Better Research Conversations
Continue with: How to plan a user interview study

