SM Small Proof Studio
Customer Discovery

Run a Customer Interview Without Leading

Small Proof Studio · Updated 2026-07-19 · 4 min read
Run a Customer Interview Without Leading
In shortRun a non-leading customer interview by defining one decision, recruiting people with recent relevant experience, and asking them to reconstruct a specific event. Use neutral prompts about triggers, actions, tools, alternatives, constraints, consequences, and what happened next. Avoid describing your solution, assuming the problem, or asking whether they would buy an imagined product. Obtain appropriate consent, protect private information, and separate observations from interpretation after the call. Compare repeated behaviors and counterexamples without turning a small sample into market percentages, then choose the next test or change in direction.
Contents

Ask for a recent story before offering a solution

Run a customer interview without leading by choosing one learning question, asking about a specific recent event, and following the person's actions, alternatives, constraints, and decisions in their own words. Keep your idea and preferred answer out of the question. End by summarizing what you heard and checking your understanding, not by asking whether they like the startup.

An interview is evidence about this participant's experience. It is not a representative survey, a product order, or proof of a market. Five enthusiastic compliments remain compliments, even when entered into a spreadsheet wearing currency formatting.

Define the decision the interview should inform

Write the risky assumption and the decision attached to it right now. For example: Do people currently spend meaningful effort reconciling these records, and should we test a simpler workflow? Avoid goals such as “validate the product,” which quietly asks the conversation to return one approved conclusion.

Choose participants who have encountered the situation, not only friends who understand why the idea sounds exciting. Define relevant experience without targeting or excluding people unlawfully or unethically.

Explain who you are, the purpose, expected length, note or recording method, privacy, compensation if any, and how the person can decline or stop. Obtain appropriate consent. Do not collect sensitive personal, health, financial, employment, or confidential business information without a justified, approved plan.

Browse customer discovery for more evidence-led research setup.

Build a neutral question path

Start broad: “Tell me about the last time you had to….” Then ask:

Ask “how” and “what” more often than “would.” Future intentions are easy to state and hard to interpret. A recent event gives the participant something concrete to reconstruct.

Avoid loading the problem into the question: “How frustrating is the slow process?” assumes it is slow and frustrating. Ask “How would you describe the process?” and follow the language they choose.

Follow evidence without conducting a cross-examination

When a statement is abstract, request an example: “Can you walk me through the last instance?” Ask what the person actually used, paid, delayed, abandoned, or asked someone else to do.

Use short neutral prompts—“What happened then?” or “Tell me more”—and allow silence. Do not rescue every pause with a miniature sales pitch. The participant is thinking, not buffering.

When the story contradicts your assumption, explore it with the same curiosity. Do not debate, teach the person the correct problem, or keep reformulating until they agree.

Keep the concept test separate

If you show an idea, label the transition. Present the smallest neutral description or prototype needed for the next question, then ask the participant to interpret or use it without a feature tour.

Observe what they expect, where they hesitate, and what they do. “Would you use this?” invites politeness and imagination. A task with a prototype reveals whether the proposed flow makes sense under test conditions.

Use our paper-prototype guide for a low-cost concept session, and visit prototype workshop for materials and test boundaries.

Debrief facts before themes

Immediately after, separate observed or said, interpretation, and decision. Preserve short exact phrases only with consent and appropriate handling. Remove unnecessary identifying detail.

Compare interviews for repeated behaviors, constraints, alternatives, and consequences, but retain counterexamples. Do not convert frequency in a small convenience sample into a market percentage.

Write what would change your mind and choose the next test. That may be another participant segment, a workflow observation, a pricing experiment conducted ethically, or a decision to stop.

The interview has succeeded when it makes the next decision better, including the inconvenient decision that the problem is smaller, different, or already well served. Discovery is not a courtroom where the idea wins; it is a workshop where the expensive mistake is invited to identify itself early.

FAQ

What is a good first customer interview question?

Ask for a recent specific story: “Tell me about the last time you had to…” followed by the situation you are studying in neutral terms. Then ask what triggered it, what happened first, and what happened next. This grounds the conversation in behavior rather than broad opinion or future intention. Avoid naming your solution or describing the experience as difficult, slow, expensive, or frustrating before the participant does.

What makes a customer interview question leading?

A leading question contains or rewards the preferred answer, assumes a problem, praises the concept, or offers only favorable choices. “How frustrating is this process?” assumes frustration; “Would this convenient feature help?” advertises the response. Ask the participant to describe the process, recent event, alternatives, and consequences in their own language. Neutral follow-ups such as “Can you give an example?” reveal more than a reformulated sales claim.

Should I pitch my startup during a customer interview?

Keep problem discovery separate from a concept test. Learn the participant's current behavior before showing the idea. If a concept must be tested, announce the transition, present only enough neutral material for the task, and observe use without a feature tour. Pitching early teaches the participant your vocabulary and invites politeness. It also makes later agreement difficult to distinguish from genuine experience or simple kindness toward an enthusiastic founder.

How many customer interviews are enough?

There is no universal number that guarantees a conclusion. Sample relevance, decision risk, segment variation, interview quality, and the cost of being wrong all matter. Continue until the evidence is sufficient for the next limited decision and important counterexamples are understood, then test behavior through another method. Do not report small convenience-sample frequencies as market percentages or imply statistical representation the research design does not provide.

How should I take notes in a customer interview?

With consent, record brief exact phrases, event sequence, actions, alternatives, constraints, and consequences. Mark direct statements separately from your interpretation and remove unnecessary identifying detail. If recording audio or video, explain storage, access, use, retention, and the right to decline under applicable rules. Debrief immediately into observed or said, interpretation, open question, and next decision. A thematic summary should preserve counterexamples rather than sanding every interview into agreement.