Ask Better Follow-Up Questions in Customer Interviews
Use concrete sequences and recent examples to understand behavior without steering the participant toward your idea.

The first answer in a customer interview is often a summary: “It takes too long,” “we need automation,” or “the team does not use it.” The useful detail usually appears in the follow-up.
A good follow-up helps the participant reconstruct an actual event. It should not tell them which explanation you hope to hear.
Move from opinion to an example
Ask about the last time the situation occurred. What started it? Who was involved? What happened next? This gives the conversation a sequence instead of a collection of general beliefs.
If the participant cannot recall an example, keep that uncertainty. Do not supply a hypothetical scenario and later report their agreement as evidence of existing behavior.
Follow the workaround
When someone says they use a spreadsheet, ask what goes into it, who updates it, and what happens after it is shared. The workaround can reveal the real coordination problem.
For example, “we need reminders” might conceal unclear ownership rather than forgotten dates. You need to understand the sequence before deciding which product mechanism would help.
Ask about consequences
“What happened because of that?” can reveal whether the problem causes delay, rework, frustration, or little practical harm. Avoid inserting a consequence into the question, such as “Did that cause expensive mistakes?”
Let the participant describe significance in their own terms. You can assess business implications later with the rest of the evidence.
Explore exceptions
Ask when the process works well and what is different on those occasions. Exceptions can reveal a missing condition, a useful local practice, or a segment where the problem is less relevant.
Do not treat an exception as a reason to dismiss the original difficulty. It is a chance to understand its boundaries.
Keep interpretation separate
During synthesis, distinguish the participant’s account, your observation, and your explanation. A quote does not automatically establish frequency across a market. A memorable story can be important without being representative.
Retain only the personal information needed for the research purpose and follow the agreed consent and storage arrangements.
The point of follow-up questions is not to extract a stronger endorsement of your feature. It is to understand the person’s work well enough that the team can make a more informed decision about whether and how to help.
Keep reading

Turn a Feature Request into a Problem You Can Evaluate
Keep the requested solution, then uncover the trigger, workaround, and consequence behind it.

Cut Feature Scope Without Cutting the Useful Outcome
Protect the core user action, then remove optional paths and polish with explicit consequences.

Keep a Product Decision Log That Explains the Tradeoff
Record the choice, alternatives, evidence, and revisit condition without turning every discussion into a formal ceremony.

What did you take away?
Thoughts, pushback, or a story of your own? Drop a reply below — I read every one.
Comments are powered by Disqus. By posting you agree to theirterms.