Customer discovery

Customer Discovery is the first phase of the Customer Development process, focused on validating that a proposed product addresses a real problem that customers care about solving. Through direct conversations with potential customers, teams test their assumptions about who the customer is, what problem they face, and whether the proposed solution would be valuable. It's about finding problem-solution fit before building.

Why it matters

Building products based on untested assumptions wastes resources. Customer Discovery matters because it tests those assumptions early, when changing direction is cheap:

Validates the problem exists. Do customers actually have the problem you're solving?

Confirms they want a solution. Having a problem doesn't mean they want to solve it now or that they'd pay for a solution.

Clarifies who the customer is. Early assumptions about target customers are often wrong.

Reveals competitive alternatives. How do customers currently solve this problem? What would your solution need to beat?

Surfaces unexpected insights. Conversations reveal things you wouldn't have thought to ask about.

The customer discovery process

Define hypotheses

Before talking to customers, explicitly state what you believe:

Customer hypothesis. Who has this problem? What segments? What characteristics?

Problem hypothesis. What problem do they have? How painful is it? How frequently do they encounter it?

Solution hypothesis. Would this solution address the problem? What would they need it to do?

These are hypotheses, not facts - they're meant to be tested and updated.

Find customers to talk to

Identify potential customers who match your hypothesis:

Aim for people who might actually have the problem, not just people who are easy to reach.

Conduct interviews

Discovery interviews explore the customer's reality:

Ask about their situation. What do they do? What challenges do they face?

Explore the problem. Have they experienced this problem? How often? How painful?

Understand current behavior. How do they handle this today? What have they tried?

Test solution concepts. Would they want something like this? What would it need to do?

Focus on understanding their reality, not pitching your solution.

Synthesize and update

After interviews, assess what you learned:

Update your understanding and iterate.

Interview best practices

Talk about their life, not your idea. The goal is understanding their reality, not getting validation for your concept.

Ask about specific past behavior. "Tell me about the last time you faced this" reveals more than "Would you want this?"

Avoid leading questions. "Don't you hate it when..." invites agreement. "How do you feel about..." invites truth.

Listen more than talk. The customer should be talking 70%+ of the time.

Dig into emotions. When they express frustration, interest, or excitement, explore what's behind it.

Capture what they do, not just what they say. Stated preferences often differ from actual behavior.

The mom test

Rob Fitzpatrick's "Mom Test" offers guidance for discovery conversations:

Bad questions (your mom would lie to you):

Good questions (your mom couldn't lie about):

Good questions get at behavior and reality, not hypothetical preferences.

How many conversations?

There's no magic number, but patterns emerge:

5-10 conversations. Initial patterns start appearing. Good for very early exploration.

15-25 conversations. Clearer patterns emerge. Sufficient for most discovery phases.

50+ conversations. High confidence. Appropriate for major strategic decisions.

Stop when you hear the same things repeatedly and new conversations add little new information.

Signs of problem-solution fit

Customer Discovery suggests fit when:

One enthusiastic customer isn't validation. Patterns across many customers are.

Signs you need to pivot

Pivot signals during Customer Discovery:

Pivots are expected. Customer Discovery is designed to surface them early.

Customer discovery vs. selling

Customer Discovery and selling are different activities:

Discovery asks: "Do you have this problem? How do you solve it today? Would you want something like this?"

Selling asks: "Will you buy this? Let me show you why you should."

Mixing them produces misleading results. Sales conversations trigger different responses than discovery conversations.

Tools like Klero extend Customer Discovery beyond the startup phase by maintaining ongoing customer insight. Discovery shouldn't end when you launch - it should continue as your market and customers evolve.