How To Run Customer Discovery Interviews: Scripts, Mistakes, And Metrics

Customer Discovery The process of interviewing or observing prospective customers to understand problems, purchasing behavior, and unmet needs. Interviews are the most common discovery technique—when structured correctly they reveal motivations, constraints, and real-world behaviors that surveys or feature tests miss.

Running effective discovery interviews requires preparation, neutral questioning, and rigorous synthesis. The goal is to surface reproducible evidence—frequency of a problem, triggers, current workarounds, and indications of willingness to change—rather than to collect polite approvals for your idea.

Preparing For Interviews

Begin with a concise hypothesis and a list of the people who can test it. For logistics products, include operators as well as buyers: operations managers know constraints, but line workers reveal execution friction.

• Hypothesis Statement: One sentence linking customer, problem, and expected outcome (e.g., "Warehouse supervisors experience >2 hours/day lost due to inaccurate slotting during peaks").
• Interview Targets: Identify roles and attributes (e.g., annual throughput, number of SKUs, B2B vs B2C customers).
• Consent & Recording: Request permission to record; if refused, take detailed notes immediately after.

Designing Questions And A Script

Use a semi-structured script: start with contextual warm-up, move to problem-focused questions, and close with decision and budget questions. Avoid leading or hypothetical questions; favor concrete, past-tense prompts.

• Warm-Up: "Tell me about your role and a typical day on the dock."
• Problem: "Can you walk me through the last time you had a slotting error? What happened and how did you fix it?"
• Frequency & Impact: "How often does that happen in a week/month, and what does it cost you in time or money?"
• Current Workarounds: "What do you do now to avoid or correct that issue?"
• Decision Signals: "If a tool could reduce that time by half, who approves that purchase and what budget line would it come from?"

Conducting The Interview

Start with a brief explanation of the session and confirm recording. Keep questions open. When answers are vague, request a specific example. Use silence intentionally—people often fill gaps with useful detail.

• Ask For Examples: "When was the last time this cost you more than an hour? What happened?"
• Watch For Pain Signals: Repeated phrases like "we always..." or "we can't afford..." indicate persistent issues.
• Probe Budget & Authority: Identify who signs off and the typical procurement timeline.

Synthesis And Metrics To Track

After interviews, synthesize using a simple rubric: frequency of mention, severity (operational impact), and purchaseability (budget & authority). Track metrics that convert qualitative answers into decision inputs.

• Interview Count: Number of conversations per segment (target 10–20 to reach saturation).
• Problem Prevalence: Percentage of interviews reporting the problem.
• Severity Score: A simple scale (e.g., 1–5) for time/cost impact, averaged across respondents.
• Purchase Signals: Number of interviews indicating existing budget, authority, or documented procurement processes.

Common Interview Mistakes And Fixes

Leading questions and conflating wishful answers with demand are common. If a prospect says they "would" buy, follow up: ask when they last paid for a similar solution or what budget line it would come from. If answers are optimistic, look for measurable signals like pilot commitments or timeline constraints.

• Leading Questions: Replace "Would you use X?" with "How do you solve X today?"
• Small Sample Bias: Diversify recruitment across company size, region, and role to avoid skewed findings.
• No Follow-Up: If someone expresses strong interest, ask for a reference, pilot, or budget conversation to convert interest into action.

Example Interview Script For A Logistics Tool

Use a short 10–12 question script for a 30–45 minute call. Start with role and context, then timeline-based problem questions, and close with procurement and next-step questions. Example closing prompts: "Who else on your team should I speak with?" and "If we built a simple prototype, would you be willing to pilot it next quarter?"

Scaling Discovery In Organizations

To scale, train sales and customer success teams to run short discovery touches and feed responses into a central repository. Use tagging for themes (e.g., "slotting errors," "returns processing") so product managers can prioritize based on prevalence and commercial signals.

In short, the Customer Discovery interview process combines targeted questions, observation, and a synthesis framework to turn anecdote into actionable evidence. Properly executed, interviews shorten time to product-market fit and align engineering, sales, and operations around real customer needs.