Latest / 5 Minute UX / Determining How Many Participants a Qualitative Study Needs
Transcript
- 0:08This lesson is Determining How Many Participants a Qualitative
- 0:11Study Needs. Let's get started.
- 0:19The first step in planning any study is defining the research
- 0:21approach as qualitative or quantitative, because the method
- 0:24dependency dictates the sample size you need. If you’re aiming
- 0:26for statistical validity, you’ll need twenty to forty
- 0:29participants per round, but that’s not what we’re doing
- 0:31here. For qualitative usability testing, the consensus in the
- 0:33U.X. field is to recruit five to eight users per group for each
- 0:36round. This specific range is considered sufficient for
- 0:38identifying usability problems and achieving sufficient data
- 0:41coverage for qualitative insights. You don’t need
- 0:43hundreds of people to find where the design breaks; you just need
- 0:45enough eyes to spot the recurring friction points. When
- 0:48you stick to this five-to-eight participant guideline, you
- 0:50ensure your study remains focused on deep, actionable
- 0:52feedback rather than broad, shallow metrics. This
- 0:54distinction is crucial because it prevents you from wasting
- 0:57resources on unnecessary recruitment while still
- 0:59capturing the critical issues that matter most to your users.
- 1:01By establishing this baseline, you set the stage for iterative
- 1:04learning, which means you can plan multiple rounds of research
- 1:07instead of one massive, static test. The goal isn’t to count
- 1:09every single error in the entire population, but to uncover the
- 1:12most significant barriers to success early in the design
- 1:14process. Once you’ve locked in this smaller sample size, you’re
- 1:17ready to explore why breaking your research into multiple
- 1:19rounds outperforms a single large study.
- 1:27You might feel tempted to recruit fifteen or twenty people
- 1:29for a single large study, thinking that more participants
- 1:32mean better data, but this is actually a common pitfall that
- 1:34significantly reduces your learning opportunities. When you
- 1:37run one massive session, you lock yourself into a static
- 1:39version of the design, which means you miss the chance to
- 1:41iterate based on early findings. The reason is that qualitative
- 1:44research thrives on iteration, not volume, so splitting that
- 1:46group into multiple five-person studies provides three distinct
- 1:49opportunities to learn about the design and make revisions. By
- 1:52breaking your recruitment plan into smaller chunks, you create
- 1:54space for the design to evolve between each round of testing.
- 1:57After the first five users, you identify critical issues and
- 1:59revise the design immediately, rather than waiting until the
- 2:02end of a long study to see what went wrong. This approach allows
- 2:04you to uncover hidden issues that might have been masked by
- 2:07other problems, or new issues introduced by your own design
- 2:09changes. Multiple smaller tests offer more opportunity to impact
- 2:12the product or service than one large test ever could. The
- 2:14trade-off is clear: you sacrifice the comfort of a
- 2:16single, large dataset for the agility of rapid improvement.
- 2:19Each round of testing becomes a checkpoint where you can
- 2:21validate whether your previous fixes actually worked, or if
- 2:23they introduced new friction. This iterative process ensures
- 2:26that the final product is shaped by continuous feedback rather
- 2:28than a single snapshot in time. You are not just gathering data;
- 2:31you are actively refining the experience with every cycle of
- 2:33observation and adjustment. So when you plan your next study,
- 2:36resist the urge to scale up the participant count in one go.
- 2:38Instead, apply the strategy of splitting large studies into
- 2:41multiple smaller rounds for iterative revision. This method
- 2:43ensures that every hour of testing contributes directly to
- 2:46design improvements, maximizing the value of your research
- 2:48budget. You will find that three focused sessions yield far more
- 2:51actionable insights than one sprawling event. This iterative
- 2:53structure sets the stage for understanding how to manage
- 2:56expectations regarding statistical significance versus
- 2:58problem identification, which we will explore in the next
- 3:00section.
- 3:07Let’s look at a specific scenario where a designer plans
- 3:09a single study with fifteen participants to gather more
- 3:12data. This approach is a common pitfall because it reduces
- 3:14learning opportunities by delaying feedback until the
- 3:17entire group has finished. Instead, you should split this
- 3:20into three separate tests with five participants each. This
- 3:22strategy aligns directly with the guideline to recruit five to
- 3:25eight users per group for each round of research. By
- 3:28conducting three tests with five participants each, you create
- 3:31three distinct opportunities to learn about the design and make
- 3:34revisions. After the first five users, you can identify critical
- 3:37issues and revise the design immediately. This iterative
- 3:39process allows you to impact the product or service much more
- 3:42effectively than one large, static test would. The second
- 3:45and third rounds then test the revised design, which helps
- 3:47uncover new issues introduced by changes. Multiple rounds are
- 3:50essential because they reveal problems that were hiding under
- 3:53other issues or unintentionally created during updates. This
- 3:56method ensures you apply the strategy of splitting large
- 3:59studies into multiple smaller rounds for iterative revision.
- 4:01It transforms your research from a single snapshot into a dynamic
- 4:04cycle of improvement.
- 4:12You need to manage expectations because five to eight
- 4:15participants identify usability problems but do not achieve
- 4:17statistical significance. Statistical significance
- 4:19requires at least one percent of the population, which
- 4:22qualitative samples rarely meet. So when you run these small
- 4:24tests, you aren't looking for numerical precision or broad
- 4:27generalizations. Instead, you are aiming for sufficient data
- 4:30coverage for qualitative insights. This distinction
- 4:32matters because it shifts your focus from counting errors to
- 4:34understanding behaviors. Consider how you recruit those
- 4:37specific users to ensure your small sample represents key user
- 4:40themes. Use persona-based recruitment inputs like surveys,
- 4:42interviews, and analytics to ground your selection in real
- 4:45data. These methods help you identify recurring needs and
- 4:47characteristics before you even book the testing room. By
- 4:50relying on this foundational research, you ensure that every
- 4:52participant counts toward solving the right problems. You
- 4:55avoid the trap of picking random people who might not reflect
- 4:57your actual user base. Think about the trade-off between
- 5:00depth and breadth in your current project. Are you trying
- 5:02to prove a metric or uncover a hidden friction point? If you
- 5:05are hunting for issues, trust that the five-to-eight range
- 5:08gives you what you need. You gain the ability to make design
- 5:10revisions between rounds rather than waiting for a massive
- 5:13dataset. This iterative approach allows you to fix critical
- 5:15issues immediately and see the impact of those changes. As you
- 5:18move forward, apply this framework to your next study to
- 5:21ensure you are planning for iteration. You will check
- 5:23whether your group size fits the qualitative range or if you need
- 5:26to split a larger plan. This preparation sets the stage for
- 5:28effective execution and meaningful revisions.
- 5:37Start by asking if your current research plan is qualitative or
- 5:39quantitative, because the approach dictates everything
- 5:42that follows. If you are conducting qualitative usability
- 5:44testing, check whether your group size falls between five
- 5:47and eight users per round to ensure sufficient data coverage.
- 5:49This specific range allows you to identify usability problems
- 5:52without wasting resources on unnecessary participants who add
- 5:54little new insight. If you have recruited more than eight
- 5:57participants, plan to split them into multiple iterative rounds
- 6:00rather than running one massive session. This strategy creates
- 6:02distinct opportunities for design revisions between rounds,
- 6:05allowing you to fix critical issues before they compound. You
- 6:07will uncover hidden issues or new problems introduced by those
- 6:10very changes, which a single large study would likely miss
- 6:12entirely. Ensure you have a framework for planning research
- 6:15that explicitly allows for these design revisions between rounds.
- 6:18Without this structure, you risk treating the test as a one-off
- 6:21event rather than a cycle of continuous improvement. When you
- 6:23apply the five-to-eight participant guideline to plan
- 6:25iterative qualitative usability studies, you transform data into
- 6:28actionable design improvements. This disciplined approach
- 6:31ensures your research directly impacts the product, turning
- 6:33initial observations into refined, user-centered
- 6:35solutions.
- 6:39Welcome to The Take. I'm joined by a fellow practitioner and
- 6:41together we're going to dig into Determining How Many
- 6:44Participants a Qualitative Study Needs — what it means in
- 6:46practice and what's worth remembering.
- 6:49[HOST] The idea of splitting fifteen participants into three
- 6:53separate rounds feels counterintuitive at first. We
- 6:56usually think more data means better insights. [LEARNER]
- 6:59Exactly. But waiting until the end to fix things is a waste.
- 7:02I’d rather know on day two that the navigation is broken. [HOST]
- 7:06That agility is the real win. You fix the blocker, then see if
- 7:10the fix created new friction. [LEARNER] True. But how do you
- 7:13convince stakeholders who want statistical significance from a
- 7:17sample of five? [HOST] You have to reframe the goal. We aren’t
- 7:20counting errors. We are uncovering behavioral barriers.
- 7:23[LEARNER] Right. Five people find ninety percent of the
- 7:27issues. The rest is just noise. [HOST] And now AI tools can
- 7:30synthesize those sessions faster than ever. It makes the
- 7:33turnaround time between rounds even tighter. [LEARNER] I’ve
- 7:37seen that. AI transcripts highlight friction points
- 7:39instantly. It removes the analysis bottleneck. [HOST] That
- 7:43speed allows us to treat research as a continuous loop.
- 7:46Not a gatekeeping event. [LEARNER] So the constraint
- 7:49isn’t time. It’s our willingness to iterate early. [HOST]
- 7:52Precisely. Small batches force us to act. Large batches let's
- 7:56delay.