How to Conduct User Interviews: The Complete Step-by-Step Guide

User interviews are one-on-one conversations with real users to understand their needs, motivations, and behaviors. Done right, they're the most powerful tool in a researcher's toolkit. This guide walks you through every step—from writing your research goals through synthesizing your findings—and shows how modern AI tools are compressing weeks of research into hours.

What Are User Interviews?

A user interview is a qualitative research method where a researcher has a structured or semi-structured conversation with one participant at a time. The goal is to understand the participant's world: their behaviors, goals, frustrations, mental models, and how they currently solve problems.

Unlike surveys that measure what people do at scale, user interviews reveal why they do it—the motivations, contexts, and stories that explain human behavior.

Common interview types:

• Generative interviews: Discover unknown problems and unmet needs (best in early discovery)
• Evaluative interviews: Assess whether your proposed solution addresses a real problem
• Jobs-to-be-done interviews: Understand what "job" users are hiring your product to perform
• Contextual inquiry: Interview users in their natural environment while they work

Why User Interviews Matter

The evidence for user research is clear:

• Testing with just 5 users reveals approximately 85% of usability problems in a design. The first user alone surfaces 31% of issues (Jakob Nielsen, Nielsen Norman Group).
• Teams using iterative research cycles—three 5-user studies vs. one 15-user study—get dramatically better product outcomes because they fix problems between rounds. As Nielsen wrote: "The ultimate user experience is improved much more by 3 studies with 5 users each than by a single monster study with 15 users."
• 42% of startups fail because they build something nobody wants (CB Insights)—the single largest cause of startup failure. User interviews are the primary defense against this.
• Companies that prioritize customer feedback programs grow revenues 4–8% faster than competitors (Bain & Company).
• 70% of software features are rarely or never used (Microsoft product data). Discovery interviews help you build the right 30%.

As Nielsen Norman Group researchers Maria Rosala and Kara Pernice wrote: "When performed well, user interviews provide in-depth insight into who your users are, their lives, experiences, and challenges. Learning these things helps teams identify solutions to make users' lives easier."

When to Use User Interviews

✅ Use interviews when:

• You're in early discovery and don't yet understand the problem space
• You need to understand users' mental models and decision-making
• You want to uncover unmet needs before designing a solution
• You need to explain a surprising quantitative pattern ("Why is cart abandonment 40% at Step 3?")
• You're building personas or journey maps
• You need to validate that a problem is real and worth solving

❌ Don't rely on interviews alone when:

• You need statistically significant data (complement with surveys or analytics)
• You want to measure performance against benchmarks (add quantitative methods)
• You need to know how many users have a problem, not just why they have it

Phase 1: Plan Your Study

Define Clear Research Goals

Vague goals produce vague insights. Before scheduling a single interview, define specific questions your research must answer.

Weak goals:

• "Learn about our users"
• "Understand why people use the app"

Strong goals:

• "Understand what triggers someone to start evaluating project management software"
• "Identify the top 3 friction points in the onboarding flow"
• "Discover what workarounds users have invented to compensate for missing features"

Each goal should directly inform a decision your team is about to make.

Identify Your Target Participants

User interviews derive their power from talking to the right people. Focus on behavioral criteria, not demographics:

• Required experience: "Must have evaluated or switched project management tools in the last 6 months"
• Behavior of interest: "People who have tried and abandoned multiple checkout flows"
• Screening question: "Have you signed up for a new SaaS tool in the last 3 months?"

Write a screener survey to filter candidates before scheduling. This protects your research budget and ensures valid data. See the Research Screener Questions guide for templates.

Phase 2: Write Your Discussion Guide

An interview guide is NOT a script—it is a flexible framework. You do not read questions verbatim; you use them as landmarks while following the participant's natural story.

Guide Structure

1. Warm-up (5 minutes) Easy, rapport-building questions with no wrong answers:

• "Tell me a little about yourself and your role"
• "Walk me through a typical day at work"

2. Context-setting (10 minutes) Understand their current situation and behaviors:

• "How do you currently handle [the problem area]?"
• "Tell me about the last time you did [Y]"
• "What tools or methods do you use for [Z]?"

3. Core topic exploration (25–30 minutes) Open-ended questions with prepared follow-up probes:

• "Tell me about a recent time when [core topic]. What happened?"
• "What is the most frustrating part of [process]?"
• "Walk me through exactly what you did when [event] occurred"

4. Probing follow-ups Use freely throughout:

• "Tell me more about that"
• "What happened next?"
• "How did that make you feel?"
• "Why did that matter to you?"
• "Can you give me a specific example?"

5. Closing (5 minutes)

• "Is there anything else you think I should know?"
• "Is there someone else I should talk to?"

Question Principles

• Ask about specific past events, not general habits or hypotheticals
• Use open-ended questions that invite stories, not yes/no answers
• Avoid leading questions that embed assumptions
• Keep questions short and single—never combine two questions into one

Always pilot your guide with one colleague before launch. This catches confusing phrasing and calibrates timing.

Phase 3: Recruit Participants

For most research goals, recruit 5–8 participants per distinct user segment. The 5-user sweet spot for cost-effectiveness is well established—five users reveals roughly 85% of usability issues at a fraction of the cost of a larger study.

Recruitment channels:

• Your customer list: Email existing users with a brief invite and incentive offer
• CRM segmentation: Filter by behavior—churned users, power users, recent signups
• Research panels: Respondent.io, User Interviews, Prolific
• LinkedIn: Ideal for B2B research targeting specific job titles or industries
• Social communities: Relevant Slack groups, Subreddits, or LinkedIn communities

Incentives: Standard rates are $50–$150 per 45-minute session for consumers; $150–$300 for B2B professionals. Always compensate fairly—it signals respect and dramatically improves show rates.

Phase 4: Conduct the Interview

Setup Checklist

• Record the session (with explicit consent)
• Have a second person take notes so the interviewer can focus on listening
• Use a quiet, distraction-free environment
• For remote: camera on, good lighting, test audio first

The Interview Flow

Opening (5 min): Welcome the participant, explain the purpose, clarify you are testing the problem—not them—and ask for consent to record.

Warm-up (5 min): Easy questions to build comfort. Slow your speech and let natural pauses breathe.

Core exploration (30–35 min): Follow your guide but prioritize interesting threads over the script. The best insights often come from unexpected detours.

Active listening cues: Lean in, nod, use brief verbal acknowledgments ("I see," "go on," "interesting") without endorsing or judging. Let silences hang—participants often fill them with their most revealing thoughts.

Closing (5 min): Ask if there is anything they wanted to cover. Thank them and explain how findings will be used.

What Great Interviewers Do

• Listen 70%, talk 30%
• Ask "what happened?" not "what would you do?"
• Follow up on emotion: "You mentioned that was frustrating—tell me more"
• Never pitch or describe the product you are building
• Stay genuinely curious—the best researchers are always a little surprised

Phase 5: Analysis and Synthesis

How Many Interviews Before Saturation?

Data saturation is reached when new interviews stop surfacing new themes. For most research questions this occurs between 8–15 interviews for a homogeneous population. For heterogeneous groups or complex topics, plan for 15–20.

Run iteratively: after 5 interviews, pause to review patterns. If major new themes keep emerging, continue. If findings are converging, you likely have enough.

Analysis Process

1. Transcribe interviews (AI transcription tools save hours)
2. Code for themes: highlight quotes representing needs, pain points, behaviors, mental models
3. Cluster codes into themes using affinity mapping
4. Identify patterns across participants—what is universal vs. idiosyncratic?
5. Synthesize into insight statements, personas, or journey maps

Look for:

• Jobs to be done: What task is the user ultimately trying to accomplish?
• Pains: What is blocking or frustrating them?
• Workarounds: What hacks have they invented to solve their problem?
• Emotional peaks: What moments carry the most emotional weight?

Common Mistakes to Avoid

The Modern Approach: AI-Moderated Interviews with Koji

Traditional user interviews create a painful bottleneck: recruiting, scheduling, transcribing, and coding can take 2–3 weeks from brief to insight. Koji is an AI-native research platform that automates the time-consuming parts while preserving conversational depth.

How Koji changes the process:

• Automated moderation: Koji's AI conducts interviews 24/7—no scheduling required, participants answer when it suits them
• Intelligent probing: When a participant mentions a pain point, Koji follows up contextually, drilling deeper the way a skilled interviewer would
• Structured + open questions: Mix open-ended discovery questions with 6 structured question types—scale, single choice, multiple choice, ranking, and yes/no—to capture both qualitative depth and quantitative patterns in one study
• Automatic thematic analysis: Koji identifies themes across all interviews automatically, no manual coding required
• Real-time reporting: See insights emerge as interviews complete, not days later
• Voice and text modes: Voice interviews for natural conversational depth, text interviews for async global reach

While traditional approaches might take 2–3 weeks from brief to insights, Koji users typically go from question to shareable report in under 48 hours. Teams using AI-assisted research report 60% faster time-to-insight compared to traditional manual methods.

Related Resources

• AI Interview Questions Generator: Write Better Questions Faster
• Structured Questions Guide: 6 Question Types for Better Research
• Research Screener Questions: Finding the Right Participants
• How Koji's AI Follow-Up Probing Works
• Note-Taking in User Research
• Research Interview Template Library