Identifying Real Problems
Find problems worth solving through systematic research
Your Progress
Section 2 of 5How to Find Problems
Problems are everywhereβyou just need to know where to look and what to listen for. The best problems come from direct user contact combined with behavioral data.
Use multiple sources. No single method reveals the full picture. Triangulate insights from conversations, behavior, and market signals.
Problem Discovery Sources
Where to Find Problems
π€User Interviews
Direct conversations with users
- β’Repeated frustrations
- β’Time-consuming tasks
- β’Workarounds they built
- β’Things they avoid
Ask "Tell me about the last time you..." and listen for pain points
Every week I spend 3 hours copying data between systems. I hate it but there is no other way.
Signs of a Real Problem
β Good Signs
- β’ Users mention it without prompting
- β’ They've built workarounds
- β’ It costs them time or money
- β’ Multiple users have the same problem
- β’ They express urgency or emotion
β Warning Signs
- β’ Only mentioned when you ask directly
- β’ "Nice to have" language
- β’ No current workaround attempted
- β’ Each user describes it differently
- β’ Theoretical "would be cool if..."
Qualifying Problems
Problem Qualification Framework
Not all problems are worth solving. Evaluate problems on three dimensions:
Users find it hard to remember their passwords
How often it happens
How painful it is
Monetization potential
Frequent but low willingness to pay (password managers are free/cheap)
Quality Over Quantity
Better to deeply understand 5 users' problems than superficially collect feedback from 100. Go deep, ask follow-ups, and understand the context and impact of each problem.
Key Takeaways
- β’Use multiple sources: user interviews, support tickets, analytics, sales calls, and social listening.
- β’Look for frequency, intensity, and willingness to payβall three should be high for strong problems.
- β’Real problems surface unprompted, have existing workarounds, and show urgency from users.
- β’Depth beats breadthβdeeply understand a few users rather than superficially survey many.