Skip to content

Chapter 3 of 7

Sampling, Recruitment, and Ethics

A user segment is a meaningful subset of customers who share similar goals, constraints, or behaviors. Recruiting quality participants for that segment is so important that weak fit leads to misleading findings, no matter how polished the interview guide is. Recruitment uses a participant screener, a set of questions that filter participants by relevant traits such as role, behavior, and recency. Good screener questions are specific, behavior-based, hidden from the candidate so the right answer is not obvious, and disqualifying when criteria are not met. Screening criteria should be split into must-haves, which disqualify a participant if missing (such as making purchasing decisions for the category), and nice-to-haves, which improve fit but are not dealbreakers and help balance the sample.

Three non-probability sampling approaches dominate qualitative work. Purposive sampling deliberately chooses participants who match pre-defined traits relevant to the research question. Snowball sampling recruits through referrals from existing participants and is appropriate for hard-to-reach or specialist populations, though it can amplify bias if referrals are homogeneous. Convenience sampling recruits whoever is easiest to reach, such as coworkers or social followers; it is fast but rarely representative and should be flagged as a limitation in findings. In qualitative research, sample size is typically guided by saturation rather than statistics: most interview studies reach thematic saturation somewhere between five and thirty well-chosen participants per segment, depending on segment heterogeneity. Quantitative studies, by contrast, use a power analysis — a statistical calculation estimating the sample size needed to detect a given effect size with a chosen confidence level and power.

Ethical and practical recruitment details matter. Researchers should also distinguish behavioral questions, which ask what people actually did (last action, frequency, tool used), from attitudinal questions, which ask what people say they believe, prefer, or intend, since the two often diverge. Interviewing extreme users, those at either end of a behavior spectrum such as power users or complete non-adopters, surfaces unmet needs, workarounds, and constraints that average users blur. Participant incentives should be calibrated to the expected time, effort, emotional labor, and the participant's role: too low reduces completion quality, while too high can coerce or attract the wrong participants. Informed consent ensures participants understand the study's purpose, what will happen with their data, any risks, and their right to stop, and then voluntarily agree, usually documented in writing. A research participant NDA protects confidential product plans, designs, or customer data while still allowing participants to speak honestly about their own experience. In academic and medical contexts, an Institutional Review Board (or equivalent) reviews the study to ensure risks are minimized, consent is informed, and vulnerable populations are protected.

All chapters
  1. 1Foundations of Customer Research
  2. 2Qualitative Research Methods
  3. 3Sampling, Recruitment, and Ethics
  4. 4Customer Understanding Frameworks
  5. 5Synthesis and Insight Generation
  6. 6Quantitative Research and Measurement
  7. 7Sharing Research and Driving Decisions

Drill it

Reading is not remembering. These come from the Customer Research deck:

Q

What is customer research?

Customer research is the disciplined process of learning how customers think, behave, and make decisions so teams can design better products and messaging.

Q

Why is customer research valuable?

It reduces guesswork by grounding decisions in real customer evidence instead of assumptions.

Q

What is the difference between qualitative and quantitative research?

Qualitative research explores motivations and patterns in depth, while quantitative research measures scale, frequency, and statistical confidence.

Q

What is a customer interview?

A structured conversation used to understand needs, context, workflows, frustrations, and decision criteria.