How to conduct user interviews that uncover genuine needs instead of polite opinions. Includes question frameworks, common mistakes, and practical tips for better research.
The most expensive mistake in product development is building something nobody wants. Customer interviews are the cheapest way to avoid that mistake. But most interviews fail to reveal real needs because the interviewer asks leading questions, accepts surface-level answers, or turns the conversation into a pitch for their existing solution. This guide covers how to run interviews that actually teach you something.
Interviews work best during the Empathize stage when you are trying to understand the problem space. They are also valuable during the Test stage when you are evaluating prototypes. They are less useful for validating ideas you have already committed to building (that is what usability testing and analytics are for) or for measuring satisfaction across large populations (that is what surveys are for).
If you need breadth (understanding patterns across many users), use surveys. If you need depth (understanding why one person does what they do), interview. Most design projects need both, but at different stages.
Interviewing the wrong people is worse than not interviewing at all because it gives you false confidence. You need people who match your target user profile, not just people who are easy to reach.
Five to eight interviews per persona segment is usually enough to identify major patterns. After about the sixth interview, you will notice the same themes repeating. That is when you know you have sufficient coverage.
An interview guide is not a script. It is a list of topics you want to cover, with example questions under each topic. You should know the guide well enough that you rarely look at it during the conversation. The conversation should feel natural, not like a questionnaire.
Structure your guide in three phases:
Start with questions about the person's world, not about your product. "Tell me about your role. What does a typical week look like?" This builds rapport and gives you context for interpreting everything that follows.
Focus on the specific problem area. Use storytelling prompts: "Walk me through the last time you tried to [do the thing your product addresses]. Start from the very beginning." Then follow up on whatever is most interesting or surprising.
Ask them to step back and reflect. "If you could wave a magic wand and change one thing about how you [do this task], what would it be?" Then: "Is there anything I should have asked but did not?"
Good interview questions share three properties: they are open-ended, they are about the past (not the hypothetical future), and they invite stories rather than opinions.
Most interviewers talk too much. The ideal ratio is 20% you, 80% them. Here are techniques to stay in listening mode:
A fundamental rule of user research: never trust what people say they will do. Trust what they have done. People are not lying. They are bad at predicting their own behavior. They overestimate how much they will use a new feature, underestimate how attached they are to their current workflow, and forget about the workarounds they have built.
This is why empathy maps separate "says" from "does." The discrepancy between these two quadrants is where the real insights live.
When possible, combine interviews with observation. Ask them to show you how they do the task while they talk about it. You will see steps they forgot to mention, tools they did not think to bring up, and frustrations they have normalized.
After your interviews, you need to turn hours of conversation into actionable insights. Here is a practical process:
Remote interviews work well with a few adjustments. Turn your camera on and ask them to do the same (facial expressions carry important emotional information). Use screen sharing when possible so they can show you their workflow. Record the session (with permission) so you can review moments you might have missed. And give the conversation an extra five minutes at the start for the awkward video-call settling-in period that does not happen in person.
Related guides: persona creation · journey mapping · jobs to be done
Design Thinker Labs Home · All Guides · How It Works · Pricing