User Interviews: How to Ask Questions That Get Real Answers

User interviews are one of the most powerful research methods in product design. A single conversation can reveal workflows you didn't know existed, problems your analytics can't see, and the real reasons people choose — or abandon — a product.

But interviews are also easy to do badly. Leading questions, hypothetical scenarios, and too much talking from the interviewer produce answers that sound useful and turn out to be misleading. This guide covers how to plan and run interviews that get real answers.

When to use interviews#

Interviews are best for understanding:

• People's goals, motivations, and context.
• How they currently solve a problem, including workarounds.
• Pain points and frustrations in existing processes.
• The language they use to describe their needs.

They're less suited to:

• Measuring how many people share a behavior — use surveys or analytics.
• Evaluating whether a design is usable — use usability testing.
• Predicting future behavior — people are poor predictors of what they'll do.

Step 1: Set clear research goals#

Start with what you need to learn. Good research goals are specific and tied to decisions:

• "Understand how small clinic managers schedule staff each week."
• "Learn why trial users don't connect their bank accounts."

Write down your assumptions too. Interviews are a chance to test them.

Step 2: Recruit the right people#

Talk to people who represent your target users. Define the characteristics that matter — role, experience, behaviors — and screen for them. Include a mix: new and experienced users, satisfied and dissatisfied customers, and people who chose a competitor.

Five to eight interviews per user group often reveal clear patterns. Stop when new interviews mostly repeat what you've already heard.

Step 3: Write an interview guide#

An interview guide is a flexible plan, not a script to read word for word. A typical structure:

1. Introduction — explain the purpose, how long it will take, and how notes will be used.
2. Warm-up — easy questions about their role and background.
3. Core topics — open questions about their experiences related to your goals.
4. Specific probes — deeper questions on important areas.
5. Wrap-up — anything they'd like to add, and thanks.

Prepare more questions than you need and let the conversation guide which ones you use.

Ask about past behavior, not hypotheticals#

The most important rule: ask about what people have actually done, not what they would do.

• Weak: "Would you use a feature that automatically categorizes expenses?"
• Strong: "Tell me about the last time you sorted your expenses. What did you do?"

People are generous and optimistic when predicting their future behavior. Almost everyone says they'd use a helpful-sounding feature. Past behavior, described in specific detail, is far more reliable.

Use open-ended questions#

Open questions invite stories and detail:

• "Walk me through how you…"
• "Tell me about a time when…"
• "What happened next?"
• "How did you decide…?"
• "What was the hardest part of…?"

Closed questions — answered with yes or no — have their place for clarifying facts, but they don't reveal much on their own.

Avoid leading questions#

Leading questions suggest the answer you're looking for:

• Leading: "Don't you find the current process frustrating?"

• Neutral: "How do you feel about the current process?"

• Leading: "How much would this feature save you time?"

• Neutral: "What, if anything, slows you down in this task?"

Also avoid mentioning your solution early. Once people know what you're building, they tend to tell you what they think you want to hear.

Probe deeper#

The first answer is rarely the full story. Follow-up questions uncover the real insight:

• "Can you tell me more about that?"
• "Why was that important?"
• "What did you do then?"
• "Can you show me?"
• "You mentioned it was annoying — what made it annoying?"

A useful technique is to ask "why" several times in different forms until you reach an underlying motivation, but keep it conversational rather than interrogative.

Listen more than you talk#

The interviewer should talk far less than the participant. Resist the urge to:

• Fill silences — pauses often lead to the most honest reflections.
• Explain or defend the product.
• Correct the participant's understanding.
• Agree enthusiastically, which can bias later answers.

Your job is to understand their world, not to share yours.

Pay attention to what people do, not just say#

When possible, ask participants to show you their process: share their screen, open the spreadsheet they use, walk through the tool. Observing behavior often reveals workarounds and frustrations people don't think to mention because they've become routine.

Take good notes#

Record interviews with permission so you can focus on the conversation. Have a colleague take notes, or take brief notes yourself, capturing:

• Key quotes in the participant's own words.
• Specific behaviors and workarounds.
• Emotional moments — frustration, delight, confusion.
• Surprises that challenge assumptions.

Write a short summary immediately after each interview while it's fresh.

Synthesize across interviews#

Individual interviews are anecdotes; patterns are insights. After the interviews:

1. Collect observations from all sessions, one per note.
2. Cluster related observations into themes, often using affinity mapping.
3. Name each theme with a clear insight statement.
4. Support insights with evidence: quotes and examples from multiple participants.
5. Connect insights to decisions: what does this mean for the product?

A strong insight explains a behavior and its cause. "Clinic managers build schedules in spreadsheets because the existing tool can't handle last-minute shift swaps" is far more useful than "users don't like the scheduling tool."

Share findings effectively#

Keep outputs actionable:

• Lead with the most important insights.
• Include direct quotes and short clips.
• Highlight implications and open questions.
• Invite the team to observe future interviews themselves.

Common mistakes#

• Asking about hypothetical future behavior.
• Pitching the solution during the interview.
• Asking leading or double-barreled questions.
• Talking too much.
• Interviewing only happy customers.
• Treating one person's opinion as a pattern.

Curiosity is the skill#

Great interviewers are genuinely curious. They ask about real experiences, listen carefully, follow interesting threads, and stay neutral. The result is an understanding of users that no dashboard can provide.

Ask better questions, listen more than you talk, and look for patterns across conversations. That's how interviews turn into insights that shape better products.