Customer Interview Script Templates for Product Managers

Running a customer interview without a script is like sailing without a map—you might eventually find land, but you'll waste a lot of time getting there.

Yet most product managers wing their customer calls. They ask whatever comes to mind, let the conversation meander, and walk away with notes that don't connect to anything actionable.

This guide gives you battle-tested interview scripts you can use immediately, plus the thinking behind why each question works. Whether you're doing discovery for a new feature, validating an idea, or diagnosing churn, there's a template here for you.

TL;DR: Key Takeaways

• Structure beats improvisation: A good script keeps you on track while staying conversational
• Open-ended questions reveal more: Avoid yes/no questions that lead witnesses
• Context before opinions: Ask about behavior first, feelings second
• Follow-up is everything: The best insights come from "tell me more about that"
• Different goals need different scripts: Discovery, validation, and churn interviews each require unique approaches

Why You Need an Interview Script

Research from IDEO shows that unstructured interviews produce inconsistent data that's difficult to synthesize. Meanwhile, overly rigid scripts make conversations feel like interrogations.

The sweet spot? A flexible framework that ensures you cover key topics while letting natural conversation flow.

A good script helps you:

• Stay consistent across multiple interviews
• Avoid leading questions that bias responses
• Remember to ask the important stuff when you're nervous
• Compare answers across different customers
• Train teammates to conduct interviews themselves

The Universal Customer Interview Framework

Before diving into specific scripts, here's the framework that underpins all great customer interviews:

1. Warm-Up (2-3 minutes)

Build rapport. Explain the purpose. Set expectations about time.

2. Context Gathering (5-10 minutes)

Understand their role, their world, and the problems they face daily.

3. Deep Dive (15-20 minutes)

Explore specific topics related to your research goals.

4. Synthesis & Close (5 minutes)

Summarize what you heard, ask if you missed anything, thank them.

Now, let's get into the scripts.

Script 1: Discovery Interview Template

Use when: You're exploring a problem space and don't yet know what to build.

Opening (2 minutes)

"Thanks for making time for this. We're researching how [target audience] handles [problem area]. I'm not here to sell anything—I just want to understand your experience. There are no right or wrong answers. Is it okay if I take notes?"

Context Questions (5 minutes)

• "Can you walk me through your role? What does a typical week look like?"
• "What are the biggest challenges you face in [relevant area]?"
• "How long have you been dealing with [problem area]?"

Behavior Questions (10 minutes)

These reveal what people actually do, not what they say they do:

• "Tell me about the last time you [relevant task]. Walk me through exactly what happened."
• "What triggered that? What made you decide to do it?"
• "Who else was involved? What did they do?"
• "What happened after that?"
• "How often does this come up?"

Pain Point Questions (10 minutes)

• "What's the most frustrating part of [process]?"
• "If you could wave a magic wand and fix one thing, what would it be?"
• "What have you tried in the past to solve this? What happened?"
• "How much time/money does this problem cost you?"

Closing (5 minutes)

• "Is there anything I should have asked but didn't?"
• "Who else should I be talking to about this?"
• "Would it be okay to follow up if I have more questions?"

Script 2: Solution Validation Interview Template

Use when: You have an idea or prototype and want to test if it solves a real problem.

Opening (2 minutes)

"Thanks for joining me. We've been working on something that might help with [problem], and I'd love your honest feedback. I'm testing the idea, not you—so if this doesn't make sense or seems useless, please tell me. Brutal honesty helps us build something better."

Problem Confirmation (5 minutes)

Before showing anything, confirm the problem exists:

• "Tell me about how you currently handle [problem]."
• "On a scale of 1-10, how painful is this for you?"
• "What would it mean for your work if this problem went away?"

Concept/Prototype Presentation (5 minutes)

Show your solution. Keep it simple. Don't oversell.

Reaction Questions (15 minutes)

• "What's your first reaction?"
• "What would you use this for?"
• "What's confusing or unclear?"
• "What's missing that would make this more useful?"
• "How does this compare to what you use today?"
• "Would you switch from your current solution to this? Why or why not?"

The Critical Question

According to The Mom Test by Rob Fitzpatrick, this is the most important question:

"If I built this, what would you expect to pay for it?"

Watch for hesitation. Real interest shows in specifics, not enthusiasm.

Closing (5 minutes)

• "Anything else I should know?"
• "Can I reach out when we have something to try?"

Script 3: Churn Investigation Interview Template

Use when: A customer has cancelled or is at risk, and you need to understand why.

Opening (2 minutes)

"Thanks for being willing to chat. I know you decided to move on from [product], and I want to understand what happened—not to win you back, but to learn how we can do better. Your candid feedback genuinely helps."

The Decision (10 minutes)

• "Can you walk me through the decision to leave? What triggered it?"
• "Was there a specific moment when you knew it wasn't working?"
• "How long were you considering leaving before you actually did?"
• "Did you evaluate alternatives? Which ones?"

The Experience (10 minutes)

• "Think back to when you first started using us. What were your expectations?"
• "When did reality start differing from expectations?"
• "What was the most frustrating part of your experience?"
• "Was there anything we did well that you'll miss?"

What Would Have Changed Things (5 minutes)

• "If you could go back in time and we could do one thing differently, what would it be?"
• "What would we have needed to do to keep you?"
• "Is there any scenario where you'd come back?"

Closing (3 minutes)

• "Anything else I should know?"
• "I really appreciate your honesty—this helps us improve."

Script 4: Jobs-to-Be-Done Interview Template

Use when: You want to understand the real motivation behind why customers "hire" your product.

This script is based on the Jobs-to-Be-Done framework developed by Clayton Christensen at Harvard Business School.

The Timeline (15 minutes)

Walk backwards through their purchase decision:

• "Take me back to when you first realized you needed a solution like this. What was happening?"
• "What were you doing before? How were you getting by?"
• "What pushed you to actively look for something new?"
• "What other options did you consider?"
• "Why did you choose us over the alternatives?"
• "What almost held you back from switching?"

The Forces (10 minutes)

Understand the push and pull dynamics:

• Push: "What was so bad about your old way that made you want to change?"
• Pull: "What was so appealing about the new solution?"
• Anxiety: "What concerns did you have about making the switch?"
• Habit: "What did you like about your old way that was hard to give up?"

The Outcome (5 minutes)

• "What does success look like for you?"
• "How will you know if this was a good decision?"
• "Has your definition of success changed since you started using us?"

Script 5: Feature Prioritization Interview Template

Use when: You're deciding what to build next and need customer input.

Opening (2 minutes)

"We're planning our roadmap and want to make sure we're building what matters most to you. This isn't a feature request session—I want to understand your workflows and challenges so we can make smart prioritization decisions."

Current Workflow (10 minutes)

• "Walk me through how you use [product] on a typical day."
• "What do you do first? Then what?"
• "Where do you get stuck or slowed down?"
• "What workarounds have you created?"

Prioritization Exercise (10 minutes)

Present 3-5 potential features or improvements:

• "If you could only have one of these, which would you choose? Why?"
• "What would change for you if we built this?"
• "How much time would this save you?"
• "Would this change how you think about [product]?"

The Dream State (5 minutes)

• "Imagine [product] in two years and it's perfect for you. What does it do?"
• "What would make you recommend us to everyone you know?"

Closing (3 minutes)

• "Anything we're not talking about that we should be?"

Common Interview Mistakes to Avoid

1. Leading the Witness

❌ "Don't you think it would be better if we added X?" ✅ "How do you currently handle this situation?"

2. Asking About Future Behavior

Research from Stanford's Persuasive Technology Lab shows that people are terrible at predicting their own behavior.

❌ "Would you use this feature?" ✅ "Tell me about the last time you faced this problem."

3. Accepting Vague Answers

❌ Customer: "That would be useful." You: "Great!" (moving on)

✅ Customer: "That would be useful." You: "Tell me more. What specifically would you use it for?"

4. Selling Instead of Listening

If you're talking more than 30% of the time, you're doing it wrong. The best interviews feel like the customer is telling a story while you listen intently.

How AI Can Transform Your Interview Process

Conducting interviews is only half the battle. The real challenge is extracting insights across dozens of conversations.

AI-powered tools like Pelin can:

• Transcribe and analyze interviews automatically
• Surface patterns across multiple conversations
• Connect interview insights to support tickets, reviews, and feedback
• Generate summaries stakeholders can actually read
• Track themes over time as your product evolves

Instead of spending hours on post-interview synthesis, you can focus on asking better questions and building deeper customer relationships.

Making Interview Insights Actionable

Here's the uncomfortable truth: most customer interviews end up in graveyards—buried in Notion pages nobody revisits, lost in folders, or trapped in someone's head.

To make interviews valuable:

1. Synthesize immediately: Write up key insights within 24 hours
2. Tag consistently: Use a consistent taxonomy across interviews
3. Connect to decisions: Link insights directly to roadmap items
4. Share broadly: Make insights accessible to sales, support, and leadership
5. Revisit regularly: Schedule monthly reviews of accumulated learnings

Your Next Steps

Pick one interview from your calendar this week and try one of these scripts. Don't wait for perfection—you'll learn more from one real conversation than from endless planning.

Start with the Discovery Interview Template if you're exploring new opportunities, or the Feature Prioritization Template if you're planning a roadmap.

The best product teams aren't just collecting feedback—they're building systematic approaches to understanding customers. That starts with better conversations.

Ready to turn customer conversations into product decisions? Pelin helps product teams analyze feedback from interviews, support tickets, and reviews—all in one place.