The Product Framework Problem: Knowing What to Use, When to Use It
You know RICE.
You know JTBD.
You know AARRR.
You know Kano.
You’ve probably seen dozens of product frameworks.
But then a real product problem lands on your desk.
And suddenly the question is:
“Which framework should I actually use here?”
That’s the part most framework lists don’t teach.
The real skill isn’t memorizing frameworks.
It’s knowing which framework fits which situation — and what decision it should help you make.
1. “We have 20 ideas. What should we build first?”
Use: Prioritization Frameworks
Try:
- RICE
- ICE
- MoSCoW
- Value vs. Effort
Use them when:
Your team has more opportunities than capacity.
The goal is to create a transparent way to compare opportunities instead of prioritizing based purely on whoever speaks the loudest.
Ask:
“Which opportunity creates the most value relative to the investment?”
But remember: a score is an input to a decision, not the decision itself.
2. “Are we even solving the right problem?”
Use: Product Discovery Frameworks
Try:
- Jobs-to-be-Done
- Design Thinking
- Double Diamond
- Opportunity Solution Tree
Use them when:
You’re still trying to understand the customer problem.
This is especially useful before jumping into feature discussions.
Instead of asking:
“What should we build?”
Start with:
“What is the user actually trying to accomplish?”
That shift can completely change the product direction.
3. “Where should our product go next?”
Use: Product Strategy Frameworks
Try:
- SWOT
- Porter’s Five Forces
- Playing to Win
- Blue Ocean Strategy
Use them when:
You’re making longer-term decisions about markets, positioning, differentiation, or competitive advantage.
Ask:
“Where should we play and how can we create an advantage there?”
Strategy frameworks are particularly useful when the answer isn’t simply another feature.
4. “Our product is growing, but where is the problem?”
Use: Growth Frameworks
Try:
- AARRR
- Growth Loops
- North Star Metric
- AIDA
Use them when:
You need to understand acquisition, activation, retention, referral, or monetization.
Instead of saying:
“We need more users.”
Break the growth problem down.
Are users discovering the product?
Are they activating?
Are they returning?
Are they converting?
Ask:
“What behavior actually drives sustainable growth?”
5. “Users are dropping off somewhere. Where?”
Use: UX Frameworks
Try:
- User Journey Mapping
- Service Blueprint
- HEART
- Kano Model
Use them when:
You need to understand friction across the customer experience.
A user may not have a “feature problem.”
They may have a discovery problem, usability problem, trust problem, or handoff problem.
Ask:
“Where does the experience break down?”
6. “Should we launch this change?”
Use: Experimentation Frameworks
Try:
- A/B Testing
- Hypothesis → Experiment → Learn
- ICE
- OEC
Use them when:
You have uncertainty that can be reduced through testing.
Start with a hypothesis.
Define what success means.
Run the smallest useful experiment.
Get Arushi Rana’s stories in your inbox
Join Medium for free to get updates from this writer.
Learn.
Then decide whether to scale, iterate, or stop.
Ask:
“What do we need to learn before investing more?”
7. “Are we measuring the right thing?”
Use: Metrics Frameworks
Try:
- North Star Metric
- Input vs. Output Metrics
- HEART
- AARRR
Use them when:
Teams are drowning in dashboards but still don’t know whether the product is actually improving.
For example:
A feature shipped is an output.
A user successfully completing a meaningful task is closer to an outcome.
Ask:
“Are we measuring activity or impact?”
8. “We have a strategy. Now how do we actually deliver it?”
Use: Execution Frameworks
Try:
- Agile
- Scrum
- Dual-Track Agile
- Shape Up
Use them when:
You need to translate product direction into coordinated execution.
The framework should create clarity around:
What are we building?
Why are we building it?
Who is involved?
How will we know it worked?
Ask:
“How do we move from decision → execution without losing the outcome?”
9. “Everyone has an opinion. Who actually decides?”
Use: Stakeholder Frameworks
Try:
- RACI
- DACI
- RAPID
- Pyramid Principle
Use them when:
Decision-making is becoming slow or unclear.
This is especially useful when product, engineering, design, sales, operations, compliance, and leadership all have different perspectives.
Ask:
“Who decides, who contributes, and who needs to know?”
10. “Should AI solve this problem?”
Use: AI Product Thinking
AI products introduce another layer of complexity.
You need to think about:
- Human-in-the-loop
- AI opportunity mapping
- Model → Product → Outcome
- Risk × Impact
Use them when:
You’re deciding whether AI genuinely improves the customer or business outcome.
Not every problem needs AI.
And adding an LLM to a workflow doesn’t automatically create an AI product.
Ask:
“Where does AI create meaningful value — and where should humans remain in control?”
The Framework Is Not the Product Decision
This is where product managers sometimes get stuck.
They find a framework.
They fill in the boxes.
They calculate the score.
They produce a beautiful slide.
And then they assume the framework made the decision.
It didn’t.
You did.
A framework gives you structure.
It helps you surface assumptions.
It creates a common language for teams.
But context still matters.
A RICE score cannot understand every strategic dependency.
A user journey cannot tell you your entire business strategy.
An A/B test cannot tell you whether something is ethically or strategically worth building.
And an AI framework cannot tell you whether AI is actually necessary.
That’s where product judgment comes in.
A Simple Rule I Use
Before reaching for a framework, ask four questions:
1. What problem am I trying to solve?
2. What decision do I need to make?
3. What information do I currently have?
4. What uncertainty am I trying to reduce?
Then choose the framework.
Not the other way around.
The Real PM Skill
The strongest product managers aren’t necessarily the ones who know the most frameworks.
They’re the ones who can look at a messy situation and quickly identify:
Problem → Context → Framework → Decision → Outcome
And sometimes the right answer is:
“We don’t need a framework for this.”
Because frameworks should make your thinking clearer.
Not make your thinking dependent on them.
Know the frameworks.
Understand the context.
Make the decision.
That’s product thinking.
Which product framework do you find yourself using most often and in what situation?
#ProductManagement #ProductManager #ProductStrategy #ProductDiscovery #ProductLeadership #AIProductManagement #ProductThinking #GrowthProductManagement #ProductManagementTips #ArtificialIntelligence
