3.4Customer Discovery Interviews

In Brief

Description

Customer discovery interviews are one-on-one conversations with potential customers to learn what problems they actually have, how they currently solve them, and what they would change. They are generative — you are not validating a feature or testing copy; you are mapping the problem space before you build anything. The single most important rule of the method is that questions probe past behavior, not future intent. “What did you do the last time this came up?” produces signal; “Would you use a tool that did X?” does not.

The method has several common variations. Most interviews are 1:1, but panel interviews (one researcher, two or three customers from the same segment) work when you want to surface how customers describe the problem to each other rather than to you. In-person sessions are the default in B2B and produce the richest observation data — body language, environment, what is on the customer’s screen — but remote sessions over Zoom or Google Meet have become the norm post-2020 and now reach customers no in-person session ever could. Structured interviews follow a tight script and are easier to compare across customers; semi-structured interviews keep the script as a backbone but follow whatever thread the customer pulls on, and tend to produce the unexpected findings that change product direction. Most experienced interviewers default to semi-structured.

Customer discovery interviews sit at the front of the generative-research arc. They typically come before Storyboard the Pain, Card Sorting - Pain Points, and any quantitative pass like a Closed-Ended Survey. The output of a good interview round is a sharper customer persona, a ranked list of pains worth investigating, and a much shorter list of assumptions you were carrying that the data did not support.

How to

Prep AI Prompt

1. Define the learning goal. Write one sentence: “I want to learn whether [target customer] currently struggles with [problem space], and how they handle it today.” If you cannot finish that sentence, you are not ready to interview yet — go back to your customer hypothesis.

2. Write down your customer-persona assumptions. What you currently believe about who the customer is, what they do, and what they care about. The interviews will test these assumptions; you cannot tell what the data is telling you if you have not stated the prior.

3. Draft a screener. Three to four short closed-ended questions that confirm the person you are about to interview matches the segment you are trying to learn about. Ask them on the recruiting form, not at the start of the call. See Alexander Cowan’s customer discovery handbook for screener examples.

4. Write the interview guide. Eight to ten open-ended questions focused on past behavior, not hypotheticals. The classic backbone — adapted from Justin Wilcox — covers:

   • “What’s the hardest part about [problem context]?”
   • “Can you tell me about the last time that happened?”
   • “Why was that hard?”
   • “What, if anything, have you done to solve that problem?”
   • “What don’t you love about the solutions you’ve tried?”

   Treat the guide as a backbone, not a script. Follow whatever thread the customer pulls on.

5. Recruit the interviewees. Five interviews is a defensible minimum for early discovery; 8-12 is the saturation range within a single segment (Guest, Bunce, Johnson 2006); some practitioners run dozens before drawing conclusions. For sourcing and outreach guidance see the recruitment notes in Card Sorting - Pain Points.

6. Set up logistics. Confirm consent before recording (legal requirements vary by jurisdiction). Prepare a notes template, the recording tool you will use, and any thank-you gift (a $5–$50 gift card is typical for B2C consumers; B2B specialists may expect more or refuse compensation).

7. Pilot the guide. Run one practice interview with a colleague or a friendly customer before going live. Pilots almost always surface a leading question, an ambiguous phrasing, or a question whose answer you can already predict.

Analysis AI Prompt

Are you able to listen and record data based on the following?

• Job: What activities are making the customer run into the problem?
• Obstacle: What is preventing the customer from solving their problem?
• Goal: If they solve their problem, then _____?
• Current solution: How are they solving their problem?
• Decision trigger: Were there pivotal moments where the customer made key decisions about a problem?
• Interest trigger: Which questions did the customer express interest in?
• Persons: Are there any other people involved with the problem or solution?
• Emotions: Is there anything specific that causes the customer to express different emotions?
• Measurement: How is the customer measuring the cost of their problem?