Home/Product Building/Problem Discovery/Problem Identification

Identifying Real Problems

Find problems worth solving through systematic research

How 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

WHAT TO LISTEN FOR
  • β€’Repeated frustrations
  • β€’Time-consuming tasks
  • β€’Workarounds they built
  • β€’Things they avoid
HOW TO USE IT

Ask "Tell me about the last time you..." and listen for pain points

EXAMPLE

Every week I spend 3 hours copying data between systems. I hate it but there is no other way.

Quality: High - direct insight into real problems

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:

PROBLEM STATEMENT

Users find it hard to remember their passwords

FREQUENCY
High

How often it happens

INTENSITY
Medium

How painful it is

WILLINGNESS TO PAY
Low

Monetization potential

Overall Score
6/10
Moderate Problem

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.