{"site":{"name":"Koji","description":"AI-native customer research platform that helps teams conduct, analyze, and synthesize customer interviews at scale.","url":"https://www.koji.so","contentTypes":["blog","documentation"],"lastUpdated":"2026-05-18T13:33:07.692Z"},"content":[{"type":"documentation","id":"85c13b9b-03eb-4ed6-af94-1497dd7626cf","slug":"how-many-interviews-enough","title":"How Many Interviews Are Enough? A Guide to Sample Size","url":"https://www.koji.so/docs/how-many-interviews-enough","summary":"This guide reviews the academic evidence on qualitative sample sizes, including findings from Guest et al. (2006), Creswell (2013), and Hennink et al. (2017). It provides practical frameworks for determining sample size based on population homogeneity, research scope, and project type.","content":"# How Many Interviews Are Enough?\n\nIt's the question every researcher hears: \"How many interviews do we actually need?\" The honest answer is nuanced, but there is solid research to guide you. This article breaks down the concept of saturation, reviews the academic evidence, and gives you practical frameworks for determining your sample size.\n\n## The Short Answer\n\nFor most qualitative research projects with a reasonably homogeneous participant group:\n\n- **6 interviews** will surface the most prominent themes\n- **12 interviews** will get you to thematic saturation for most topics\n- **15–20 interviews** may be needed for highly diverse populations or complex topics\n\nThese numbers come from real research, which we'll walk through below.\n\n## What Is Saturation?\n\nSaturation is the point at which additional interviews stop generating fundamentally new insights. You're still hearing stories and details, but the core patterns have stabilized — new data confirms existing themes rather than introducing new ones.\n\nThe concept was introduced by Barney Glaser and Anselm Strauss in 1967 as part of grounded theory, but it's since become the standard criterion for sample adequacy across qualitative methods.\n\nSaturation doesn't mean you've learned everything there is to know. It means the return on investment of each additional interview has dropped below a practical threshold.\n\n## What the Research Says\n\n### Guest, Bunce, and Johnson (2006)\n\nThis landmark study is the most frequently cited empirical investigation of saturation. The researchers analyzed 60 in-depth interviews from a study in West Africa and tracked when new themes emerged.\n\nTheir findings:\n\n- **73% of all themes were identified within the first 6 interviews**\n- **92% of themes were identified within the first 12 interviews**\n- After 12 interviews, new themes emerged at a very low rate\n\nTheir recommendation: **For studies with a fairly homogeneous population, a sample of 12 is generally sufficient** to reach saturation for high-level thematic analysis. For more granular, detailed coding, more interviews may be needed.\n\n### Creswell (2013)\n\nJohn Creswell, one of the most widely cited qualitative methodology scholars, provides the following general guidelines in his textbook *Qualitative Inquiry and Research Design*:\n\n| Methodology | Recommended Sample Size |\n|---|---|\n| Phenomenology | 3–10 participants |\n| Grounded theory | 20–30 participants |\n| Case study | 1–5 cases |\n| Narrative research | 1–2 individuals |\n| Generic qualitative (incl. thematic analysis) | 5–25 participants |\n\nFor product research, which most commonly uses semi-structured interviews with thematic analysis, the **5–25 range** is relevant, with most studies falling in the **8–15** range.\n\n### Hennink, Kaiser, and Marconi (2017)\n\nThis study distinguished between two types of saturation:\n\n1. **Code saturation** — the point where no new codes emerge (typically reached by **9 interviews**)\n2. **Meaning saturation** — the point where you fully understand the dimensions and nuances of each code (typically reached by **16–24 interviews**)\n\nThis distinction is practically important: if you need broad themes to guide a product direction, 9–12 interviews may suffice. If you need deep understanding of a specific behavior for detailed design, you might need 16 or more.\n\n### Namey et al. (2016)\n\nThis study focused specifically on code saturation in applied health research and found that **80% of all themes were discovered within the first 8 interviews** when the sample was relatively homogeneous. With more heterogeneous samples, the number increased to 16.\n\n## Factors That Affect Your Sample Size\n\nThe right number of interviews depends on several factors:\n\n### Population Homogeneity\n\n| Population Type | Description | Typical Sample Needed |\n|---|---|---|\n| **Highly homogeneous** | Similar role, company size, industry, experience level | 6–10 interviews |\n| **Moderately homogeneous** | Same role but different industries or company sizes | 10–15 interviews |\n| **Heterogeneous** | Different roles, industries, or experience levels | 15–25 interviews |\n\nThe more similar your participants are, the faster you'll reach saturation. If you're interviewing senior product managers at enterprise SaaS companies, 8–10 interviews will likely be sufficient. If you're interviewing \"anyone who has used a project management tool,\" you'll need many more.\n\n### Scope of Research Questions\n\nNarrow, focused research questions saturate faster than broad, exploratory ones.\n\n- \"How do PMs at companies with 50–200 employees prioritize their backlog?\" — Narrow; likely saturates by 8–10\n- \"How do people manage work across multiple tools?\" — Broad; may need 15–20\n\n### Data Richness Per Interview\n\nLonger, more in-depth interviews (45–60 minutes) generate richer data per session. You may need fewer interviews if each one is substantial. Short, shallow interviews (15–20 minutes) require more participants to reach the same depth.\n\n### Analysis Method\n\nBasic thematic analysis requires fewer interviews for saturation than detailed grounded theory or phenomenological analysis. For most product research, basic to moderate thematic analysis is appropriate. Learn more in our [thematic analysis guide](/docs/thematic-analysis-guide).\n\n## A Practical Decision Framework\n\nHere's a practical framework for deciding your sample size:\n\n| Project Type | Population | Recommended N | Reasoning |\n|---|---|---|---|\n| Quick discovery sprint | Homogeneous, focused topic | 5–8 | Surface top themes quickly; time-boxed |\n| Standard product research | Moderately homogeneous | 8–12 | Reach code saturation with good confidence |\n| Deep strategic research | Diverse or complex population | 12–20 | Approach meaning saturation for nuanced understanding |\n| Foundational research | Highly diverse, new domain | 20–30 | Map a wide landscape; build comprehensive understanding |\n\n## How to Know When You've Reached Saturation\n\nIn practice, you can track saturation in real time:\n\n1. **After each interview**, note the new insights (things you hadn't heard before)\n2. **Track the rate of new themes** emerging per interview\n3. **When 2–3 consecutive interviews** produce no fundamentally new themes, you're likely at code saturation\n\nThis doesn't need to be formal. A simple tally of \"new things I learned\" per interview gives you a practical saturation curve.\n\nWith Koji, this process becomes even more visible — as the platform analyzes each interview, you can see themes building and stabilizing across your dataset. When the theme map stops changing meaningfully with new interviews, you know you're approaching saturation.\n\n## The Case for Starting Small\n\nA pragmatic approach is to plan for 8 interviews initially, with the option to extend:\n\n1. Conduct 5 interviews\n2. Do a preliminary analysis — what patterns are emerging?\n3. Conduct 3 more interviews\n4. Check: are new themes still emerging at a meaningful rate?\n5. If yes, conduct 2–4 more. If no, you're likely at saturation.\n\nThis iterative approach avoids both under-researching (too few interviews to be confident) and over-researching (diminishing returns on time investment).\n\n## Defending Your Sample Size to Stakeholders\n\nStakeholders from quantitative backgrounds often challenge qualitative sample sizes. Here's how to respond:\n\n- **Different purpose, different rules.** Qualitative research aims for depth and understanding, not statistical generalizability. The goal is to understand why, not to measure how many.\n- **Cite the research.** Guest et al. (2006) demonstrated that 12 interviews capture 92% of themes for a homogeneous group. This is peer-reviewed, reproducible evidence.\n- **Frame it practically.** \"After 10 interviews, we stopped hearing fundamentally new problems. Adding more interviews would add nuance but not change our strategic recommendations.\"\n- **Compare the alternatives.** A survey of 500 people will tell you 73% find onboarding confusing. Ten interviews will tell you exactly why, where, and how to fix it.\n\n## Further Reading\n\n- [User Interview Guide](/docs/user-interview-guide) — the complete interview methodology\n- [Finding Research Participants](/docs/finding-research-participants) — recruit the right people for your study\n\n## Further reading on the blog\n\n- [Best AI Market Research Tools in 2026: The Complete Buyer's Guide](/blog/ai-market-research-tools-2026) — AI has fundamentally changed market research. This guide compares the leading AI market research platforms—from AI-native interview tools li\n- [AI-Moderated vs Human-Moderated Interviews: Which Should You Choose?](/blog/ai-moderated-vs-human-moderated-interviews) — AI-moderated and human-moderated interviews each have a time and a place. Here is the honest comparison to help you choose the right approac\n- [Best AI Customer Interview Tools in 2026: The Complete Buyer's Guide](/blog/best-ai-customer-interview-tools-2026) — AI has fundamentally changed how product teams conduct customer research. Here are the best AI customer interview tools in 2026 — ranked by \n\n<!-- further-reading:blog -->\n","category":"Research Methods","lastModified":"2026-05-13T00:25:38.788654+00:00","metaTitle":"How Many Interviews? — Koji Docs","metaDescription":"Research-backed guidance on qualitative sample sizes, saturation points, and practical frameworks for determining how many interviews your study needs.","keywords":["sample size","qualitative research","saturation","interview sample size","how many interviews","research methodology","Guest Bunce Johnson"],"aiSummary":"This guide reviews the academic evidence on qualitative sample sizes, including findings from Guest et al. (2006), Creswell (2013), and Hennink et al. (2017). It provides practical frameworks for determining sample size based on population homogeneity, research scope, and project type.","aiPrerequisites":["user-interview-guide"],"aiLearningOutcomes":["Understand the concept of saturation in qualitative research","Apply research-backed guidelines for determining sample size","Adjust sample size based on population homogeneity and research scope","Track saturation in real time during a study","Defend qualitative sample sizes to stakeholders from quantitative backgrounds"],"aiDifficulty":"intermediate","aiEstimatedTime":"8 min read"}],"pagination":{"total":1,"returned":1,"offset":0}}