The problem with customer interviews is that people are trying to help you. They fill silences, they agree with premises, and they answer hypothetical questions with hypothetical honesty. The interview feels productive and the evidence is worthless. The fix is not asking more questions. It is asking about the past instead of the future.
Why most customer discovery produces nothing usable
Three habits ruin it, and all three feel like good interviewing at the time.
- Asking about the future. “Would you use this?” measures politeness, not demand. Nobody knows what they will do next quarter.
- Leading with your idea. Once you describe the solution, the conversation becomes feedback on your solution rather than evidence about their problem.
- Accepting the first answer. The first answer is the rehearsed one. The useful answer is usually two follow-ups deeper.
What to ask instead
Ask what happened, not what would happen
“Tell me about the last time this came up” produces a story with dates, people and consequences. “Would you find this useful” produces a yes.
Ask what it cost them
Time, money, a missed deadline, an internal argument. If the problem never cost anything specific, it is an irritation, not a budget line. Irritations do not get funded.
Ask what they tried
Every real problem has a graveyard of attempted fixes: a tool they bought, a contractor they hired, a spreadsheet someone still maintains. That graveyard is your actual competition.
Ask who else was involved
This surfaces the buying committee before you meet it. The person feeling the pain is often not the person approving the spend.
Ask for the words, then use them
Write down the phrasing they use, verbatim. That language belongs in your positioning and messaging. Founders who invent their own vocabulary end up marketing to themselves.
How to run the conversation
- Do not pitch until the end, if at all. The moment you describe your solution, you stop collecting evidence and start collecting reactions.
- Let silences sit. The three seconds after someone finishes is where the honest sentence arrives.
- Follow every vague word. “Difficult”, “messy”, “a nightmare” — ask what specifically happened that made it feel that way.
- Take verbatim notes, not summaries. Your paraphrase is already your interpretation. The exact words are the asset.
- Twelve to fifteen conversations. Patterns start repeating around eight; by fifteen you are mostly confirming.
How to know the interview was any good
A useful interview leaves you with at least one of these:
- A story with specifics — dates, amounts, names of tools
- Evidence someone already spent money trying to solve it
- A phrase you had not thought of, in their words
- A surprise — something that contradicts what you assumed
If none of those appeared, you had a pleasant conversation. That is not the same as research.
Where the interviews go next
Discovery is not a standalone exercise. The output feeds directly into positioning: the language becomes messaging, the workarounds become competitive framing, the triggers become the launch narrative.
This is why research sits first in the Authority Engine™ and not in parallel with content. Content built on assumed language is expensive to unwind, because by then it is on the website, in the deck, and in every post the founder has published.
Related: what product validation actually proves, and what founder positioning is.
Written by Neha Vyas, founder of You Creatives, a Stockholm-based brand strategy, positioning and go-to-market consultancy. Ten years in strategic consumer and market research, a BSc in Computer Science Engineering and an MBA in Marketing.
