The Definitive Guide to User Interviews

User interviews are the backbone of qualitative research. They give you direct access to the thoughts, motivations, and frustrations of the people you're building for — something no survey or analytics dashboard can replicate.

But there's a catch: poorly conducted interviews produce misleading data that can send your team in the wrong direction. This guide will teach you how to run interviews that surface genuine insights, not just confirmation of what you already believe.

What Is a User Interview?

A user interview is a one-on-one conversation between a researcher and a participant, designed to explore the participant's experiences, behaviors, needs, and motivations related to a specific topic. Unlike surveys, interviews allow you to follow up on unexpected responses, probe deeper into reasoning, and observe the emotional weight behind answers.

According to the Nielsen Norman Group, user interviews are one of the most frequently used UX research methods, employed by over 80% of UX professionals. Their power lies in their flexibility — you can adapt your questions in real time based on what you're hearing.

When Should You Use Interviews?

Interviews are ideal when you need to:

• Explore a problem space you don't yet understand well
• Understand motivations behind behaviors you've observed in analytics
• Validate or challenge assumptions before investing in a solution
• Gather rich context around user workflows and pain points
• Uncover needs users can't articulate through indirect questioning

They're less useful when you need statistically significant data, when you're testing usability of a specific interface (use usability testing instead), or when you need to measure preferences across a large population (use surveys).

Types of User Interviews

Not all interviews serve the same purpose. Here's how the main types compare:

For most product research, semi-structured interviews hit the sweet spot. You get the consistency of a prepared guide with the freedom to explore unexpected threads. Learn more about different approaches in our choosing a methodology guide.

Planning Your Interviews

Step 1: Define Your Research Questions

Before writing a single interview question, clarify what you're trying to learn at the project level. Research questions are not the same as interview questions — they're the strategic questions your study aims to answer.

Good research questions are specific enough to be answerable but broad enough to leave room for surprise:

• "How do product managers currently prioritize feature requests, and what frustrations do they experience in that process?"
• "What triggers someone to switch from a free tool to a paid solution for project management?"

Step 2: Identify Your Participants

The quality of your insights depends entirely on talking to the right people. You need participants who have relevant, recent experience with the topic you're studying.

According to research published by Nielsen Norman Group, 5 participants will uncover approximately 85% of usability problems in usability testing. For interview-based research exploring attitudes and behaviors, the numbers are different — most researchers find that 8 to 12 interviews are needed to reach thematic saturation for a reasonably homogeneous group.

For more on recruitment, see our guide on finding research participants, and for guidance on sample size, read how many interviews are enough.

Step 3: Write Your Interview Guide

Your interview guide is a structured document that outlines the topics and questions you want to cover. It's a guide, not a script — you should feel comfortable departing from it when a participant says something interesting.

A strong guide includes:

• Warm-up questions (2–3 minutes): Build rapport, confirm background
• Core questions (20–40 minutes): Your main research topics, roughly 8–12 open-ended questions
• Wrap-up (5 minutes): Catch-all questions, thank the participant

For detailed guidance on crafting questions, read how to write great interview questions.

Step 4: Set Up Logistics

Decide on:

• Format: Remote (video call) vs. in-person. Research from the Journal of Usability Studies suggests that remote interviews produce comparable data quality for most topics, with higher participant recruitment rates.
• Recording: Always get consent. Record audio and video if possible — transcripts are essential for analysis.
• Duration: 30–60 minutes is the sweet spot. Shorter and you can't go deep; longer and fatigue sets in.
• Incentives: Appropriate compensation shows respect for participants' time. See finding research participants for guidance on incentive amounts.

Conducting the Interview

Opening (First 5 Minutes)

The first few minutes set the tone for the entire conversation. Your goals are to:

1. Make the participant comfortable. Small talk matters. Ask how their day is going.
2. Explain the purpose. "We're trying to understand how people approach [topic]. There are no right or wrong answers — we're learning from your experience."
3. Get consent. "Is it okay if I record this conversation? The recording is only for our research team."
4. Set expectations. "This will take about 45 minutes. I'll be asking questions and mostly listening. Feel free to say if any question doesn't make sense."

The Core Conversation

This is where your skill as an interviewer matters most. Here are the techniques that separate great interviews from mediocre ones:

Follow the energy. When a participant's voice changes — they speed up, slow down, show frustration or excitement — that's a signal. Follow it. "You seemed really frustrated when you mentioned that. Can you tell me more?"

Use the 5-second rule. After a participant finishes an answer, wait 5 seconds before asking your next question. People often fill silence with their most honest, unfiltered thoughts.

Probe with purpose. Generic follow-ups like "tell me more" are fine occasionally, but targeted probes are more effective:

• "You mentioned X — what did you mean by that?"
• "Can you walk me through a specific time that happened?"
• "What happened next?"
• "How did that make you feel?"

Ask for stories, not opinions. "Tell me about the last time you had to onboard a new team member" produces richer data than "What do you think about onboarding?"

Stay neutral. Don't react to answers with "That's great!" or "Oh no." Use neutral acknowledgments: "That's helpful," "I see," or a simple nod.

Closing (Final 5 Minutes)

End with catch-all questions that give participants space to share things you didn't think to ask:

• "Is there anything about [topic] that I should have asked about but didn't?"
• "Is there anything else you'd like to share?"

Thank them genuinely. Tell them what happens next.

Analyzing Your Interviews

Raw interview recordings are useless until you transform them into structured insights. This is where many research projects stall — analysis is time-consuming and cognitively demanding.

Research from the University of Auckland found that manual qualitative coding typically takes 5 to 8 hours per hour of interview recording. For a study of 10 interviews averaging 45 minutes each, that's 37 to 60 hours of analysis work.

The analysis process typically follows these steps:

1. Transcribe all recordings. Use automated transcription and then review for accuracy.
2. Read through all transcripts to get an overall sense of the data.
3. Code the data by tagging meaningful segments with labels.
4. Identify themes by grouping related codes together.
5. Synthesize themes into findings that answer your research questions.

For a complete breakdown of the analysis process, see our thematic analysis guide and affinity mapping guide.

Platforms like Koji can significantly accelerate this process by automatically transcribing interviews and using AI to surface initial themes — turning weeks of manual coding into hours of guided analysis. This lets you spend more time interpreting what the patterns mean rather than hunting for them.

Common Mistakes to Avoid

Building an Interview Practice

The best research teams don't treat interviews as one-off events — they build a continuous practice of talking to users. Here's how to get there:

• Establish a regular cadence. Even 2–3 interviews per month keeps you connected to your users.
• Create a participant pool. Maintain a list of people who've consented to be contacted for future research.
• Build organizational buy-in. Invite stakeholders to observe interviews (with participant consent). Nothing converts skeptics faster than hearing a user struggle with something the team thought was obvious.
• Document and share. Make findings accessible to the whole team, not locked in a researcher's notebook.

Next Steps

Ready to start interviewing? Here's your learning path:

1. How to Write Great Interview Questions — craft questions that surface honest, useful answers
2. Finding Research Participants — recruit the right people efficiently
3. How Many Interviews Are Enough? — know when you've reached saturation
4. Thematic Analysis Guide — turn raw transcripts into structured insights