What is Problem Discovery?

In product management, the single biggest point of failure is building a product that nobody wants. This usually happens because we start with a solution in mind and search for a problem to justify it. Problem Discovery is the disciplined practice of exploring the user's world to uncover genuine frustrations, needs, and desires before designing any features.

"If I had an hour to solve a problem I'd spend 55 minutes thinking about the problem and 5 minutes thinking about solutions."
— commonly attributed to Albert Einstein

The Solution Trap

Why do we fall into the Solution Trap? As humans, we are wired to resolve tension quickly. Seeing a problem makes us want to fix it immediately. However, the first solution that comes to mind is rarely the best one, and it is often based on unverified assumptions.

Problem discovery forces you to build a deep understanding of:

• Who is the user experiencing the pain?
• What is the exact context and frequency of the pain?
• Why does it matter to them (emotional and functional triggers)?
• How are they solving it today (existing workarounds)?

Continuous vs. Dual-Track Discovery

Traditionally, discovery was done in a big upfront batch at the start of a project (waterfall discovery). Modern product teams use Continuous Discovery, a weekly cadence of talking to customers, run in parallel with delivery (development).

This ensures that the product team is always learning and adapting, rather than building based on outdated research or initial assumptions.