Analytics can tell you what users do, but only a conversation can tell you why. User interviews uncover motivations, habits, and frustrations that no dashboard shows. Yet a poorly planned interview can waste an hour on leading questions, vague answers, and opinions about features nobody has used.

This guide gives you a free user interview script template, sample questions, and moderation tips so every conversation produces insights your team can act on.

What Is a User Interview Script?

A user interview script, also called a discussion guide, is a flexible outline of topics and questions for a research conversation. It isn’t a rigid survey. It helps you cover the important areas, stay neutral, and still follow interesting threads when they appear.

Why a Script Matters

A good script helps you:

• Stay focused on your research goals
• Avoid leading questions that bias answers
• Keep sessions consistent across participants
• Manage time so key topics aren’t missed
• Make analysis easier by collecting comparable data

When to Use User Interviews

Interviews work best when you need depth and context.

• Early discovery, to understand needs and problems
• Workflow research, to see how people work today
• Concept validation, before investing in design
• Persona and journey map creation, to ground them in real stories
• Post-launch research, to understand why metrics changed

Before You Write the Script: Planning Checklist

• Research goals: what decisions will this research inform?
• Participants: who should you talk to, and how will you recruit them?
• Number of interviews: many studies start with five to eight per user segment
• Format and length: in person or remote, usually 30 to 60 minutes
• Consent and recording: how will you store and protect data?
• Team roles: who interviews, and who takes notes?

Free User Interview Script Template

Section 1: Introduction (3 to 5 minutes)

“Thanks for making time today. I’m [Name] from [Team]. I’d like to learn about how you [topic]. This isn’t a test, and there are no right or wrong answers. I’m interested in your honest experience.

With your permission, I’ll record the session for note-taking only. Your answers will stay confidential, and you can skip any question or stop at any time. Is that okay?”

Section 2: Warm-Up Questions (5 minutes)

• “Tell me a bit about yourself and what you do.”
• “What does a typical week look like for you?”
• “How does [topic] fit into your routine?”

Warm-up questions relax the participant and give you context for everything that follows.

Section 3: Core Topic Questions (20 to 30 minutes)

Organize questions by theme and adapt them to your study.

Section 4: Probing Questions

Use probes to go deeper without leading.

• “Can you tell me more about that?”
• “Why was that important to you?”
• “What happened next?”
• “Can you give me an example?”
• “How did that make you feel?”

Section 5: Wrap-Up (5 minutes)

• “Is there anything we haven’t covered that you think is important?”
• “Who else should I talk to about this?”
• “Thank you. Your insights are very helpful.”

Types of Interview Questions

Good vs. Poor Interview Questions

Questions about past behavior reveal far more than questions about future intentions, because people are poor predictors of what they will do.

How to Run a Great Interview

Before the Interview

• Pilot your script with a colleague to catch unclear questions
• Test your recording setup and backup tools
• Confirm the time, link, and consent with the participant
• Review your research goals one more time

During the Interview

• Listen more than you talk. Aim for the participant speaking most of the time.
• Embrace silence. Pauses often lead to the most honest answers.
• Follow interesting threads, even if they’re off-script.
• Avoid pitching or defending your product.
• Note emotions and body language, not only words.

After the Interview

• Write a quick summary within 24 hours while memory is fresh
• Tag quotes and themes in your notes or repository
• Compare across participants to find patterns
• Share clear insights, not raw transcripts

Simple Note-Taking Template

Common Interview Mistakes

• Asking leading or hypothetical questions
• Interviewing the wrong audience
• Talking too much and filling every silence
• Taking answers at face value without asking for examples
• Treating one interview as proof of a trend
• Skipping analysis, leaving notes unused
• Forgetting consent and privacy basics

Turn Interviews into Impact

Interviews are most valuable when they change decisions. Experienced UX research services teams can help with recruiting, moderation, and analysis, so your insights are credible and ready to use. Once findings are in hand, a facilitated design thinking workshop helps stakeholders turn insights into shared priorities and concrete ideas. And when research points to a redesign, UI/UX design services can translate what you learned into tested, user-centered interfaces.

How to Analyze Interview Data

• Transcribe or summarize each session
• Highlight key quotes and observations
• Group similar notes into themes using affinity mapping
• Count patterns across participants, such as how many mentioned the same pain point
• Write insight statements in this format: “[User] needs [need] because [reason]”
• Prioritize by frequency, severity, and business impact

Frequently Asked Questions

How long should a user interview be?

Usually 30 to 60 minutes. Longer sessions risk fatigue and shallow answers.

How many user interviews do I need?

Many studies start with five to eight interviews per user segment, then continue until new interviews stop revealing new patterns.

Should I send the questions in advance?

Share the topic and expected length, but not the detailed questions, so answers stay natural and unrehearsed.

Should I record user interviews?

Yes, with clear consent. Recordings improve accuracy and let you focus on the conversation instead of typing.

What is the difference between a user interview and a usability test?

An interview explores experiences, needs, and motivations through conversation. A usability test observes people completing tasks with a product to find usability problems.

Final Thoughts

A good interview script gives you structure without limiting curiosity. Use the template, ask about real past behavior, stay neutral, and analyze findings quickly. Small, thoughtful conversations often reveal the insights that change a product’s direction.