The most common user interview mistake is asking users what they want. Users are not product designers. They cannot tell you what to build. They can tell you what problems they face, what workarounds they use, and what outcomes they care about. Your job is to extract those insights and translate them into product decisions.
The Interview Structure
First 5 minutes: Context. "Walk me through a typical day when you deal with [problem area]." Get them talking about their real workflow, not your product. You are mapping their world before you zoom into specifics.
Middle 20 minutes: Pain and behavior. Follow the threads they reveal. When they mention a problem, go deeper: "What happens when that goes wrong?" "How do you handle that today?" "What have you tried?" Never suggest solutions. Just listen and probe.
Last 5 minutes: Priorities. "If you could fix one thing about [problem area], what would it be?" This forces ranking. Everything is a problem. What is the biggest problem?
The Five Rules
Rule 1: Ask about past behavior, not future intentions. "Tell me about the last time you had to prioritize features" beats "Would you use a tool that prioritizes features?" Past behavior is real. Future intentions are fiction.
Rule 2: Shut up. After asking a question, wait. Silence is uncomfortable but productive. Users fill silence with the details you need. If you are talking more than 20% of the time, you are interviewing wrong.
Rule 3: No leading questions. "Do you find prioritization difficult?" leads the witness. "How do you currently prioritize your backlog?" is neutral. Let users define their own problems.
Rule 4: Follow the emotion. When a user sighs, laughs, or gets frustrated while describing a workflow, probe there. Emotional reactions flag real pain points, not theoretical ones.
Rule 5: Document immediately. Write up your notes within 2 hours. Memory decays fast. Record calls (with permission) and use timestamps, not full transcripts.
Sample Size
Run 12-15 interviews per customer segment per research question. You will hear new patterns through interview 6-8 and reach saturation by 12-15. After saturation, additional interviews add cost without new insights.
Use the user persona builder to synthesize interview findings into actionable personas. The assumption mapper helps identify which interview insights should change your product assumptions.
From Interviews to Decisions
Interviews generate qualitative signal. To make it actionable:
- Cluster findings into themes. Group similar pain points across interviews.
- Quantify where possible. "8 out of 12 users mentioned X" is more persuasive than "users mentioned X."
- Feed themes into prioritization. Use the RICE Calculator with interview insights informing the impact and confidence scores.
- Build an opportunity solution tree mapping discovered opportunities to potential solutions.
The prioritization guide covers how to combine qualitative research with quantitative scoring.