A customer interview template structures your discovery conversations so you actually extract insights—not just transcribe complaints. This guide walks through the framework's core components, question sequencing, and how to translate raw interview notes into actionable product, messaging, and positioning decisions.
A working customer interview framework separates questions into three sequential layers. The first layer gathers context: who the interviewee is, their role, their environment, and how they currently solve the problem you're investigating. This isn't small talk—it anchors everything that follows. The second layer explores the problem itself: when it surfaces, what triggers it, how severe it is, what they've tried, and where existing solutions fall short. The third layer evaluates your proposed solution or tests assumptions about what matters. Each layer builds on the last. If you skip context and jump to solution validation, you lose the narrative thread that explains why someone cares. In a Canadian customer interview template, add a context question about geography or market if your product has regional variability—buying behaviour in Montreal differs from Calgary, and compliance or language requirements shift across provinces.
Start with role, company size, and how long they've faced the problem. Ask what their day looks like and where this problem fits into their broader workflow. For example: 'Walk me through a typical week—when does [problem] come up?' or 'What tools do you currently use to handle this?' These questions establish whether the interviewee is actually in your target segment. If you're building for small business owners and the person delegates the task entirely, their answers will mislead you. Context questions also surface the economic and organizational reality: budget authority, decision cycles, whether they're bilingual if you're targeting Quebec, or if they operate seasonally. Capture these details in a dedicated section of your template so you can filter interviews later by segment. Don't treat context as filler—it's the foundation for interpreting every answer that follows.
The core of any customer interview example is the problem exploration section, and the trick is specificity. Instead of 'How often do you experience this problem?', ask 'Tell me about the last time this happened.' Concrete stories reveal actual behaviour; hypotheticals reveal aspiration. Probe for trigger events: 'What caused it that time?' Ask about impact: 'What did it cost you—time, money, frustration?' and 'What did you do next?' If they mention a workaround, dig into it: 'How long have you used that approach? What's annoying about it?' Workarounds are gold—they show the problem is real enough to justify effort, and they expose the gaps your solution must fill. Avoid binary or leading questions like 'Would you pay for a tool that does X?' That contaminated data is useless. Stay in the past tense, stay in stories, and let the interviewee do most of the talking.
If you're testing a concept or prototype, frame it as an artifact for feedback, not a pitch. Say 'I'm going to show you something we're working on—tell me what's confusing or what's missing' rather than 'Here's our amazing solution.' Walk them through the idea, then ask: 'Does this solve the problem you described earlier? What part does, and what part doesn't?' or 'If this existed, where in your workflow would you use it?' Watch for disconnect between stated interest and behavioural cues. If they say 'I'd definitely use this' but can't articulate a specific scenario or next step, that's a red flag. A strong signal is when they start suggesting integrations or asking about pricing unbidden—that means they've mentally slotted it into their world. In your customer interview framework, include a checklist of solution assumptions to test so you cover all critical hypotheses across interviews, not just the ones that come up organically.
Word choice determines data quality. Replace 'Do you think…?' with 'What do you think about…?' to avoid yes/no traps. Replace 'Would you…?' with 'Have you ever…?' to shift from hypothetical to actual. Use 'Why?' and 'Tell me more' relentlessly—silence is a tool, let the interviewee fill it. Avoid compound questions: 'What's frustrating about this and would you pay to fix it?' is two questions; ask them separately. If you're conducting a customer interview in Canada and your audience spans English and French, prepare a bilingual template or at minimum have key questions reviewed by a native French speaker to ensure tone and formality align. Direct translation often sounds unnatural or changes nuance. During the interview itself, if the interviewee gives a vague answer, reframe: 'Can you give me an example of that?' Concrete examples are the entire point—everything else is noise.
The template doesn't end when the call does. Record the session with permission, but don't rely on transcripts alone—tag while listening. Create a simple tagging taxonomy: problem severity, workaround sophistication, willingness to pay, feature requests, objections. As you review, pull direct quotes into a shared document organized by theme, not by interviewee. This lets you see patterns: if eight of ten people mention the same friction point using different words, that's a priority. Map insights to jobs-to-be-done: what is the customer hiring your product to accomplish? Use that framing to guide product and messaging decisions. In Canada, be mindful of privacy laws when storing recordings—PIPEDA requires consent and reasonable safeguards. If you're interviewing across provinces, a simple consent script at the start of each interview covers you. The output of this process isn't a pile of transcripts; it's a prioritized list of problems, validated assumptions, and direct language you can deploy in copy, landing pages, and feature specs.
Most effective interviews run 30 to 45 minutes. Shorter than 30 minutes rarely allows enough depth for useful problem exploration. Longer than 45 minutes risks fatigue and diminishing returns—the sharpest insights usually surface in the first half-hour. If you're testing a prototype or conducting solution validation, budget closer to 45 minutes. Context and problem layers can often be covered in 20 minutes if the interviewee is articulate and you avoid tangents.
Send a brief agenda or themes, but not the exact questions. If interviewees see your questions ahead of time, they rehearse answers and you lose spontaneity. A short note like 'We'll discuss how you currently handle X and explore some new ideas' sets expectations without scripting responses. The goal is a conversation, not a survey read aloud. Providing too much detail also anchors them to your assumptions rather than letting their reality emerge.
Patterns typically emerge after five to eight interviews within a single segment. If you're seeing the same problems and language repeated by interview six, you've likely reached saturation for that persona. If answers remain scattered, either your segment definition is too broad or your questions aren't specific enough. For multiple segments—say, small business owners versus enterprise buyers—you need five to eight per segment. Quality beats quantity: three deep, well-conducted interviews outperform fifteen shallow ones.
A customer interview is qualitative and exploratory—you're probing for stories, context, and underlying motivations through open-ended conversation. A survey is quantitative and confirmatory—you're measuring how widespread a known insight is across a population. Interviews help you discover what questions to ask; surveys help you validate how many people share a specific answer. Use interviews early in product development or positioning work, then surveys to test hypotheses at scale. Mixing the two—asking yes/no questions in an interview or open-ended essays in a survey—wastes the strengths of both methods.
Prepare both English and French versions if you're targeting Quebec or bilingual markets, and ensure the French isn't a literal translation—idiomatic phrasing matters for rapport. Offer interviewees the choice of language upfront. If you're not fluent, hire a bilingual moderator or translator rather than relying on machine translation during the conversation. Tone and formality differ: French-Canadian business culture often expects slightly more formal address than English-Canadian, especially in initial outreach. Culturally, be aware that direct questions about money or failure can land differently across regions—frame them as process questions rather than personal judgments.
Acknowledge their input politely, then redirect: 'That's a great point—I'll come back to it at the end. First, I want to understand how you currently handle this.' If they keep derailing, it often means they're not invested in the problem you're exploring, which is itself useful data. At the end of the interview, leave time for their questions—it builds goodwill and sometimes surfaces insights you missed. If they're pitching you on a feature, ask why they want it: 'What would that let you do that you can't do now?' to get at the underlying job rather than the surface request.