"Is solving problems the ultimate product management skill? Not quite. The real game-changer lies in uncovering the right problems to solve."
When I stumbled upon a LinkedIn post claiming that “solving a problem is an invaluable skill,” I paused to reflect. While this is a fair argument, I believe it only scratches the surface. The ability to solve problems is important, but the true superpower lies in identifying the right problems to solve.
This insight struck me years ago when I was teaching 8-year-olds mathematics. They could easily solve equations when provided, but word problems — requiring them to deduce the problem before finding the solution — left them perplexed. This taught me a crucial lesson: the key to value creation is not in the solution itself but in understanding the problem’s impact. And isn’t that why product-market fit matters?
But I might be wrong — so, let’s debate this. Share your thoughts after reading!
Product management literature often emphasizes the value of solutions. According to scrum.org, a key skill for product managers is identifying features that create user value. But many assume that a product’s value stems solely from the impact of its solution—how well it performs or meets user needs.
But is that really true? Let’s explore the impact of a solution vs. the impact of a problem with a simple example.
A Tale of Two Headaches: The Problem Impact Framework
Imagine you have a slight headache and visit a pharmacy for paracetamol. The price tag says $100 instead of the usual $5. Would you buy it? Likely not. You’d probably walk away, deciding the headache isn’t worth the cost.
Now imagine you’re experiencing a splitting migraine—blurred vision, pounding pain. That same $100 paracetamol might suddenly feel like a lifesaver. You might even consider buying it at $120 or $150.
What changed?
The solution remained constant—paracetamol relieves pain. But the problem’s impact dramatically shifted your willingness to pay.
This insight holds the secret to monetization. The value of a solution depends on the impact of the problem it solves. Once you identify a high-impact problem, you can create engagement, reliance, and revenue around the solution.
Case Study: Insurance Comparison Site and the Misunderstood Problem
I once worked with an InsureTech client in South America that owned a popular comparison site. They averaged 1,000 daily visits but suffered from single-digit conversion rates, affecting revenue. They asked me to optimize conversions.
At first glance, the problem seemed clear: customers wanted convenient insurance purchasing. But after analysis, I realized the real problem was different: customers valued finding the best price, not purchasing through the platform.
If I had focused solely on the client’s desired solution—lowering prices, improving user journeys, or increasing marketing spend—I would have missed the real issue. Instead, I proposed monetizing the comparison page through ads, subscriptions, and premium memberships. This pivot tapped into the true value users sought and unlocked a potential $5M in annual revenue.
1. Stop Solutionizing and Focus on Problem Impact
One of my managers always said, “Stop solutionizing; let’s discuss the problem.” Solutions are easy to find, but solving the wrong problem wastes resources and creates frustration.
2. Weight Problems Using Frameworks
Use tools like the RICE model (Reach, Impact, Confidence, Effort) to evaluate problems and prioritize those with the highest impact.
3. Understand Value Through the Customer’s Lens
Think beyond the immediate solution. Ask yourself:
Understanding the real problem your product addresses is essential for growth. It helps you:
1. Always Question Assumptions
When stakeholders present a solution, dig deeper. Ask, “What problem are we solving?” before investing time or resources.
2. Use Data to Validate Problem Impact
Segment customers, analyze their pain points, and quantify problem urgency through surveys, analytics, and feedback.
3. Leverage Real-World Insights
Take inspiration from examples like the restaurant charging travelers for toilet access or the pharmacy pricing paracetamol for migraines. Understand user needs in context to uncover high-impact problems.
The next time you’re brainstorming solutions, pause. Ask yourself:
“Are we addressing the right problem?”
Understanding the impact of the problem is the cornerstone of creating real value as a product manager. And remember: solutions are only as good as the problems they solve.
Have you ever built a solution for the wrong problem? Share your experiences in the comments and let’s learn together!
Questions and Comments about the article? Connect with Nenny Stevenson
Mentorship program and in-person event experiences are at an extra cost.
Join for free!Join the TPMA Slack Community with 1000+ members
Free Virtual TPMA events for the entire TPMA Season
Become the first to know about in-person events and networking opportunities
"Is solving problems the ultimate product management skill? Not quite. The real game-changer lies in uncovering the right problems to solve."
When I stumbled upon a LinkedIn post claiming that “solving a problem is an invaluable skill,” I paused to reflect. While this is a fair argument, I believe it only scratches the surface. The ability to solve problems is important, but the true superpower lies in identifying the right problems to solve.
This insight struck me years ago when I was teaching 8-year-olds mathematics. They could easily solve equations when provided, but word problems — requiring them to deduce the problem before finding the solution — left them perplexed. This taught me a crucial lesson: the key to value creation is not in the solution itself but in understanding the problem’s impact. And isn’t that why product-market fit matters?
But I might be wrong — so, let’s debate this. Share your thoughts after reading!
Product management literature often emphasizes the value of solutions. According to scrum.org, a key skill for product managers is identifying features that create user value. But many assume that a product’s value stems solely from the impact of its solution—how well it performs or meets user needs.
But is that really true? Let’s explore the impact of a solution vs. the impact of a problem with a simple example.
A Tale of Two Headaches: The Problem Impact Framework
Imagine you have a slight headache and visit a pharmacy for paracetamol. The price tag says $100 instead of the usual $5. Would you buy it? Likely not. You’d probably walk away, deciding the headache isn’t worth the cost.
Now imagine you’re experiencing a splitting migraine—blurred vision, pounding pain. That same $100 paracetamol might suddenly feel like a lifesaver. You might even consider buying it at $120 or $150.
What changed?
The solution remained constant—paracetamol relieves pain. But the problem’s impact dramatically shifted your willingness to pay.
This insight holds the secret to monetization. The value of a solution depends on the impact of the problem it solves. Once you identify a high-impact problem, you can create engagement, reliance, and revenue around the solution.
Case Study: Insurance Comparison Site and the Misunderstood Problem
I once worked with an InsureTech client in South America that owned a popular comparison site. They averaged 1,000 daily visits but suffered from single-digit conversion rates, affecting revenue. They asked me to optimize conversions.
At first glance, the problem seemed clear: customers wanted convenient insurance purchasing. But after analysis, I realized the real problem was different: customers valued finding the best price, not purchasing through the platform.
If I had focused solely on the client’s desired solution—lowering prices, improving user journeys, or increasing marketing spend—I would have missed the real issue. Instead, I proposed monetizing the comparison page through ads, subscriptions, and premium memberships. This pivot tapped into the true value users sought and unlocked a potential $5M in annual revenue.
1. Stop Solutionizing and Focus on Problem Impact
One of my managers always said, “Stop solutionizing; let’s discuss the problem.” Solutions are easy to find, but solving the wrong problem wastes resources and creates frustration.
2. Weight Problems Using Frameworks
Use tools like the RICE model (Reach, Impact, Confidence, Effort) to evaluate problems and prioritize those with the highest impact.
3. Understand Value Through the Customer’s Lens
Think beyond the immediate solution. Ask yourself:
Understanding the real problem your product addresses is essential for growth. It helps you:
1. Always Question Assumptions
When stakeholders present a solution, dig deeper. Ask, “What problem are we solving?” before investing time or resources.
2. Use Data to Validate Problem Impact
Segment customers, analyze their pain points, and quantify problem urgency through surveys, analytics, and feedback.
3. Leverage Real-World Insights
Take inspiration from examples like the restaurant charging travelers for toilet access or the pharmacy pricing paracetamol for migraines. Understand user needs in context to uncover high-impact problems.
The next time you’re brainstorming solutions, pause. Ask yourself:
“Are we addressing the right problem?”
Understanding the impact of the problem is the cornerstone of creating real value as a product manager. And remember: solutions are only as good as the problems they solve.
Have you ever built a solution for the wrong problem? Share your experiences in the comments and let’s learn together!
Questions and Comments about the article? Connect with Nenny Stevenson