Customer Interview Script Template

What This Template Is For

Talking to users is the single highest-signal activity a product manager can do. Yet most PMs either skip interviews entirely or run them without structure, ending up with a pleasant conversation and zero actionable insights. The difference between a useful interview and a wasted 30 minutes is preparation.

This template provides a ready-to-use interview script organized into five phases: rapport building, current workflow exploration, pain point discovery, jobs-to-be-done questioning, and solution exploration. Each phase has a purpose, a time allocation, and specific questions designed to surface honest, detailed responses. The script avoids leading questions that confirm what you already believe and focuses on what the user actually does today, not what they think they might want.

For the broader methodology of running a discovery program (when to interview, how to recruit participants, how to synthesize across multiple interviews), see the Product Discovery Handbook. If you need to document who you are building for after your interviews, the User Persona Template gives you a structured format for turning interview insights into shareable personas.

When to Use This Template

• At the start of a new initiative. Before writing a PRD or drawing wireframes, talk to 5-8 users from your target segment. These conversations should shape the problem definition, not validate a solution you have already designed.
• When you inherit a product area. New to a team or a domain? Customer interviews are the fastest way to build real understanding. You will learn more in five interviews than in five weeks of reading documentation.
• When quantitative data shows a problem but not a cause. Your funnel shows a 40% drop-off at step 3 of onboarding. Analytics tells you where. Interviews tell you why.
• During continuous discovery. Schedule 2-3 interviews per week as an ongoing habit, not a one-time research project. The best product teams treat interviews like a regular practice.
• Before a major pricing or packaging change. Understand how users perceive the value they get today before you change what they pay for it.
• When stakeholders disagree about user needs. Replace opinion-based debates with direct user evidence. Five interview transcripts settle more arguments than fifty meeting hours.

How to Use This Template

1. Define your research question. Before scheduling any interview, write down the one question you need to answer. "How do marketing teams plan campaigns today?" is a good research question. "Would users pay for our new feature?" is not (users cannot reliably predict their own purchasing behavior).
2. Recruit 5-8 participants. Aim for people who match your target segment. Recruit from your existing user base, prospect lists, or communities where your target users spend time. Offer a reasonable incentive ($50-100 gift card for a 30-minute call).
3. Customize the script. Copy this template and adapt the questions to your specific domain. Keep the structure (five phases) but replace the example questions with ones relevant to your product and research question.
4. Run the interview. Follow the script loosely, not rigidly. The best insights come from follow-up questions like "Tell me more about that" and "Can you walk me through the last time you did that?" Let the user talk 80% of the time.
5. Complete the synthesis card immediately after. Fill in the post-interview synthesis card within 30 minutes of ending the call. Your memory degrades fast. Capture key quotes, surprises, and patterns while they are fresh.

The Template

Pre-Interview Setup

Complete this section before the call.

Phase 1: Introduction and Rapport (3 minutes)

Goal. Make the interviewee comfortable. Set expectations for the conversation. Get recording consent.

Script:

"Hi [Name], thanks for taking the time to talk with me. I am [Your Name], a product manager at [Company]. I am researching how teams like yours handle [topic area]. There are no right or wrong answers here. I am genuinely trying to understand your experience, not sell you anything.

>

I would like to record this conversation so I can focus on listening instead of note-taking. The recording stays internal. Is that okay with you?

>

This should take about 25-30 minutes. I have some questions prepared, but feel free to take the conversation wherever it is useful for you."

Warm-up questions:

• Can you give me a quick overview of your role and what your team is responsible for?
• How long have you been in this role?

Phase 2: Current Workflow (7 minutes)

Goal. Understand how the user handles the problem area today. Map their existing process before looking for pain points.

• Walk me through how you currently [do the activity related to your research question]. Start from the beginning.
• What tools or systems do you use for this?
• How often do you do this? Daily, weekly, ad hoc?
• Who else is involved in this process?
• What does a typical [week/sprint/cycle] look like for this workflow?
• How has this process changed over the past year?

Follow-up prompts:

• "You mentioned [specific step]. Can you tell me more about what happens there?"
• "What does that look like in practice? Can you show me or describe a recent example?"

Phase 3: Pain Points and Frustrations (7 minutes)

Goal. Surface the specific problems, inefficiencies, and frustrations in their current workflow. Get concrete examples, not abstract complaints.

• What is the most frustrating part of [this process]?
• Can you tell me about a time in the last month when this did not go well? What happened?
• Where do you spend the most time on things that feel like wasted effort?
• What workarounds have you built to deal with the limitations of your current tools?
• If you could wave a magic wand and fix one thing about this process, what would it be?
• What have you tried in the past to solve this problem? What worked and what did not?

Follow-up prompts:

• "How often does that happen?"
• "What is the impact when that goes wrong? What does it cost you in time, money, or stress?"
• "How do you deal with it today?"

Phase 4: Jobs-to-Be-Done (7 minutes)

Goal. Understand the underlying goals and motivations behind the user's behavior. Frame their needs in terms of outcomes, not features.

• When you [do this activity], what are you ultimately trying to achieve?
• How do you measure success for this process? What does "good" look like?
• Who benefits when this goes well? Who suffers when it does not?
• Think about the last time you switched to a new tool or process for this. What triggered that switch?
• What were you hoping the new [tool/process] would do for you that the old one could not?
• If this process took zero effort, what would you do with the time you saved?

Follow-up prompts:

• "Why is that important to you specifically?"
• "What happens if you do not achieve that?"

Phase 5: Solution Exploration (5 minutes)

Goal. Explore reactions to potential solutions without leading the user. Do not pitch your product. Present concepts broadly and listen for what resonates.

• If a tool existed that [describe the capability broadly], how would that fit into your current workflow?
• What would make you skeptical about a new tool in this space?
• What would you need to see before you trusted it with [this process]?
• How much would you expect to pay for something that solved [the problem they described]?
• Who else at your company would need to approve using a new tool for this?

Important. Do not describe your product's features. Describe capabilities in generic terms and let the user react. If they ask "Does your product do X?", say "We are exploring that. Tell me more about why X matters to you."

Phase 6: Wrap-Up (1 minute)

"Thank you so much for your time. This has been very helpful. Is there anything else about [topic] that I did not ask about but you think I should know?

>

Would it be okay if I followed up with a short email if I have any clarifying questions?

>

If we build something related to what we discussed, would you be interested in seeing an early version and giving feedback?"

Post-Interview Synthesis Card

Complete within 30 minutes of the interview ending.

Filled Example: Marketing Team Campaign Planning

Context. A PM at a marketing automation SaaS company is researching how mid-market marketing teams (10-30 person teams) plan and coordinate multi-channel campaigns. The goal is to identify opportunities for a new campaign planning feature.

Pre-Interview Setup (Example)

Interview Notes (Example, Abbreviated)

Current Workflow (Phase 2):

Rachel described a quarterly planning process. Her team of 14 plans 6-8 campaigns per quarter. Campaign planning starts in a Google Doc that lives in a shared Drive folder. Each campaign has a brief, a channel plan, a content calendar, and a budget sheet. The brief template was created by a former team member three years ago. Different team members own different channels (email, paid, content, social). Coordination happens in a Monday morning "campaign sync" meeting and a Slack channel.

Pain Points (Phase 3):

"The brief is always done, but nobody reads it. People just ask me in Slack what the campaign goals are. Every single time." She spends 3-4 hours per week answering questions that are already documented somewhere. The biggest frustration: no single place to see all campaigns and their status. She has a personal spreadsheet that tracks launch dates, owners, and status. "I update it manually every Monday morning. It takes 45 minutes and it is wrong by Wednesday."

When a campaign slips its launch date, there is no cascading update to dependent channels. The paid team ran ads for a webinar that the content team postponed by two weeks. "We burned $4K in ad spend pointing to a registration page for a webinar that was not happening."

JTBD (Phase 4):

"When I am planning a quarter's worth of campaigns, I want to see all the moving pieces in one view so I can spot conflicts and resource gaps before they become emergencies." Her success metric is launching campaigns on time with all channels coordinated. She switched from Trello to Monday.com six months ago because she needed Gantt-style timeline views. Monday.com is "better for task management but still not built for campaign planning."

Solution Exploration (Phase 5):

When asked about a tool that could show all campaigns on a timeline with dependencies: "That is literally what I try to build in Monday every quarter. But the dependencies break when dates shift and I end up back in my spreadsheet." She would pay $200-300/month for a tool that replaced her spreadsheet and the Monday morning meeting. Her VP of Marketing would need to approve.

Post-Interview Synthesis Card (Example)

Key Takeaways

• Write down your research question before scheduling a single interview. Every question in the script should serve that research question.
• The five-phase structure (rapport, workflow, pain points, JTBD, solution exploration) prevents the two most common interview mistakes: jumping to solutions too early and asking leading questions.
• Let the user talk 80% of the time. Your job is to listen, not to present. The best follow-up question is almost always "Tell me more about that."
• Complete the synthesis card within 30 minutes. Memory fades faster than you think, and reconstructing an interview from notes alone loses the nuance.
• Five good interviews surface 80% of the patterns for a segment. You do not need 50 interviews to start making decisions. You need 5 deep ones.
• Never describe your product's features during Phase 5. Describe capabilities generically and listen for what resonates. The moment you pitch, the user stops giving you honest feedback and starts being polite.

About This Template

Created by: Tim Adair

Last Updated: 2/19/2026

Version: 1.0.0

License: Free for personal and commercial use