What Not to Ask During Customer Discovery Interviews
Most guidance about customer discovery interviews focuses on what to ask. Just as important — and often overlooked — is what not to ask. Certain question patterns quietly undermine an interview before it produces anything useful, no matter how well-intentioned the rest of the conversation is. Here’s what to avoid, and why each one causes trouble.
Avoid Hypothetical Questions
“Would you use an app that does X?”
This is the single most common mistake in discovery interviews. Hypothetical questions ask someone to predict their own future behavior, and people are notoriously unreliable at this, especially for a product they haven’t experienced. Answering costs nothing, so most people default to a polite, encouraging yes — which tells you almost nothing about what they’d actually do. See how to validate demand without asking “would you use this?” for the alternative approach.
Avoid Leading Questions
“Don’t you think a tool that automates this would be helpful?”
Leading questions suggest the answer before the person has a chance to form their own. Once you’ve named your idea or opinion, most people will agree with it out of politeness or social pressure, regardless of their actual view. Keep questions neutral and let the person’s own words come first.
Avoid Questions About Willingness to Pay in the Abstract
“Would you pay $50 a month for this?”
Abstract pricing questions rarely predict real purchasing behavior, because there’s no actual cost to saying yes. A far more useful approach is to understand what someone currently spends — in money or time — on the problem today, which gives you a grounded reference point instead of a guess.
Avoid Yes/No Questions When You Want Detail
“Is this a problem for you?”
Yes/no questions are easy to answer without elaboration, and a quick “yes” or “no” tells you little about severity, frequency, or context. Replace them with open prompts: “Tell me about the last time this came up” invites detail a closed question can’t.
Avoid Mentioning Your Solution Too Early
“I’m building an app that would let you do X — what do you think?”
Once your idea enters the conversation, every subsequent answer becomes a reaction to your idea rather than an honest account of the person’s own experience. Hold off on describing your solution until you’ve thoroughly understood their current situation.
A Quick Reference
| Avoid | Why | Better Alternative |
|---|---|---|
| “Would you use this?” | Hypothetical, costs nothing to agree | “Tell me about the last time you dealt with this.” |
| “Don’t you think this would help?” | Leading, suggests the answer | “What’s your experience been with this?” |
| “Would you pay $X for this?” | Abstract, ungrounded in real spending | “What are you currently spending on this problem?” |
| “Is this a problem for you?” | Closed, produces low-detail answers | “How often does this come up for you?” |
| Mentioning your idea early | Contaminates the rest of the conversation | Save it for the end, if at all |
Why This Matters More Than It Seems
A single leading or hypothetical question doesn’t necessarily ruin an interview, but a pattern of them compounds quickly. Interviews conducted this way tend to produce a consistent stream of polite, encouraging feedback — which is exactly the kind of misleading signal discussed in interest is not demand. The founder walks away feeling validated, while the underlying evidence is much weaker than it appears.
Correcting Course Mid-Interview
If you catch yourself asking a leading or hypothetical question, it’s easy to recover — simply follow up with a neutral, open-ended question: “Setting that aside, what’s actually been your experience?” Most people won’t notice the correction, and it gets the conversation back onto solid ground.
Better Questions Lead to Better Decisions
Avoiding these patterns isn’t just about interview technique — it directly affects the quality of the decisions you make afterward. An interview free of leading and hypothetical questions gives you a much more honest read on whether a real problem exists, which is the entire point of doing discovery before development.
Want Better Customer Discovery Interviews?
MVPHUB helps founders design interview guides that avoid common bias traps and reveal real problems. Book a free consultation with MVPHUB to review your interview approach.
Book a free consultation with MVPHUBFrequently Asked Questions
Why are hypothetical questions bad in customer discovery interviews?
Hypothetical questions ask people to predict their own future behavior, which they're generally bad at, especially about a product they haven't actually used. They also cost nothing to answer positively, which inflates the apparent signal.
What's a leading question, and how do I avoid asking one?
A leading question suggests the answer you want to hear, often by mentioning your idea or a specific opinion before the person has shared their own. Avoid it by describing neutral situations and letting the person supply their own reaction first.
Is it ever okay to ask about my product idea directly?
Yes, but only after the person has described their current situation in detail, and treat their reaction to your idea as weaker evidence than what they said about their own experience.
Why shouldn't I ask yes/no questions in discovery interviews?
Yes/no questions tend to produce short, low-information answers and make it easy for people to just agree without elaborating. Open-ended questions that ask someone to describe or explain tend to reveal much more.
What if I accidentally ask a leading question mid-interview?
Follow up with a neutral, open-ended question to get back on track — for example, "and separate from that, what's your actual experience been?" It's a common mistake and easy to correct in the moment.
