Home/Product Building/Product Thinking/Problem-First Approach
←
Previous Module
Product Lifecycle

Problem-First Approach

Learn to fall in love with the problem, not your solution

Your Progress

Section 2 of 5
1
2
3
4
5

Problem-First Approach

The problem-first approach means deeply understanding the problem before exploring solutions. It is about falling in love with the problem, not your solution.

Too many products fail because teams jump straight to building without truly understanding what problem they are solving. A well-defined problem opens up more creative solution possibilities.

Problem or Solution?

Examples:

✅problem

Users struggle to find relevant products in our catalog

❌solution

We should add a search feature

✅problem

Customers spend too much time on checkout

❌solution

Build a one-click purchase button

The Five Whys Technique

The Five Whys is a simple but powerful technique to uncover root causes. Each "why" digs deeper beneath surface symptoms to reveal underlying issues.

Example: Cart Abandonment

Users are abandoning their shopping carts

1. Why? Users leave without completing purchase

2. Why? They get distracted or change their mind

3. Why? Checkout process takes too long

4. Why? Too many form fields and steps

5. Why? We ask for unnecessary information

Try It Yourself:

Problem-First Principles

🔍

Seek to Understand

Invest time in understanding the problem deeply. Talk to users, observe behavior, feel their frustration.

❓

Challenge Assumptions

Question everything. Your first understanding of a problem is rarely complete or accurate.

🎯

Focus on Root Causes

Do not stop at symptoms. Use techniques like Five Whys to dig deeper and find root causes.

💡

Delay Solutions

Resist jumping to solutions too early. A well-defined problem opens up more creative solution possibilities.

⚠️

Common Pitfall

Do not mistake stakeholder requests for problems. "We need a mobile app" is a solution. Ask why they think they need it to uncover the actual problem.

Key Takeaways

  • •Always understand the problem deeply before exploring solutions
  • •Use the Five Whys technique to uncover root causes
  • •Challenge assumptions and stakeholder requests
  • •Delay solutions until the problem is well-defined
← Introduction