Free tools Windows power users keep installed
One-click scans. No signup required.
Customer discovery interviews help you learn whether a defined group of people has a consequential problem by asking about what they have actually experienced and done. Start with the problem, not your proposed product: a recent, specific example is more useful than a person’s opinion about an idea or prediction about what they might buy.
These conversations are exploratory. They can help you refine a problem hypothesis, but they do not establish market size or prove that a solution will sell.
As an Amazon Associate I earn from qualifying purchases.
What a useful discovery interview can tell you
A discovery interview is a learning conversation about a person’s situation, behavior, and needs. It is not a focus group, product demo, or sales call. Steve Blank describes customer discovery as testing hypotheses about customers and their problems, rather than treating discussion as proof that a business idea will work: Customer Development is Not a Focus Group.
Recommended Free Tools
The central distinction is between evidence and approval. Dr. Alex Osterwalder of Strategyzer puts it this way: “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.
- Problem exploration: What happened, what was the person trying to do, and what got in the way?
- Solution evaluation: Does a proposed product help, and will people adopt or pay for it? That is a later question to test separately.
- Evidence: Specific actions, workarounds, consequences, repeated effort, and attempts to find or pay for alternatives.
Concrete episodes can show that a problem deserves more investigation. They do not automatically establish a viable business, and a handful of interviews cannot stand in for a representative survey.
Prepare before you recruit
Define the segment and the uncertainty
Write down which customer group you want to understand and the problem you think some members experience. Make the hypothesis narrow enough to investigate. For example: “Independent shop owners lose time reconciling online orders with inventory” is more testable than “small businesses need better software.” Treat that statement as an open question, not as a claim to persuade the participant to accept.
Decide in advance what evidence would make you strengthen, revise, or drop the hypothesis. That might include a recent example, a repeated workaround, a measurable consequence, or an effort to find an alternative. Also note what would count against the hypothesis, such as the problem being rare, inconsequential, or already handled easily.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Recruit people who encounter the situation
Invite people who have firsthand experience with the relevant task or circumstance, rather than only people who are likely to like your idea. In organizations, the person doing the work may not be the buyer: consider talking to users, decision-makers, influencers, or buyers as appropriate, and keep their different perspectives distinct.
Rank #2
Set expectations in the invitation. If someone might assume the meeting is a sales call, say plainly that you want to learn about their work or experience and are not pitching a product. Steve Blank discusses this setup for corporate customer discovery in Solving the Innovator’s Dilemma – Customer Development in a Big Company.
Prepare a flexible guide, not a script
Choose a few topics and open prompts, then practice the conversation once. Blank’s slides and videos resource includes preparation, interview dry runs, interview flow, and pattern-finding. Start from what customers care about, and do not open with a demo or value proposition. Strategyzer’s guidance on capturing customer jobs, pains, and gains also cautions against substituting subjective opinions for observed behavior: How To Capture Customer Jobs, Pains, & Gains That Aren’t Subjective.
Run the conversation around a real episode
Open with context and permission
Briefly explain that you are trying to understand the person’s current process, not sell them something. Ask permission to take notes, then invite them to describe the relevant situation in their own words. In organizational interviews, learn about the problem before disclosing your product hypothesis; introducing a concept too early can steer the conversation toward reactions to your idea rather than the underlying experience.
Ask about the last time it happened
A recent episode gives both of you something concrete to examine. A useful opener is: “Tell me about the last time you ran into [situation]. What happened?” Strategyzer recommends asking when the person last struggled with a particular challenge and then probing for evidence, rather than asking for a general opinion: The One Biggest Error in Customer Interviews: Mistaking Opinions For Facts.
Follow the participant’s account instead of mechanically reading every prompt. These questions can help you understand what happened without implying a preferred answer:
- “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?”
Probe for consequences and measures
When a participant says something is “slow,” “expensive,” or “annoying,” ask what that means in practice. How long does the task take? What does it delay? How much money or effort was involved? What was the result? If the person tried a workaround, ask what they used and how they judged whether it succeeded.
Ask about frequency and context, but do not turn a vague recollection into a precise statistic. If the person cannot remember or quantify something, record that uncertainty rather than filling in the gap yourself. Strategyzer’s interview guidance emphasizes asking how the interviewee measures success or failure and seeking concrete evidence for claims about improvement.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Avoid questions that manufacture encouragement
Questions about a hypothetical product can produce pleasant, confident answers without showing that the problem is important enough to change behavior. Early in discovery, avoid prompts such as:
- “Do you like this idea?”
- “Would you buy this?”
- “Would you use a tool that…?”
- “Which solution do you prefer?”
These ask for opinion or prediction, not a record of what the person did. If you reveal a concept before establishing the problem, a negative reaction could mean either that the solution is weak or that the problem itself is not important. Keep those questions for a later solution or demand test. Strategyzer explains the distinction between establishing a problem and evaluating a proposed solution in “Problem” vs Solution In Customer Interviews.
Listen without rewarding answers that confirm your hypothesis. Follow up neutrally: “What makes you say that?”, “Can you walk me through what happened?”, or “What did you do after that?” A workaround, repeated effort, or purchase is a reason to investigate further—not proof by itself that a new product will succeed.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Turn separate conversations into a decision
Record observations separately from interpretation
After each interview, capture enough context to understand the example later. Distinguish what the participant did or said from what you think it means. A practical note structure is:
- Participant context: role, relevant responsibilities, and connection to the situation.
- Episode: when and where it occurred, and what the person was trying to accomplish.
- Behavior: what they did, including steps, workarounds, and other people involved.
- Consequences: difficulty, delay, cost, risk, or other effects they described.
- Frequency and evidence: recurrence if known, actual spending or search for alternatives, and how success was judged.
- Open questions: details you could not establish and interpretations to test in later conversations.
Look for patterns and contradictions
Compare interviews against the same problem hypothesis. Look for recurring contexts, behaviors, consequences, and workarounds, while also recording cases that do not fit. Notes are useful when they help you see which parts of the hypothesis are supported, which differ by customer or situation, and which remain unclear. Strategyzer’s 2026 event page describes the challenge teams face when trying to turn differently structured interview notes into patterns and decisions: Run customer interviews that produce insights, not notes.
Use what you learn to choose a next step: continue exploring the same problem, narrow or change the customer segment, revise the hypothesis, or move on to a separate test of a solution or demand. Do not treat any fixed interview count as a universal threshold; the sources cited here do not establish a statistically validated number of interviews that proves a problem exists.
What interviews cannot establish on their own
Interviews reveal what particular people remember and describe in a conversation. They are useful for discovering context and generating or challenging hypotheses, but they do not show how prevalent a problem is across a market. Nor do accounts of past behavior prove that people will adopt, use, or pay for your proposed solution. Keep conclusions tied to the participants and evidence you actually have, then use later methods suited to questions about market scale, solution fit, and demand.
Further reading
For more background on 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.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsQuick 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.
