Customer discovery
Customer Interview Questions for Product Discovery (with a Practical Script)
The strongest customer interview questions ask about a recent real situation, the workaround a person used, what it cost, and what happened next. They delay the pitch, avoid hypothetical promises, and produce evidence you can compare across conversations.
Prepare the interview around a decision
Before writing questions, name the decision the interview should inform. Are you checking whether a problem is frequent, understanding the current workflow, choosing between segments, or testing whether a solution fits? A bounded learning goal produces better conversations than a generic request for feedback.
Recruit people who recently experienced the situation, not only people who match a broad persona. Record the context you need to compare answers later: role, segment, trigger, current alternative, and recency.
- What assumption would most change the product decision?
- Which recent behavior would provide evidence for or against it?
- What must remain private or outside the research record?
- What will you do if the evidence is mixed?
A neutral customer interview question set
Use these as prompts, not a rigid questionnaire. Stay with the last concrete example long enough to understand what actually happened. Ask for the person's words before translating them into product language.
- 01
Context
Tell me about the last time you had to [job]. What triggered it, and who else was involved?
- 02
Workflow
Walk me through what you did from the first signal to the final outcome.
- 03
Friction
Where did the process slow down, break, or require a workaround?
- 04
Cost
What did that problem cost in time, money, risk, or a missed outcome?
- 05
Alternatives
What have you tried, and why did you keep or stop using each option?
- 06
Change
What have you already done to improve the situation, and what would make you act differently?
Use follow-ups to get past opinions
When someone says a feature would be useful, ask what happened the last time they needed it. When they say they would pay, ask how they handle the problem today, who owns the budget, and what process a purchase would replace. Past behavior is usually more informative than a hypothetical yes.
- What makes you say that?
- Can you give me a recent example?
- What did you do next?
- How often does this happen?
- What happens if you do nothing?
- Who notices or pays for the problem?
- What would you use instead?
Analyze interviews by situation and evidence
Separate the person's words from your interpretation. Capture the situation, observed behavior, workaround, consequence, desired outcome, and confidence. Keep contradictory evidence visible; a neat theme that erases exceptions is not a reliable insight.
Compare patterns across people who share the same situation rather than counting every mention as an equal vote. A severe problem for a small but reachable segment may matter more than a mild request from a large but inactive audience.
- Direct quote or close paraphrase.
- What actually happened and when.
- Existing alternative or workaround.
- Cost, urgency, and decision-maker.
- Evidence for, evidence against, and what remains unknown.
Where Specky fits
Keep the evidence attached to the work.
Specky connects customer signals, research, decisions, specs, tickets, and outcomes in one Product Graph. It drafts and connects the work; your team reviews and decides.
Questions people ask about this topic
How many customer interviews should I run?+
Run enough interviews within the same situation to see whether the workflow, problem, and language repeat, then test the riskiest assumption with observable behavior. There is no universal quota.
What should I ask in a customer discovery interview?+
Ask about a recent real event: what triggered it, what the person did, where it broke, what workaround they used, what it cost, and what happened next.
Should I show my prototype during the interview?+
Only after you understand the current problem and workflow, and only when prototype feedback is the learning goal. Ask what the person would do, not merely whether they like it.
How do I turn interview notes into product decisions?+
Keep quotes and situations attached to themes, distinguish evidence from interpretation, compare patterns across the target segment, and record the decision, confidence, unknowns, and next test.