Customer Interview

What is a Customer Interview?

A customer interview is an extended, conversational inquiry into user experience, context, and behavior. Unlike surveys (which ask predetermined questions to many people) or casual feedback (which lacks rigor), interviews create space for discovery. The interviewer uses open-ended questions and active listening to surface what users cannot articulate in multiple-choice formats or in front of groups. Interviews are tools for building empathy at scale—one conversation with a user struggling through a workflow is worth more than twenty survey responses about “satisfaction.”

The craft of interviewing lies in asking smart questions and then staying quiet. Most inexperienced interviewers fill silence with more questions, interrupting the user’s own thinking. The best interviews create pauses where users elaborate, qualify, or correct themselves. This is where insight lives: in the moments when users explain not just what they did but why, and especially where their reasoning changes as they talk.

Interview Types: Discovery vs. Validation

Discovery interviews are open-ended, early-stage investigations into user context and problem space. Questions are broad: “Tell me about how you approach this task.” “What’s frustrating about your current workflow?” Discovery interviews are generative—they help shape your understanding of the problem before you’ve locked in a solution. They produce narratives and themes, not quantified conclusions.

Validation interviews test whether a specific solution addresses the stated problem. They’re more structured: “Here’s a prototype. Try to do X.” “Does this solve the problem we discussed earlier?” Validation interviews are confirmatory—they check whether your hypothesis about the solution is sound. The output is often binary: does this work for users who had the original problem?

Sample Selection & Saturation

Customer interviews require careful participant selection. Recruiting “available” customers produces biased samples (loyal, patient users willing to talk). The best interviews recruit purposefully: existing users with the specific problem you’re investigating, churned users (who left because the problem wasn’t solved), and target users who haven’t adopted yet (to understand barriers). Diversity in interview recruitment (different roles, company sizes, industries, use cases) ensures you’re not mistaking one segment’s truth for universal truth.

Interview saturation occurs around 8-12 conversations with the target segment. New interviews begin repeating insights already heard. This signals you’ve understood the user landscape, not that interviews are “done”—new segments may reveal different patterns.

Why It Matters for Product People

Customer interviews create what behavioral economists call “concrete specificity”—you stop reasoning abstractly about “users” and start understanding specific humans with specific constraints. An engineer who has listened to five customers debug their workflows, hearing frustration in their voice, will make different design trade-offs than an engineer reasoning from tickets.

For product leaders, interviews are where you detect misalignment between what you believe the problem is and what customers actually experience. Interviews surface underestimated dependencies, reveal what problems matter most (and to whom), and show where your current solution is solving the wrong problem entirely. They’re also political assets: when a leader says “users want X,” customer narratives become evidence.

Related Concepts

Customer interviews feed directly into persona development, assumption mapping, and hypothesis formation. They provide the qualitative foundation that A/B testing and cohort analysis later quantify and validate at scale. Regular interview cadence (monthly with a subset of users) prevents insight decay.