Skip to content
Product validation

Customer Interviews Without Leading People Toward the Answer You Want

Editorial owner: Yumea · Published and reviewed on · Next review

A useful customer interview does not ask whether an idea is good. It reconstructs a past situation: trigger, behavior, alternative, cost, decision and outcome. Compliments and future intentions are easy. Evidence appears in what a person already tried, paid for, abandoned or worked around.

Solution bias

When a founder presents the product too early, the participant becomes polite, imaginative or focused on interface criticism. The conversation no longer reveals problem priority.

Start from the person's world, not the mockup.

Behavioral questions

  • Tell me about the last time this happened.
  • What did you do next?
  • Who was involved?
  • What did it cost in time or money?
  • Which tool or workaround did you use?
  • What prevented a change?
  • Which consequence mattered most?
  • When did the problem become urgent?

Ask for examples and documents only when they can be shared legitimately.

Questions to avoid

  • Would you use our product?
  • Is this a good idea?
  • How much would you pay for an imaginary feature?
  • This would save time, right?
  • Do you prefer A or our solution?

Replace an intention with commitment: try a manual service, provide a case, make an introduction, reserve a date or pay for a pilot.

Separate notes and interpretation

During the interview, record exact words and behavior. Afterwards, separate direct facts, inferences, testable hypotheses, contradictions and the next proof.

Do not turn one quote into a segment truth.

Sample and saturation

Start with five people in a comparable situation. Look for patterns and differences. When new interviews stop revealing new mechanisms, test an offer or behavior.

Saturation does not prove market size. It indicates that the problem model may be stable enough for the next experiment.

Example

Leading: “Would an automatic summary save you time?”

Behavioral: “After your last important call, how did next actions enter the CRM?”

The second may reveal that the real issue is assignment, recording consent or follow-up discipline rather than summarization.

A 15-minute debrief

  1. Which behavior was observed?
  2. Which alternative already exists?
  3. Which cost or risk is real?
  4. Which assumption became weaker?
  5. Which concrete commitment can be requested next?

FAQ

Should interviews be recorded?

Only with clear consent, purpose, protection and retention. Structured notes may be enough.

How many interviews are required?

There is no magic number. Five homogeneous interviews may reveal a mechanism; behavior and commitment strengthen the evidence afterwards.

When should the prototype be shown?

After understanding the situation, to observe use and confusion. Do not let the demo replace discovery.

Next step

Use the Non-Leading Interview Guide in five conversations and end each with a concrete next proof. For a script review, email contact@yumea.fr with “INTERVIEWS” in the subject.

Original reference frameworks

These links provide access to public reference frameworks. The episode audit remains internal and is not independent evidence for each claim. Also consult the limitations and references in the article.

A human review of your brief

Prepare a summary, review it and email contact@yumea.fr. No response time is guaranteed at this stage. The Tsuno CRM connection remains subject to validation; no automatic transfer is active.

contact@yumea.fr