How Many User Interviews Do You Need? A Field Guide for Product Teams
How to plan, recruit, moderate and synthesize user interviews, with sample size evidence from 4 studies and a bad-question rewrite table for product teams.

How to plan, recruit, moderate and synthesize user interviews, with sample size evidence from 4 studies and a bad-question rewrite table for product teams.

User interviews are one-on-one research conversations where you ask a participant about their experiences, listen, and probe with follow-up questions to learn what they need. Nielsen Norman Group places them in the discovery phase, and Jakob Nielsen's 2026 ranking puts interviews second of 50 research methods by value.
The method looks easy because it resembles conversation. The evidence on sample size, question design and synthesis says otherwise, and most teams stop too early or ask the wrong questions.
This guide covers user interviews end to end, from research goals and recruiting to moderation, bias and synthesis, with the published sample-size studies side by side.
NN/g defines a user interview as "a research method where the interviewer asks participants questions about a topic, listens to their responses, and follows up with further questions to learn more." The output is new knowledge about users: their pain points, mental models, motivations and the vocabulary they use.
Most product teams run semistructured interviews. You prepare a guide of open-ended questions, then follow it flexibly: change the order, skip a question, or chase something unexpected. NN/g contrasts this with a structured interview, where an interviewer reads a fixed script in the same order every time.
Teresa Torres, author of Continuous Discovery Habits, treats customer interviews and user interviews as the same activity with the same techniques.
The most common planning mistake is picking interviews for a question they cannot answer. Interviews tell you what people say about their experience; they cannot tell you whether a design works.
Method | Data type | Best for | Typical sample |
|---|---|---|---|
User interview | Attitudinal (reported) | Needs, motivations, mental models, past experiences | 5 to 17 per segment |
Usability test | Behavioral (observed) | Whether a design works and where it breaks | 5 per round |
Survey | Attitudinal at scale | How common a need or opinion is | Large samples |
The 5-user figure for usability testing comes from Jakob Nielsen and Tom Landauer, whose model found that 5 users uncover 85% of usability issues. That number describes finding interface problems, a narrower task than mapping needs. For more on picking a method, see the UX research methods overview.
Interviews are cheap and remote-friendly. Nielsen's 2026 scoring of 50 methods ranked moderated usability testing first and interviews second, ahead of product analytics and unmoderated testing.
Interviews are also where product decisions get their language. Emmett Shear, then CEO of Twitch, said in a Y Combinator lecture that a large round of user interviews formed the core of Twitch's product feature decisions for the next three years.
NN/g breaks the process into six steps: identify what you want to learn, prepare a guide, pilot it, start easy, build rapport, and follow up and probe. The five phases below group those steps with recruiting and synthesis, which is where most studies actually fail.
NN/g warns that goals that are too broad, such as "learning about users," produce interviews that fail to deliver actionable insights. The first issue on its list of reasons interviews fail is the wrong purpose: using an interview for a question another method answers better.
A usable goal names a behavior and a decision. Compare "understand onboarding" with "learn what made trial users who never invited a teammate stop in their first week, so you can decide whether to rebuild the invite step." The second version tells you whom to recruit and what to ask.
Write 3 to 5 research questions, then check each against the method. If a question asks "can people complete X," move it to a usability test.
Recruit people who match the behavior in your research goal, not just a demographic. Torres suggests that subscription teams responsible for retention talk to engaged and unengaged customers, plus people who recently canceled.
Screen with a short survey before you schedule, where closed and even leading questions are fine. In an r/UXResearch thread, one researcher wrote that "leading questions such as 'did you travel by car?' are perfectly acceptable" when you filter for relevant experience. Keep those questions out of the interview itself; NN/g warns against opening with screener questions because they kill rapport.
Plan for no-shows. Designer Whitney Hess recruits 5 for every 4 participants she needs, and suggests proposing a specific time instead of an open-ended request.
NN/g's interview guide process runs from research questions to brainstormed interview questions, broadened into open-ended ones, arranged in order, with probes prepared. The User Interviews field guide suggests organizing a session around 3 to 6 topics with subtopics, which keeps the guide loose enough to follow the participant.
Start with a grand-tour question ("walk me through a typical day") to warm up, then move to specific past events. Pilot the guide with a colleague or one friendly participant; you will cut questions that confuse people or that you never have time for.
Here is a starting structure for a 45-minute remote session about a past workflow. Adjust the blocks to your research questions, and keep the timings as a budget rather than a script.
Block | Time | What you ask or do |
|---|---|---|
Intro and consent | 0 to 5 min | Who you are, why you are talking, how the recording is used, that there are no wrong answers |
Warm-up | 5 to 10 min | Their role, a typical day, the tools they use for the task you study |
Main story | 10 to 30 min | "Tell me about the last time you..." then probe for sequence, people involved, workarounds and what went wrong |
Second story or contrast | 30 to 38 min | A different recent instance, or one where it went well, to compare |
Prompted topics | 38 to 42 min | Topics from your research questions they never raised, labeled as prompted in your notes |
Wrap-up | 42 to 45 min | "Is there anything I should have asked?" and next steps for the incentive |
The closing question gives the participant a last chance to raise what your guide missed. Leave room for the answer before you end the call.
Write the guide as topics and starter questions, not full paragraphs you will read aloud. If you need consistency across several interviewers, add the exact wording only for the main story prompt and the prompted topics.
Open with easy questions and an honest explanation of why you are there. Then mostly listen: NN/g's facilitation advice is to aim for the participant to speak roughly 80% of the time and to limit observers in the room to 3.
Use silence on purpose.
When a participant says something you did not expect, Shear's advice in the same YC lecture is to drop into "detective mode" and ask them to tell you more. His reason: "people don't like silence, so they'll keep talking to fill the void." The User Interviews guide suggests counting to 5 in your head before you reply.
Record every session with consent. Shear calls recording "like magic" for two reasons: it frees you from note-taking during the conversation, and you can play clips to colleagues who were not there.
Analyze after each interview instead of waiting for the last one. NN/g recommends starting with 5 to 6 participants and analyzing as you go, so you can tell when new sessions stop adding themes.
Spread sessions out when you can. NN/g suggests 2 to 3 per day over a week rather than a single marathon day, which leaves time to write notes and adjust the guide. The Interaction Design Foundation recommends leaving about 30 minutes between sessions.
For the analysis itself, thematic analysis is the standard approach: code the transcripts, group codes into themes, and tie each theme to evidence. Turn the themes into artifacts the team already uses, such as a user journey map or opportunity list.
The honest answer is "fewer than a survey, more than five, and it depends on how varied your users are." The four sources below disagree less than they appear to, once you look at what each one measured.
Study | What it measured | Finding |
|---|---|---|
Customer needs for portable food-carrying devices, 30 interviews | 20 interviews found over 90% of the needs that 30 found; recommend 20 to 30 for 90% to 95% | |
Codes in 30 interviews in Ghana (60 across two countries) | 73% of the Ghana codes in the first 6 interviews, 92% by 12 | |
Systematic review of 23 saturation studies | Saturation at 9 to 17 interviews, or 4 to 8 focus groups | |
Practitioner guidance | 5 is too few for many exploratory studies; start with 5 to 6 and analyze as you go |
The User Interviews field guide says that for most interview studies, "you only need 5 participants." NN/g disagrees, arguing that for many exploratory studies 5 is too few and that the 5-user rule was borrowed from usability testing.
The Guest study shows why both can feel true. Six interviews surfaced 73% of codes, enough for the high-level themes, but the detail kept arriving until about interview 12.
Griffin and Hauser found that a single one-on-one interview identified 33% of needs and two identified 51%. They needed 20 to 30 interviews to approach 90% to 95% of needs in one fairly homogeneous segment.
Scale up when your users split into segments with different jobs, when the decision is expensive to reverse, or when you need the long tail of needs rather than the top five. Recruit separately for each segment instead of mixing them in one pool.
Plan 6 to 8 interviews per segment, analyze after each, and stop when two sessions in a row add no new theme. If you still see new themes at interview 12, your segment is probably two segments.
People are poor predictors of their own future behavior and generous with polite opinions. Rob Fitzpatrick's The Mom Test is built on this: it teaches founders how to learn from customer conversations "when everyone is lying to you."
The fix in every serious guide is the same. Ask about specific things that already happened.
Torres calls this story-based interviewing: ask the participant to tell you about one specific time, then excavate the details. NN/g gives the same advice, noting that asking about specific examples beats asking people to describe what they think is typical.
A story gives you sequence, context, workarounds and emotion. A general answer gives you the participant's idealized version of themselves.
Use this table when you review your guide. Each row turns a question type that produces unreliable answers into one that asks about a real event.
Weak question | Why it fails | Rewrite |
|---|---|---|
"Would you use a feature that does X?" | Future intent; people say yes to be nice | "Tell me about the last time you needed to do X. What did you do?" |
"How do you usually plan a sprint?" | Typical behavior; you get the idealized process | "Walk me through how you planned your most recent sprint." |
"Don't you find the export confusing?" | Leading; agreeing is easier than disagreeing | "What happened the last time you exported a report?" |
"How would you rate onboarding from 1 to 10?" | A survey question; no story | "Tell me about your first week using the product." |
"So you switched because of price?" | Clarifying with your own interpretation | "You mentioned switching. What led up to that?" |
On why leading questions distort data, one r/UXResearch member argued that disagreeing with a leading question takes effort, so participants often go along with it even when they would rather disagree.
Follow-up questions are where a story gets its detail. Keep a short list of neutral probes: "What happened next?", "Why was that important?", "How did you handle it?", "Tell me more about that."
If you need to ask about a topic the participant never raised, ask it near the end. On r/UXResearch, researchers describe this as funneling: start broad, ask directly about the missing topic last, and label the answer as prompted when you report the finding.
Bias enters at three points: who you recruit, how you ask, and how you interpret. Synthesis is where the third one does the most damage, because one person's reading of a transcript becomes "what users said."
Steve Portigal wrote Interviewing Users, now in a second edition (Rosenfeld Media, October 2023). On the NN/g podcast, he and the NN/g host discuss a well-meant habit: helping the participant by offering examples, or sharing your own experiences to seem relatable. Both can taint the participant's account of what they actually do, so keep your stories out of the session.
Watch your reactions too. Nodding hard at the answers you hoped for teaches the participant which answers you want.
Griffin and Hauser had several analysts read the same transcripts and recommend 4 to 6 analysts per study, because each reader catches needs the others miss. On a product team, that means the designer, product manager and engineer each read or watch at least some sessions.
Torres recommends that the product trio attend interviews together: one person leads, and the other two watch and synthesize. This also solves the buy-in problem NN/g lists as the second reason interviews fail.
Write a one-page summary per interview within the same day: who, the key story, quotes, needs and surprises. Then cluster across interviews with thematic analysis or affinity mapping, and keep a link from each theme back to the sessions that support it.
Store recordings and summaries where the team can find them. A research ops practice, even a shared folder with a naming convention, keeps last quarter's interviews usable.
Two changes in 2026 affect how product teams run interviews. Neither replaces the five phases above.
In December 2025, Anthropic invited Claude.ai users to an interview run by Anthropic Interviewer, "a version of Claude prompted to conduct a conversational interview." 80,508 people across 159 countries and 70 languages took part.
The scale is new; the sampling limits are not. Oguz A. Acar noted on LinkedIn that "these are active Claude users who opted into an interview," so the results describe engaged users, not the general population.
Practitioners still report that live conversation catches what an agent misses. "Absolutely nothing beats talking to a customer directly," one builder wrote on X in September 2026, after a week of interviews and onboarding calls. Use AI moderation for breadth on a narrow question, and keep human-led sessions for the follow-ups and judgment calls.
UserTesting announced on January 7, 2026 that it had acquired User Interviews, the recruiting platform whose brand dominates searches for this keyword. The press release puts its panel at over 6 million participants.
Researchers on LinkedIn have asked whether User Interviews will keep its transparent pricing and start-small options under its new owner. If you recruit through a panel, recheck pricing, contract terms and participant quality at renewal. For a wider view of the options, see the UX research tools roundup and the Dovetail review for repository and analysis.
The User Interviews incentive guidance says that for most studies you should aim for $60 to $100 per hour. Its baselines for remote moderated sessions are $80 per hour for consumers and $100 for professionals.
The same guidance says incentives work best when they are tailored to the task, the time commitment and how inconvenient it is to take part.
NN/g's User Interviews 101 tells you to think of an interview as a research study, not a sales session or an informal conversation. If you pitch the product during the session, you collect politeness, not evidence.
The 85% figure for 5 users describes usability problems in a single interface. For needs and motivations, plan for 6 to 12 per segment and let analysis tell you when to stop.
"Would you pay for this?" invites a kind yes. Ask what they did the last time the problem came up, and what they paid for the workaround.
Back-to-back sessions leave no time to adjust the guide or notice early themes. Spread interviews across the week, at 2 to 3 per day when you can.
One analyst's reading becomes the team's truth. Bring at least two more readers into synthesis, the way Griffin and Hauser's multi-analyst approach did.

The gamification market hit $36.46 billion in 2026. These 20 statistics cover market size, a 2019 workplace survey, learning trials, and healthcare RCTs.

Learn the 5 quantitative research designs, 10-step process, statistical decision rules, and 12 tools, with UX-specific guidance for product teams.

Thematic analysis on UX interviews: six current phases, codes vs themes, and one published-quote walkthrough. Includes saturation and common mistakes.