Customer discovery follow-up questions for vague answers
A useful follow-up turns a broad opinion into a specific event, action or consequence. Start with the customer's own words, ask about one missing detail and leave room for the answer to be that there is no important problem.
These examples are invented to illustrate the questions. They are not customer results.
When someone says “it's annoying, but we manage”
Ask: “Can you walk me through the last time it happened?”
“Annoying” might mean a daily interruption, a small inconvenience or something that has never happened to this person. A recent example helps you distinguish those possibilities. Ask what happened next before proposing a solution.
| What you hear next | A useful question | What it helps establish |
|---|---|---|
| “I spent Friday reconciling two spreadsheets.” | “Did this affect anything else you planned?” | A current trade-off, if there was one |
| “It took a few minutes. It wasn't a big deal.” | “What makes the current approach good enough?” | Evidence against treating this as urgent |
| “It could become a problem when we grow.” | “Has it caused a problem at your current size?” | Experienced difficulty versus a future possibility |
| “I haven't dealt with it myself.” | “Who handles it, and what have you seen them do?” | Direct experience versus second-hand interpretation |
Do not turn “we might need a tool later” into evidence that someone needs to buy now. A proposed solution and a meaningful consequence are different things.
When someone says “we need a better tool”
Ask: “What have you tried to change so far?”
If they have tried something, explore the action: who took it, what they used, what happened and why the attempt stopped. If they have done nothing, ask whether changing it matters, and why. Lack of action is useful information, not an objection to overcome.
An invented exchange:
Customer: “We need a better way to track requests.”
Founder: “What have you tried to change so far?”
Customer: “We set up a shared inbox, but only two people use it.”
Founder: “What happens when the other people get a request?”
The last question follows the workflow gap the customer actually described. It does not assume another tracking product will solve it.
When someone says “I'd definitely use that”
Ask: “How are you handling this today?”
An encouraging reaction can be sincere without predicting future use. Look for the existing situation and the cost of leaving it unchanged. If the conversation is explicitly about evaluating your product, you can ask what would need to be true for a trial to be worthwhile. Keep an offered trial separate from an agreed trial.
When someone names a different priority
Ask: “What makes that the priority right now?”
Follow a more valuable subject when it fits the purpose of the conversation. Keep a note of the unfinished question so you can return to it deliberately. Do not force every conversation through a fixed checklist, or assume the change of subject answered the previous question.
A three-line note you can use during a call
- Established: What did they actually say happened?
- Uncertain: What am I inferring about its cause or importance?
- Next question: What single answer would change my understanding?
For example: “They use a shared inbox. I don't know why most people avoid it. Ask what happened to the last request received outside it.”
How many follow-ups should I ask?
There is no useful fixed number. Continue while a missing answer matters to your learning objective and the person is willing to explore it. Stop or change direction when the answer is clear, the topic is not important, the participant sets a boundary or something more relevant emerges.
Can a tool suggest these during the call?
Truffle is an invite-only Mac beta that suggests follow-up questions during customer conversations. It requires an Apple Silicon Mac running macOS 14.2 or later; the initial supported setup is Google Meet in Chrome. Coaching requires a separate invitation. A suggestion is something to consider at a natural gap, not an instruction to interrupt. You still choose whether it fits. See the illustrative call on the homepage, or read the beta setup requirements.
Further reading
The Mom Test by Rob Fitzpatrick addresses learning from customer conversations and avoiding biased feedback. Huthwaite's SPIN methodology distinguishes questions about situations, problems, implications and value. The examples and three-line note above are Truffle's practical suggestions, not a reproduction of either framework.