Customer discovery interview questions
Discovery questions designed to validate a problem, not sell a solution — so you learn whether the pain is real, frequent, and worth paying to fix before you write a line of code.
Founders and early product teams validating a new idea — they spend their days talking to potential users, sketching solutions, and trying to avoid the classic trap of building something nobody wants.
- What they're trying to learn
- confirm a problem is painful and common enough to build a business around — before committing engineering time.
- Who they interview
- people who have the problem you think you can solve
Use this at the earliest stage — you have a hypothesis about a problem and want to test it against reality. Run it before you build, and again whenever you enter a new market or segment.
Customer interview questions to copy & run
The problem, in their words
- 1.Tell me about how you handle [problem area] today.
- 2.Walk me through the last time you dealt with this. What did you do?
- 3.What's the hardest part about that for you?
- 4.Why is that hard?
Frequency & severity
- 1.How often does this happen?
- 2.When it happens, how big a deal is it — nice-to-fix or hair-on-fire?
- 3.What happens if you just… don't deal with it?
- 4.Who else is affected when it goes wrong?
Existing solutions
- 1.What have you tried to make this better?
- 2.How well does that work? Where does it fall short?
- 3.How much time or money do you spend on this today?
- 4.If nothing else existed, how would you cope?
Willingness to change
- 1.How are you solving this right now, honestly?
- 2.What would a better solution need to do for you to switch?
- 3.Have you ever looked for a tool to fix this? What did you search for?
Tips for better answers.
- Test the problem, not your idea. If you describe your solution, you've contaminated the interview.
- Look for evidence people already spend time or money on this — the strongest signal that a problem is real.
- Beware enthusiastic agreement. 'That sounds useful' is not the same as 'I've been trying to fix this for months'.
- Ask 'why' until you hit an emotion or a real constraint — that's the root of the problem.
Questions about this template.
What is customer discovery?
Customer discovery is the practice of interviewing potential customers to validate that a problem is real and worth solving before building a product. It's the first step of the lean startup and customer development methodologies, focused on learning rather than selling.
What questions should I avoid in discovery interviews?
Avoid hypothetical and leading questions like 'Would you use a tool that…?' or 'Don't you hate it when…?' — people are bad at predicting future behavior and tend to agree to be polite. Ask about past behavior instead.
How do I know if I've validated the problem?
You've validated a problem when multiple people describe it unprompted, it happens frequently, it causes real cost, and they already spend time or money trying to solve it. If people shrug it off, it's probably not worth building for.
Don't just ask the questions — synthesize the answers.
Save these questions as a template in Intervool, capture the interview, and let AI turn every conversation into insights, personas, and a prioritized roadmap. Free for 30 days.