Recommended Free Tools
Customer discovery interviews help you test whether a specific group of people has a consequential problem—not whether they like your proposed product. Ask about a recent real incident, what the person did, and what it cost them in time, money, effort, or missed results. Treat what they actually did as evidence; treat predictions and compliments as opinions.
What customer discovery interviews can—and cannot—tell you
A discovery interview is a learning conversation used to test a problem hypothesis: that a defined customer group regularly encounters a particular difficulty. It is not a focus group for collecting reactions to an idea, and it is not a sales call. Steve Blank describes customer development as hypothesis testing, not a focus group: Customer Development Is Not a Focus Group.
Interviews can reveal how people currently handle a situation, how often it arises, what consequences follow, and whether they have made a meaningful effort to address it. They do not, on their own, establish how common the problem is across a market or prove that a particular solution will sell. Those claims require later, separate tests.
Prepare a testable problem hypothesis
Define the group and the uncertainty
Before contacting anyone, write down whom you want to understand and what you are uncertain about. For example: “Independent retailers who reconcile orders across two sales channels spend time correcting stock discrepancies.” This is a question to investigate, not a conclusion to lead participants toward.
Decide what evidence would make you strengthen, revise, or drop the hypothesis. Look for specific episodes, consequences, workarounds, repeated effort, or attempts to find and pay for alternatives. These are signals to investigate, not automatic proof of a business opportunity.
Recruit people with relevant experience
Invite people who have actually encountered the situation, rather than people selected because they are likely to approve of your idea. In an organization, the people who experience the problem may differ from the people who influence a purchase or control the budget. Speak with the relevant users, decision-makers, influencers, or buyers as appropriate; do not assume one person can represent every role.
Set expectations in the invitation. If a participant might expect a sales pitch, say that you want to learn how they handle a particular part of their work and that the conversation is not a sales call. Blank’s guidance on corporate customer development emphasizes arranging the meeting as a learning conversation: Solving the Innovator’s Dilemma – Customer Development in a Big Company.
Rank #2
Prepare a flexible guide
Write a short sequence of open prompts, then practice the conversation once. Use the participant’s own words and follow relevant details instead of reading every question mechanically. Do not open with a demo, value proposition, or product hypothesis: first establish whether the problem exists and matters to them. Blank’s interview resources cover preparation, dry runs, interview flow, and common mistakes: Steve Blank Slides/Videos.
Ask about a real, recent incident
Start with an open question about the last time the situation occurred. Strategyzer recommends asking, “When is the last time you struggled with this particular challenge?” and probing for evidence rather than accepting general impressions. Dr. Alex Osterwalder puts the principle plainly: “Asking for opinions rather than facts is the single biggest error in customer discovery interviews.” (The One Biggest Error in Customer Interviews: Mistaking Opinions For Facts.)
Use prompts like these, adapting the wording to the subject and the problem you are exploring:
- “Tell me about the last time you ran into [situation]. What happened?”
- “What were you trying to get done?”
- “What did you do next? What else did you try?”
- “What was difficult, frustrating, or costly about that?”
- “How often does this happen? When was the previous time?”
- “How did you decide whether your workaround worked?”
- “Did you look for another solution, ask anyone for help, or spend money? What happened?”
- “You said it needs to be faster. How long does it take today, and what would count as a meaningful improvement?”
Keep probing until you understand the situation, actions, and outcome. “It takes too long” is a starting point, not a measure; ask how long it takes now and what result would count as a meaningful improvement. Likewise, a claimed workaround matters more when the person can describe when they used it and what happened. Strategyzer’s guidance emphasizes tying statements to past behavior and asking how people judge success or failure: The One Biggest Error in Customer Interviews: Mistaking Opinions For Facts.
Keep the conversation neutral
Your role is to understand the participant’s experience, not to win agreement with your hypothesis. Ask a follow-up without implying that one answer is better than another. Allow the conversation to move naturally when a detail helps explain what happened.
Free tools Windows power users keep installed
One-click scans. No signup required.
Delay questions such as “Do you like this idea?”, “Would you buy this?”, “Would you use a tool that…?”, or “Which solution do you prefer?” These ask for hypothetical opinions, not observed behavior. Showing a concept too early also muddies the evidence: a negative reaction might mean the solution is unappealing, or that the underlying problem is not important. Strategyzer recommends establishing problem evidence before evaluating a proposed solution: “Problem” vs Solution In Customer Interviews.
Listen for concrete episodes, repeated effort, workarounds, consequences, and actual attempts to find or pay for alternatives. Do not treat enthusiasm, frustration, or one dramatic story as proof by itself. The useful question is what happened, in what context, and whether similar evidence appears among other relevant people.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Turn interview notes into a decision
Record observations separately from interpretations
After each conversation, note enough context to understand the example later. Capture the participant’s relevant role or situation, what triggered the problem, what they did, the workaround, the consequence, frequency if known, evidence of effort or spending, and questions that remain unresolved. Separate direct statements and observed behavior from your interpretation; otherwise a team can mistake its theory for the participant’s experience.
Compare patterns and counterexamples
Review conversations against the same problem hypothesis. Look for recurring contexts and behaviors, as well as examples that contradict your expectation. If only a narrower group describes the problem, revise the segment. If participants describe a different difficulty, revise the problem. If the examples do not show meaningful consequences or action, do not upgrade polite interest into evidence.
Blank’s customer-development approach treats interviews as tests of hypotheses, while Strategyzer has highlighted the practical challenge teams face in turning differently structured interview notes into patterns and decisions. The 2026-01-21 event page describes its platform and an interview widget for structuring, conducting, and analyzing interviews; feature availability and current terms may change, so teams should check the current product information before relying on a specific capability: Run customer interviews that produce insights, not notes.
Choose the next step based on the evidence
Use what you heard to decide whether to keep exploring the problem, narrow the customer segment, revise the hypothesis, or move to a later solution or demand test. Do not use a universal interview-count threshold: the cited guidance does not establish a statistically validated number of conversations. The appropriate next step depends on whether you can explain the evidence and what important uncertainty remains.
What to do after problem discovery
Once a problem hypothesis has credible support, test solution fit separately. Explore whether a proposed approach helps people accomplish the task, then test demand with evidence appropriate to the decision you need to make. A discovery interview can tell you what someone did and described; it cannot turn a hypothetical purchase answer into a sale or make a handful of interviews representative of a market.
For a deeper account of customer development, Steve Blank’s course reading page references his book The Four Steps to the Epiphany alongside customer-discovery material: Innovation and Entrepreneurship 2010.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
