Customer Interview
A customer interview is a one-on-one conversation with a current or potential customer, used to understand their context, problems, behaviors, and the workarounds they rely on today. In product discovery, the goal is to learn about real past experiences in the customer's own words, not to pitch an idea or ask people to predict what they would buy.
How a Customer Interview Works
Most discovery interviews are semi-structured: the interviewer has a goal and a few prompts but follows the conversation where it leads. Strong interviews share a few habits:
- Ask about specific past events. Teresa Torres recommends story-based prompts such as "Tell me about the last time you..." People are poor at summarizing their own behavior and tend to answer general questions with what they think they should do. A specific story brings out real detail: when it happened, which tools were involved, and what went wrong.
- Avoid hypotheticals and pitches. Questions such as "Would you use a product that...?" invite polite, aspirational answers. Showing a solution too early turns the interview into a sales call.
- Focus on behavior and workarounds. What someone already spends time or money on is stronger evidence than what they say they want.
- Capture verbatim language. Customers' exact words are valuable later for synthesis, messaging, and requirements.
- Interview regularly. In continuous discovery, the product team talks to customers every week rather than in occasional large batches.
After the conversations, the team looks for patterns across interviews. Teams keep interviewing a segment until new conversations stop revealing new insights, a point often called saturation.
Why Customer Interviews Matter
Interviews explain the "why" behind behavior that analytics can only count. They reveal the situation in which a problem occurs, how painful it is, and what the customer has already tried. That context is hard to get any other way, especially before a product exists.
They also protect teams from their own assumptions. Hearing several customers describe a problem differently from how the team framed it is one of the fastest ways to correct course. Findings feed directly into personas, empathy maps, and Jobs to be Done analysis.
Interviews have limits: samples are small, and a careless interviewer can lead the answers. Teams often pair them with quantitative data to check how widespread a pattern is. For three behavior-focused questions you can use to test whether a problem is real, see question-driven product discovery.
Customer Interview Example
A founder exploring software for dental practices could ask: "Would you pay for a tool that automates appointment reminders?" Most practice managers would say yes, and the answer would tell her little.
Instead, she asks: "Tell me about the last time a patient missed an appointment." One manager describes phoning twenty patients the afternoon before from a paper list and still having two no-shows. Another explains that their practice software already sends reminders, but patients ignore them. A third says no-shows are rare and their real headache is insurance paperwork.
Three stories reveal more than a dozen yes-or-no answers: the problem varies by practice, an existing tool already partly covers it, and there may be a bigger pain elsewhere.
Customer Interview vs. Usability Test
A customer interview explores a person's experiences, needs, and context, often before any solution exists. A usability test watches someone try to complete tasks with a specific design to find where it confuses them. Both are forms of user research, and they answer different questions.