Design thinking
Empathy Interviews in Practice - Beyond the Checklist
How to run interviews that surface real pain points instead of polite confirmations - a field guide for product teams and MBA classrooms.

Empathy interviews are one of the most taught - and most poorly executed - tools in design thinking. Teams often treat them as lightweight user research when they should be structured listening sessions.
Start with a learning goal, not a hypothesis to prove
Before the first question, write down what you need to learn. Not what you hope users will say. A learning goal keeps the conversation open and reduces leading questions.
Questions that open doors
Replace "Would you use this feature?" with:
- Walk me through the last time this problem showed up.
- What did you try before that did not work?
- What would have to be true for this to feel easy?
These prompts surface context, workarounds, and emotional weight - the raw material for problem statements.
Listen for pain, not praise
Polite users will tell you what you want to hear. Listen for repetition, frustration, and workarounds. Those signals usually point to pain points worth defining.
Close the loop in Define
Interview notes are not the deliverable. Synthesized pain points, journey maps, and a crisp problem statement are. Empathy without synthesis is just conversation.
In college workshops, I ask students to conduct three interviews and then defend one problem statement in front of peers. The quality of their Define phase improves immediately - because they finally have evidence, not assumptions.
Share this article
https://www.design-thinking.in/insights/empathy-interviews-in-practice
