It was a Thursday afternoon, and our team backlog looked like a packed suitcase before a red-eye flight—bulging, messy, and full of things we didn’t actually need.
Marketing wanted a dashboard.
Sales needed a new integration “urgently.”
Design had found a usability rabbit hole.
And our CEO had a “small tweak” that would somehow take 3 weeks to build.
“So… what’s the priority?” asked my engineer.
I opened my mouth—and realized I didn’t have a good answer.
That was the day I promised myself: I’ll never “gut feel” a backlog again.
Why Prioritization Feels So Hard
Because it is.
You’re balancing:
- User needs
- Business goals
- Tech constraints
- Time and team energy
- Leadership pressure
And still, you’re expected to be decisive, fast, and right.
But here’s the good news: you don’t need to guess. You need a framework.
Let me walk you through a few that saved my sanity—and gave my team confidence we were building the right things.
Framework 1: RICE
One of the most popular—and one I still use for product roadmapping.
| Factor | What it means |
|---|---|
| Reach | How many users will this impact? |
| Impact | How big is the change per user? |
| Confidence | How sure are you about reach & impact? |
| Effort | How long will it take to build? (person-weeks, days, etc.) |
Formula:RICE Score = (Reach × Impact × Confidence) / Effort
🧠 Use RICE when:
You’re managing many ideas, need to rank them quickly, and have some early data or estimates.
Example:
We once had 10 feature ideas. After applying RICE, the “simple billing update” turned out to have 10x more reach and 3x less effort than a major redesign. That insight saved us 3 weeks and drove more revenue.
Framework 2: MoSCoW
This one is simple but powerful—especially in stakeholder discussions.
| Priority | Meaning |
|---|---|
| Must-Have | Without this, the release is broken |
| Should-Have | Adds significant value, but not essential for launch |
| Could-Have | Nice to have, often low effort |
| Won’t Have (now) | Out of scope for now (not forever) |
🧠 Use MoSCoW when:
You’re planning sprints, MVPs, or negotiating with non-technical stakeholders.
Real story:
Before one launch, we used MoSCoW to align with marketing, legal, and engineering. When tensions ran high, “Won’t Have (now)” became our best friend—it gave us permission to say “not yet” without saying “never.”
Framework 3: Value vs. Effort Matrix
Also known as the 2×2 Prioritization Grid, it’s a visual way to make quick calls.
| Low Effort | High Effort | |
|---|---|---|
| High Value | 🚀 Quick wins | 🧗 Strategic investments |
| Low Value | 🧹 Time-wasters | ❌ Avoid or deprioritize |
🧠 Use it when:
You need to align a diverse group of stakeholders and want to make trade-offs visually.
We used this in a workshop with sales, CS, and design. The moment someone tried to push a high-effort, low-value feature… the team laughed. The grid doesn’t lie.
Framework 4: Kano Model
A little more advanced—but super useful for UX-heavy or B2C products.
It categorizes features into:
- Basic Needs: Users expect this. Without it, they’re unhappy. (e.g., login)
- Performance Needs: The better it works, the happier they are. (e.g., app speed)
- Delighters: Unexpected joys. Not required, but leave a lasting impression. (e.g., witty animations, smart defaults)
🧠 Use it when:
You’re designing for delight and trying to balance utility vs. joy.
Pro tip: You can use simple surveys to map user responses to Kano buckets.
Framework 5: Opportunity Scoring (Jobs To Be Done)
This one is for PMs who love digging into why users struggle.
The idea: measure user importance vs. satisfaction on specific outcomes.
| Opportunity Score = Importance + (Importance – Satisfaction) |
🧠 Use it when:
You’re exploring new features or prioritizing improvements.
This helped us uncover that users didn’t care as much about speed—what really frustrated them was inconsistency. The insight shifted our entire Q2 roadmap.
How to Actually Use These Frameworks
A framework won’t make the decision for you. But it:
- Structures the conversation
- Surfaces assumptions
- Brings cross-functional alignment
- De-risks emotional decisions
That said, don’t overdo it. I’ve seen teams paralyzed by frameworks—scoring features to the decimal point, holding five-hour backlog sessions.
🔑 Use frameworks as lenses, not crutches. And remember: intuition sharpened by data is your best bet.
Final Thoughts: Your Job Is to Prioritize Clarity
You’ll never have perfect data.
You’ll never make everyone happy.
But if you can say—clearly, calmly, and confidently—
“Here’s why we’re doing this next…”
Then you’re doing your job right.
Great PMs don’t just prioritize features.
They prioritize focus.
And focus is how you build momentum—and eventually, magic.
product.guru 
Leave a comment