How to Conduct User Interviews: A Beginner's Guide

User interviews are the foundation of qualitative UX research. They reveal the motivations, frustrations, and mental models behind user behavior — things that analytics, surveys, and usability tests cannot surface on their own. A 45-minute conversation with a real user will teach you more about their needs than weeks of internal debate.

This guide covers the entire process from planning through analysis, written for researchers conducting their first interviews or looking to strengthen their technique.

Why User Interviews Matter

Quantitative methods tell you what users do. Interviews tell you why. A survey might reveal that 40% of users abandon your onboarding flow at step 3. An interview with someone who abandoned reveals that step 3 asks for information they do not have readily available, and they intended to come back later but forgot. That "why" changes how you solve the problem entirely.

Interviews also surface needs and pain points that users would never think to mention in a survey because they have accepted them as normal. When you watch someone describe their workflow, the workarounds they take for granted often reveal the biggest design opportunities.

Step 1: Define Your Research Goals

Start by writing down the specific questions your interviews need to answer. These are not the questions you will ask participants — they are the questions your team needs answered to make product decisions.

Examples of good research goals:

• What triggers users to look for a tool like ours?
• What does the first week of using our product look like?
• Where do users get stuck, and what do they do when that happens?
• How does our product fit into users' broader workflow?

Keep research goals to 3-5 questions. More than that and your interviews will either run too long or cover each topic too superficially.

Each research goal should connect to a product decision. If you cannot articulate what you will do differently based on the answer, refine the goal until you can.

Step 2: Write Your Interview Guide

An interview guide is a structured list of questions and topics that keeps your conversation focused without making it rigid. It is not a script — you will deviate from it constantly — but it ensures you cover every research goal with every participant.

Structure your guide in three sections:

Opening (5-10 minutes) Build rapport and establish context. Ask about the participant's role, experience, and relationship to the problem space.

• "Tell me about your role and what a typical day looks like."
• "How do you currently handle [the problem your product addresses]?"
• "Walk me through the tools you use for [relevant task]."

Core exploration (25-35 minutes) Dive into your research goals with open-ended questions. Organize questions by topic, not by priority — jumping between unrelated topics confuses participants.

For each topic, prepare:

• A primary question that opens the topic
• 2-3 follow-up probes for going deeper
• A closing question that checks for anything you missed

Example topic block:

• Primary: "Tell me about the last time you needed to reorganize your site's navigation."
• Probe: "What prompted that decision?"
• Probe: "What was the hardest part of that process?"
• Probe: "How did you know when the new structure was working?"
• Closing: "Is there anything about that experience we haven't covered?"

Wrap-up (5-10 minutes) Give participants space to add anything you did not ask about, and end on a positive note.

• "What's the one thing you wish was easier about [problem space]?"
• "Is there anything I should have asked about but didn't?"
• "Thank you — this has been incredibly helpful."

Question-writing rules:

1. Ask open-ended questions. "Tell me about..." and "Describe a time when..." produce richer data than yes/no questions.
2. Ask about specific past behavior, not hypotheticals. "Tell me about the last time you..." is more reliable than "What would you do if..."
3. Avoid leading questions. "How frustrated were you with the onboarding?" assumes frustration. "How was your onboarding experience?" is neutral.
4. Do not ask compound questions. "How did you find the product and what made you decide to sign up?" is two questions. Ask them separately.

Step 3: Recruit the Right Participants

You need 5-8 participants per user segment. Recruiting the right people matters more than recruiting many people — three interviews with your actual target users produce better insights than ten interviews with the wrong audience.

Where to find participants:

• Your existing user base (reach out through in-app prompts or email)
• Social media groups and forums where your target users congregate
• Professional recruitment platforms like Prolific or UserTesting
• Personal networks (with caution — friends and colleagues may not be representative)

Screening criteria to define:

• Demographics that match your target user
• Experience level with the problem space
• Frequency of relevant behaviors
• Exclusions (employees, competitors, people who recently participated in research)

Compensation: Always compensate participants for their time. Industry norms range from $50-150 for a 60-minute session depending on the audience. Professional or specialized audiences expect higher compensation.

Schedule 45-60 minute sessions with 15-minute buffers between them. Back-to-back interviews without breaks lead to interviewer fatigue and declining question quality.

Step 4: Conduct the Interview

Before the session

• Test your recording equipment and video conferencing setup
• Have your interview guide open but not visible to the participant
• Prepare a brief introduction explaining the session format and how data will be used
• Get explicit consent to record

During the session

Listen more than you talk. Your ratio should be roughly 80% participant talking, 20% you. Resist the urge to fill silences — participants often share their most valuable insights after a pause while they gather their thoughts.

Follow the energy. If a participant becomes animated about a topic, follow that thread even if it is not in your guide. Their enthusiasm signals something important.

Use probing techniques:

• Echo: Repeat the last few words as a question. ("...and that was really frustrating?" prompts elaboration without directing)
• Silence: Wait 3-5 seconds after a participant finishes. They will often continue with deeper reflection.
• Ask for stories: "Can you walk me through exactly what happened?" produces richer data than "Why did you do that?"
• Redirect gently: If a participant goes far off topic, say "That's really interesting — I want to come back to something you mentioned earlier about..."

Tracking sentiment

As you interview, note the emotional tone alongside the content. Track moments of:

• Frustration — What caused it? How did they express it?
• Satisfaction — What delighted them? What exceeded expectations?
• Confusion — Where did they hesitate or ask clarifying questions?
• Resignation — Where have they accepted a poor experience as normal?

Sentiment data is critical for prioritization. A pain point expressed with frustration is more urgent than one described matter-of-factly, even if both involve the same feature.

Step 5: Take Effective Notes

Even with recording, real-time notes serve an important function — they capture your observations and interpretations while context is fresh.

Note-taking best practices:

• Use a dedicated note-taker if possible so the interviewer can focus fully on the conversation
• Capture direct quotes in quotation marks — these become your most powerful evidence
• Note non-verbal cues (hesitation, excitement, confusion) that audio alone misses
• Mark surprising or contradictory statements for follow-up analysis
• Write a 2-3 sentence summary immediately after each session while your memory is sharpest

Step 6: Analyze and Detect Themes

After completing all interviews, analysis turns individual conversations into patterns that inform decisions.

Transcription

Transcribe recordings fully or use AI transcription tools. Even rough transcripts are more reliable than memory. Highlight key quotes that illustrate important findings.

Thematic coding

Read through each transcript and tag statements with theme labels:

1. First pass — Read one transcript and create initial theme codes organically (e.g., "onboarding confusion," "workaround for missing feature," "trust concern")
2. Second pass — Apply those codes to remaining transcripts, adding new codes as needed
3. Third pass — Consolidate similar codes into broader themes and count how many participants mentioned each

Pattern detection

A theme mentioned by 1 participant is an anecdote. A theme mentioned by 3+ participants (out of 5-8) is a pattern worth acting on. Focus recommendations on patterns, not individual stories.

Connecting to other research methods

Interview findings generate hypotheses that other methods can validate at scale. If 4 of 6 interview participants described navigation confusion, validate the specific problem with a tree test. If participants used unexpected vocabulary for your features, test those labels with a card sort. Use surveys to quantify how widespread an interview finding is across your full user base.

Presenting Your Findings

Structure your findings report around themes, not individual interviews. For each theme:

1. State the finding in one sentence
2. Provide the supporting evidence (participant count, representative quotes)
3. Connect it to a product recommendation
4. Assign a priority based on severity and frequency

Use direct quotes liberally. A participant's exact words are more persuasive to stakeholders than a researcher's summary. The best interview findings reports make readers feel like they were in the room.

Further Reading

• How to Write Effective UX Survey Questions
• How to Conduct Stakeholder Interviews
• How to Present UX Research to Stakeholders
• How to Choose the Right UX Research Method

Frequently Asked Questions

How many user interviews do I need to conduct? 5-8 interviews per user segment typically surface the major themes. You will notice diminishing new insights after 5-6 interviews — this is called thematic saturation. If your user base includes multiple distinct segments (e.g., administrators and end users), plan 5-8 interviews per segment.

How long should a user interview last? Plan for 45-60 minutes. Sessions shorter than 30 minutes rarely get past surface-level answers, while sessions longer than 60 minutes cause participant fatigue and reduce response quality. Build your interview guide to fill 45 minutes comfortably, with optional extension questions if the conversation is productive.

Should I record user interviews? Always record with explicit participant consent. Recording lets you focus on the conversation and active listening rather than frantic note-taking, and ensures you capture exact quotes for your findings report. Use both audio and video when possible — facial expressions and body language provide context that audio alone misses.