1 Customer Problems and Discovery

Turn assumptions into evidence

Startups begin with assumptions about who has a problem, what those people need, and how they currently cope. Customer discovery investigates potential customers’ situations and behavior to replace assumptions with evidence before a startup commits heavily to a solution. Its purpose is to define a specific, meaningful problem—not to persuade people to like an idea.

Choose a customer segment

Choose a focused customer segment with relevant needs or circumstances in common. A narrow, testable description is more useful than a broad label such as “small businesses.” For example, “independent neighborhood cafés whose owners prepare staff schedules themselves” identifies a more specific group and suggests whom to interview.

Describe the segment using characteristics that help explain the need or determine how to reach the group:

• Context: Where and when does the problem occur?

• Role: Who experiences the problem, uses a solution, approves it, and pays for it?

• Behavior: What do people currently do when the problem arises?

• Relevant traits: Which demographic, organizational, or geographic characteristics help explain the need or determine how to reach people?

In an organization, the user, decision-maker, and buyer may be different people. Investigate each role rather than assuming that they share the same priorities.

Investigate jobs, pains, and outcomes

Investigate what people are trying to accomplish, the circumstances in which they do it, and what makes it difficult. A job to be done can be functional, such as preparing next week’s staff schedule; emotional, such as feeling confident that shifts are covered; or social, such as being seen as a fair manager. Pains may include obstacles, delays, uncertainty, risk, and frustration. Desired outcomes describe the results people want and are not necessarily just the opposites of their pains.

Ask about actual experiences rather than hypothetical approval. Questions such as “Tell me about the last time you made the schedule” and “What happened when someone called in sick?” invite concrete details. Follow up by asking what the person did, how often the situation happens, what consequences followed, and what alternatives they tried.

Avoid leading questions such as “Would you use an app that fixes this?” A positive answer is easy to give and does not establish that the problem is important. Listen for evidence of effort and consequences, including repeated workarounds, time or money spent, missed opportunities, complaints, and risks. Record customers’ words and examples separately from your interpretations.

Interviews help reveal experiences. Surveys and market data can help estimate how common a pattern may be.

Describe the problem without prescribing a solution

A useful problem statement specifies who is affected, what they are trying to do, and what difficulty or consequence they face, without prescribing a particular product. For example:

Independent café owners who create staff schedules manually spend several hours each week resolving shift conflicts, making it difficult to keep schedules accurate when availability changes.

This description identifies a group, a task, and a pain while leaving room to investigate different solutions. By contrast, “cafés need scheduling software” jumps to a product and provides less information about the underlying difficulty.

Assess whether the problem is worth solving

Compare candidate problems using several considerations:

• Importance: How serious are the consequences when the problem occurs?

• Frequency: How often does it happen, and how recently did it happen?

• Current response: Do people already spend time, money, or effort addressing it?

• Reachability: Can the business identify and access the affected people?

• Consistency: Does the same problem appear across multiple people in the proposed segment?

A compelling story from one person is a clue, not proof of a widespread need. Look for recurring patterns across interviews and compare them with market information. Keep the customer profile independent of the proposed solution; otherwise, it may be easy to notice only the needs the idea already claims to meet. Further research is needed to establish how widespread and commercially important a problem is.

Refine a hypothesis through interviews

Suppose a founder believes restaurant managers need a new scheduling app. Instead of pitching the app, the founder asks managers about the last few schedules they created. Several describe checking availability through text messages, copying shifts into spreadsheets, and repeatedly revising schedules after staff changes. One manager reports spending about three hours each week on revisions; another rarely has difficulty because a supervisor handles scheduling.

These accounts suggest that scheduling problems may be concentrated among owner-managers who build schedules themselves, rather than all restaurant managers. The founder can refine the segment, interview more people in that role, and test whether the reported time burden is common and significant. This produces a sharper problem hypothesis, not proof that customers will adopt or pay for any particular solution.

Bring the findings together

Customer discovery defines a plausible customer group and investigates its real-world tasks, difficulties, and desired outcomes. Ask about recent behavior, separate observations from assumptions, and look for recurring evidence of meaningful consequences and existing workarounds. A strong problem statement identifies the customer and difficulty without jumping to a solution, while further research tests how widespread and commercially important the problem may be.