Finding a customer problem worth solving
Learn how to distinguish recurring, urgent customer problems from mild inconveniences and founder assumptions.
Start with situations, not demographics
A useful problem statement describes a person in a specific situation, the progress they are trying to make, and what blocks that progress. Demographics alone rarely explain why someone acts.
Look for moments where people improvise, create spreadsheets, hire help, tolerate repeated errors, or coordinate across several tools. Workarounds reveal both pain and willingness to invest effort.
Keep in mind
- Describe the last real occurrence.
- Measure frequency and consequence separately.
- Map every current alternative, including doing nothing.
Separate symptoms from causes
Customers often describe the visible symptom. Ask what creates it, what happens next, and why the current process persists. The root cause may be incentives, missing information, fragmented ownership, or risk rather than missing software.
A root-cause map prevents a team from automating a broken step while leaving the actual constraint untouched.
Score opportunity without pretending certainty
Compare problems using frequency, severity, budget ownership, accessibility of the audience, and dissatisfaction with alternatives. The score is a conversation tool, not proof.
Choose a narrow beachhead where learning can happen quickly. A smaller reachable group with acute pain is usually a better start than a vast audience with weak urgency.