User Interview Script Template for User Research

What This Template Is For

A good interview script is the difference between a useful 30-minute conversation and a meandering chat that produces nothing actionable. Most PMs either wing it (and miss critical topics) or read from a rigid list (and miss the follow-up that would have surfaced the real insight). This template gives you a structured script with built-in flexibility: a clear sequence of phases, specific questions for each, and probing techniques you can deploy when a participant says something interesting.

The script follows a five-phase structure: warm-up, context mapping, pain point exploration, solution validation, and wrap-up. Each phase has a purpose, a time allocation, and transition language so the conversation flows naturally. The probing techniques section teaches you how to go deeper without leading the participant toward the answer you want to hear.

This template focuses on the script itself. If you need to plan the broader research effort (recruiting, sample size, synthesis), use the User Research Plan Template. For turning interview insights into structured personas, see the User Persona Template. The Product Discovery Handbook covers the full discovery methodology from problem framing through validation.

How to Use This Template

1. Define your learning goal. Write one sentence describing what you need to learn from this interview. Every question in the script should serve this goal.
2. Customize the core questions. Replace the bracketed placeholders with questions specific to your product area. Keep the phase structure and time allocations.
3. Print or open the script during the interview. Use it as a guide, not a teleprompter. Let the conversation breathe, but glance at the script to stay on track.
4. Use the probing techniques. When a participant says something interesting, resist the urge to move on. Use the follow-up probes listed below to dig deeper.
5. Complete the debrief sheet within 30 minutes. Memory degrades fast. Fill in the debrief immediately after each session while details are fresh.
6. Synthesize across interviews. After 5-8 interviews, look for patterns in your debrief sheets. Three people describing the same pain point is a signal. One person's pet peeve is an anecdote.

Probing Techniques Reference

Use these follow-up techniques whenever a participant gives a surface-level answer. The goal is to move from opinions to specific behaviors and stories.

The Interview Script

Pre-Interview Setup (5 minutes before)

Checklist before starting:

• ☐ Recording tool tested and ready (with participant's consent)
• ☐ Note-taker briefed on what to capture
• ☐ Script printed or on second screen
• ☐ Quiet room, no interruptions scheduled
• ☐ Incentive ready if applicable (gift card, etc.)

Phase 1: Warm-Up (3-5 minutes)

Purpose. Build rapport. Put the participant at ease. Establish that there are no wrong answers.

Opening script:

"Thank you for taking the time to speak with me today. I am [name], a product manager at [company]. I am talking to people like you to understand how you [describe the activity or workflow area]. There are no right or wrong answers. I am here to learn from your experience. Everything you share will be used to improve our product, and your responses will be kept confidential. Is it OK if I record this session for my notes?"

Warm-up questions:

1. Tell me a little about your role. What does a typical day look like?
2. How long have you been in this role?
3. What tools or systems do you use most in your day-to-day work?

Transition. "Great, that is really helpful context. Now I would like to focus on [specific topic area]."

Phase 2: Context Mapping (5-7 minutes)

Purpose. Understand the participant's current workflow, environment, and constraints before exploring problems.

1. Walk me through how you currently [do the activity you are researching]. Start from the beginning.
2. Who else is involved in this process? What is their role?
3. How often do you do this? [Daily, weekly, per project?]
4. What tools or workarounds are you using today to handle this?
5. On a scale of 1-10, how satisfied are you with your current approach? What would it take to get to a 10?

Probing follow-ups:

• "You mentioned [tool/workaround]. What made you start using that?"
• "You said [other people] are involved. How do you coordinate with them?"

Phase 3: Pain Point Exploration (10-12 minutes)

Purpose. Surface specific, concrete frustrations. Get stories, not opinions.

1. What is the most frustrating part of [this activity]? Can you tell me about the last time it happened?
2. When things go wrong with [this process], what usually causes it?
3. How much time do you spend on [the workaround or manual process] each week?
4. What is the cost when this goes poorly? [Lost time, errors, rework, missed deadlines?]
5. Have you tried other solutions to fix this? What happened?
6. Is there anything you have given up trying to fix because it felt too hard?

Probing follow-ups:

• "You said it takes [X hours] a week. Walk me through what that looks like."
• "What happens downstream when that goes wrong? Who feels the impact?"
• "You mentioned you tried [alternative]. What specifically did not work about it?"

Red flags to listen for:

• Participant describes pain in vague terms. Use the Timeline and Quantify techniques.
• Participant jumps to solutions. Use the Redirect technique to bring them back to the problem.
• Participant says "it is fine." Probe with: "If you could wave a magic wand and change one thing about this, what would it be?"

Phase 4: Solution Exploration (5-7 minutes)

Purpose. Test the value of potential solutions without pitching your product. Gauge willingness to change.

1. If [the pain point from Phase 3] were solved completely, what would that change for you or your team?
2. What would a solution need to do for you to switch from your current approach?
3. [If applicable] I want to show you a rough concept. This is early thinking, not a finished product. [Show prototype/wireframe.] What is your first reaction?
4. What concerns would you have about adopting a new tool or process for this?
5. Who else would need to be on board for you to make a change like this?

Probing follow-ups:

• "You mentioned [concern]. Can you tell me more about what is driving that?"
• "If this cost [price range], would that be a budget you could access, or would you need approval?"

Phase 5: Wrap-Up (3 minutes)

Purpose. Close gracefully. Leave the door open for follow-up.

1. Is there anything about [this topic] that I should have asked but did not?
2. Is there anyone else on your team you think I should talk to?
3. Would you be open to a follow-up conversation in a few weeks if we have more questions?

Closing script:

"Thank you so much for your time today. This has been really valuable. [If incentive:] I will send your [gift card/incentive] within 24 hours. If anything else comes to mind after we hang up, feel free to email me."

Post-Interview Debrief Sheet

Complete this within 30 minutes of the interview. Brevity is fine. The goal is to capture signal before your memory fades.

Filled Example: B2B SaaS Onboarding Flow Study

Pre-Interview Setup

Phase 2 Example Exchange

Interviewer: Walk me through how a new customer gets started with DataStack after they sign up.

Rachel: So they get a welcome email with a link to the setup wizard. The wizard has six steps: connect your data source, configure your first dashboard, invite team members, set up alerts, choose a billing plan, and then there is a final review screen.

Interviewer: Six steps. How long does that typically take a new customer?

Rachel: It depends. If they have their database credentials handy and know what they want to see, maybe 20 minutes. But honestly, most people get stuck at step one, the data source connection. They need to get credentials from their engineering team, which can take days.

Interviewer: (Echo) "Can take days." Tell me more about what happens during that waiting period.

Rachel: They just leave. The setup wizard does not save progress, so when they come back three days later, they have to start over. I have had customers tell me they did the first two steps three times before they finally got everything connected.

Phase 3 Example Exchange

Interviewer: You said customers have to start over if they leave mid-setup. How often does that happen?

Rachel: A lot. I would estimate 60-70% of my onboarding calls are with people who got stuck and gave up. By the time they schedule a call with me, they are already frustrated.

Interviewer: (Quantify) How many onboarding calls do you handle per week?

Rachel: About 12-15. And each one takes 30 minutes. So I am spending 6-7 hours a week just helping people through a setup process that should be self-serve.

Interviewer: (Contrast) What would a good first-time experience look like for these customers?

Rachel: Honestly? Let them skip the data connection step and give them a sandbox with sample data. Let them see what a dashboard looks like before they invest the time to connect their real data. Right now they are doing all this work on faith. They do not know what the payoff looks like.

Debrief Sheet

Common Mistakes to Avoid

• Reading questions robotically. The script is a guide, not a teleprompter. Make eye contact (or camera contact). Listen to answers. Follow interesting threads even if they are not on the script.
• Asking leading questions. "Do you think our onboarding is too long?" leads the witness. "Walk me through your onboarding experience" does not. If you catch yourself starting a question with "Do you think..." or "Would you say...", rephrase it.
• Skipping the debrief. You will forget 50% of the details within two hours. The debrief sheet takes five minutes and preserves the insights that matter.
• Interviewing only power users. Your happiest customers will tell you everything is great. Interview churned users, trial abandoners, and people who considered your product but chose a competitor. That is where the best learning lives.
• Stopping after three interviews. Patterns do not emerge from three conversations. Plan for 5-8 interviews per research question. Track themes across your debrief sheets and stop when you hear the same stories repeated.

Key Takeaways

• A five-phase structure (warm-up, context, pain, solution, wrap-up) keeps interviews focused and natural
• Probing techniques like Echo, Timeline, and Silence surface deeper insights than scripted questions alone
• Complete the debrief sheet within 30 minutes of every interview to preserve signal
• Plan for 5-8 interviews per research question before drawing conclusions
• Never show a solution before you have fully explored the problem

About This Template

Created by: Tim Adair

Last Updated: 3/4/2026

Version: 1.0.0

License: Free for personal and commercial use