How to Find Problems Efficiently
Yishnu Pramanik | 9 min read | Dec 18, 2024 | Medium Blog
Hey there, curious minds! 👋
If there’s one thing I’ve learned as a Product Manager, it’s this: problems are goldmines. Finding the right problem to solve can transform your product, business, and user experience. But the tricky part? Finding them efficiently.
Most people focus on solutions too soon. Picture this: you notice a leaky pipe at home, so you grab a bucket to catch the water. But…what if the leak is hidden behind the wall? Fixing the bucket solves nothing if the pipe stays broken.
This blog is your guide to uncovering those “hidden leaks” (problems) using a step‑by‑step approach. By the end, you’ll know exactly how to clarify, analyze, and articulate problems that matter — whether you’re in tech, design, or business.
Let’s get into it! 🚀
Clarify and Analyze the Problem
Let me share a real story: I once sat in a tense product meeting. Our analytics team sent a worrying email — “Engagement is dropping by 15%.” Churn rates were also climbing among new users. Immediately, people started brainstorming solutions: “Let’s add more features!” or “Maybe we need a redesign?”
But instead of guessing, I said, “Hold up. Let’s analyze first.” Here’s the step‑by‑step approach to analyzing problems:
Step 1: Define the Problem Clearly
You can’t solve a blurry problem. Make it specific. Instead of saying:
❌ “Users are dropping off.”
✅ Say: “Engagement rates have dropped 15% in the last 3 months, and churn among new users increased by 10%.”
Clarity like this aligns your team and removes guesswork. Imagine standing in a room with a foggy mirror. Defining the problem is like wiping that mirror clean — it shows you exactly what’s happening.
Step 2: Gather Data
Data is your flashlight in the dark. Without it, you’re just stumbling around guessing. Start by asking:
- Where are the leaks happening? (Analytics tools like Mixpanel, Amplitude)
- What are users saying? (Surveys, app reviews, support tickets)
- What behaviors can we observe? (Tools like Hotjar, FullStory)
For example: In one project, we found that 40% of new users abandoned onboarding. We didn’t guess why — they told us! The feedback was clear:
“Too confusing.”
“Takes forever to complete.”
Suddenly, the problem had a face.
Step 3: Identify the Root Causes
Now it’s time to dig deep. Problems are like icebergs — the real causes sit below the surface. Use the 5 Whys Framework to ask “why” repeatedly until you hit the root cause.
Here’s how it worked for us:
Why are users abandoning onboarding? → It’s too complex.
Why is it complex? → Steps aren’t clear.
Why aren’t they clear? → No tutorial or tooltips to guide them.
Root Cause: Onboarding lacked clarity and guidance.
Good Reads
https://userpilot.com/blog/problem-solving-framework/
Fishbone Diagram (Ishikawa Diagram)
https://www.linkedin.com/pulse/problem-solving-decision-making-frameworks-essential-tools-karami/
https://drive.google.com/file/d/1NT6Ha1Oyp7qD9tShuQc_-A-DCjZ35v7a/view
Structure the Problem
Imagine you’re solving a 1,000‑piece puzzle. If you dump all the pieces on a table and start randomly, you’ll feel lost. But what if you sort by edges, colors, and sections? That’s what structuring a problem does — it turns chaos into clarity.
Why Structure Matters
Without structure:
❌ Teams waste time on irrelevant details.
❌ Problems stay unsolved, or fixes are temporary.
With structure:
✅ You break complexity into smaller, solvable chunks.
✅ Teams stay aligned and focused.
How to Structure Problems
Two powerful techniques — MECE (Mutually Exclusive, Collectively Exhaustive) and Issue Trees — help break down problems into manageable, logical pieces.
MECE Approach
The MECE principle ensures your problem breakdown is:
- Mutually Exclusive (ME): No overlaps between categories — each item fits in one and only one bucket.
- Collectively Exhaustive (CE): All possibilities are covered, leaving no gaps.
Issue Tree
An Issue Tree visually breaks down a problem into smaller, actionable parts. It starts with a root question and branches into sub‑questions.
Key Elements of an Issue Tree:
- Clear Root Question: The main issue you want to solve.
- Branches: Sub‑questions that logically stem from the root.
- Leaves: Specific, actionable areas for analysis.
How to Use These Tools in Problem Solving
👉 Start with the MECE Principle: Identify categories to cover the entire scope of the problem.
👉 Build an Issue Tree: Break down the problem into detailed, solvable pieces using logical branches.
👉 Analyze Leaves: Dive deep into each sub‑problem and test hypotheses.
For a deeper dive into issue trees and the MECE principle, explore these resources:
The Ultimate Guide to Issue Trees
Watch: How to Use MECE in Problem Solving
The 5 Ways to Be MECE
https://www.mbacrystalball.com/blog/strategy/mece-framework/
https://slideworks.io/resources/mece-mutually-exclusive-collectively-exhaustive
https://medium.com/@paralloid/types-of-information-and-mece-principle-ccc33f823809
Understanding the User Problem
Your product exists to solve user problems. If it doesn’t, it doesn’t matter how fancy or feature‑rich it is.
User problems are the struggles users face while interacting with your product. For example:
- “I can’t find the sign‑up button on the homepage.”
- “The app crashes every time I try to upload a photo.”
To uncover these problems, you need to ask the right questions and use the right tools.
Ask the Right Questions
Think like a detective piecing together clues. Start with these questions:
- Who is my user? Segment users (e.g., new users, power users) and build user personas. Each segment has unique struggles.
- Why do they use my product? Does it solve an absolute pain point, a good‑to‑have, or delight them with add‑ons?
- How do they use my product? Which features do they rely on? Where do they drop off?
- What do they think and feel? How do they feel before and after using your product?
- What insights can I gather? Combine feedback, behavioral patterns, and emotions to spot recurring pain points.
Gathering Insights
Now that you know what to look for, let’s talk about how to uncover these user problems. Here are the top techniques every PM should master:
- Listen to Feedback: Surveys, app reviews, and user interviews.
- Analyze Behavioral Data: Drop‑offs, bounce rates, low feature usage.
- Observe Users Directly: Hotjar, usability testing platforms.
For Example:
User Feedback: “The app loads too slowly on my phone.”
Behavioral Data: High mobile bounce rates.
Observation: Users abandon the app mid‑task because it freezes.
🔍 Root Cause: Poor mobile optimization.
Good Read
https://uxpressia.com/blog/how-to-create-persona-guide-examples
https://jobs-to-be-done.com/jobs-to-be-done-a-framework-for-customer-needs-c883cbf61c90
https://www.mindtools.com/a3mi00v/5-whys
https://www.nngroup.com/articles/journey-mapping-101/
Map Problems to Business Impact
Now that you’ve identified user problems, it’s time to ask: Is this worth solving? As PMs, our job isn’t just to solve problems — it’s to solve problems that move the needle for the business.
👉 If solving the problem ties back to either revenue or profits, it’s worth your time.
Identify Impact
Everything ties back to revenue or profits. Whether you’re boosting user growth, improving retention, driving monetization, or cutting costs, the ultimate goal is clear.
Metrics Are Your Best Friend
To evaluate business impact, tie the problem to a measurable metric — your success criteria.
- Leading Metrics: Early signals of success.
- Lagging Metrics: Long‑term results directly affecting revenue or profit.
Example
Streaming platform user problem: “It’s hard to decide what to watch next.”
Leading Metrics:
- Average time spent browsing before starting a show
- Number of shows watched per user
Lagging Metric:
- Increased subscriptions due to improved user satisfaction
Good Reads
https://blog.flipkart.tech/introducing-aspect-ratings-reviews-93875da9481a
https://about.netflix.com/en/news/looking-back-on-the-origin-of-skip-intro-five-years-later
Communicate with Clarity
You’ve found the problem. 🎉 But here’s where many PMs trip up: articulating the problem effectively.
Rules for Articulating
✅ No Assumptions. Be clear about your assumptions and hypotheses.
✅ Be Clear and Measurable. “Users are unhappy” won’t cut it. Instead: “40% of users abandon the onboarding process due to unclear steps.”
✅ Use Plain, Relatable Language. Avoid jargon.
A Simple Framework
Frame the problem from the user’s perspective:
“I am (persona) trying to (verb) but (barrier) because (cause), which makes me feel (emotion).”
Example: “I am a new mom trying to care for my baby in the best way possible, but I don’t know if I’m doing a good job because I’m always home alone and have no one to talk to about it, which makes me feel isolated and unsure.”
Good Reads
https://www.linkedin.com/pulse/5-steps-help-you-articulate-problems-clearly-build-best-dr-grace-lee/
https://eltu.cuhk.edu.hk/Project_C/module1_part1.php
Generative and Problem Discovery
In today’s world, Generative AI is revolutionizing product discovery by uncovering insights, automating research, and driving innovation. Here’s how it helps:
👉 Customer Insights: ChatGPT analyzes user feedback and behavior to reveal trends and preferences.
👉 Data Pattern Analysis: DataRobot processes large datasets to detect hidden patterns.
👉 Competitive Research: Crimson Hexagon summarizes market trends and offerings.
👉 Product Information Optimization: Writesonic creates accurate, consistent product descriptions.
👉 Personalized Recommendations: Recombee delivers tailored product suggestions.
👉 Real‑Time Feedback: MonkeyLearn analyzes feedback instantly.
Good Reads
https://medium.com/@olgamarti90/how-generative-ai-can-transform-your-discovery-phase-fc150a1759c8
https://www.productleadership.com/ai-driven-product-discovery/
https://www.producttalk.org/2024/06/generative-ai-discovery/
https://constructor.com/blog/generative-ai-product-discovery
https://www.pendo.io/pendo-blog/the-ultimate-guide-to-using-ai-for-product-discovery/
Finding problems efficiently is a superpower that every product leader needs. When you uncover the right problems, the solutions will naturally follow.
Now go out there and start digging! Your next big opportunity is hidden in the problems waiting to be solved. 🚀