Every PM learns prioritization frameworks. RICE. ICE. Value vs. Effort matrices. MoSCoW. Kano models.
Frameworks are useful. They provide structure. They make prioritization defensible. They create shared language.
But frameworks can also be theater—a way to make arbitrary decisions look rigorous.
Here's how to use them well, and when to throw them out.
Why Frameworks Help
Structure: Without a framework, prioritization discussions can be chaos. Everyone advocates for their thing. The loudest voice wins. Frameworks provide order.
Consistency: Frameworks force you to evaluate everything on the same dimensions. This reduces bias toward whatever you looked at most recently.
Communication: Frameworks create shared language. "The RICE score is 47" is more precise than "I think this is important."
Documentation: When someone asks "why did we prioritize X over Y?", the framework provides an answer.
These benefits are real. Don't dismiss frameworks entirely.
The Limits of Frameworks
Garbage in, garbage out: Frameworks require inputs—reach, impact, confidence, effort. These inputs are often guesses. A precise-looking framework built on wild guesses produces false confidence.
They reward gaming: Once you know the formula, you can make anything look good. Inflate the impact estimate, deflate the effort, and suddenly your pet project is top priority.
They obscure judgment: The framework produces a number, but the number comes from human judgment at every step. The appearance of objectivity can hide the subjectivity underneath.
They don't handle strategy: Should we invest in new growth or retention? What's our competitive positioning? These strategic questions aren't answered by scoring features.
Context gets lost: A framework treats a feature as numbers. But some things matter beyond what the numbers capture—strategic importance, team morale, technical debt, customer promises.
Common Frameworks
RICE
Reach: How many users does this affect? Impact: How much does it affect each user? (Scale: 0.25, 0.5, 1, 2, 3) Confidence: How confident are you in the estimates? (Percentage) Effort: How much work is this? (Person-months)
RICE Score = (Reach x Impact x Confidence) / Effort
When it works: When you have reasonable estimates for reach and impact. Best for features with measurable outcomes.
When it doesn't: When impact is hard to quantify, or when you're comparing apples to oranges (growth feature vs. infrastructure work).
ICE
Impact: How much impact will this have? Confidence: How confident are you? Ease: How easy is this to do?
ICE Score = Impact x Confidence x Ease
When it works: Simpler than RICE. Good for quick prioritization when you don't have detailed data.
When it doesn't: Very susceptible to gaming. "Impact" without "reach" conflates magnitude with breadth.
Value vs. Effort Matrix
Plot everything on a 2x2: high/low value vs. high/low effort.
- •High value, low effort: Do first (quick wins)
- •High value, high effort: Plan carefully (big bets)
- •Low value, low effort: Maybe do (fillers)
- •Low value, high effort: Don't do (time sinks)
When it works: Good for initial sorting. Creates obvious buckets.
When it doesn't: Oversimplified. Everything becomes a value/effort debate, and the 2x2 hides nuance.
Stack Ranking
Forget scoring. Just order everything from most important to least important.
When it works: Forces absolute decisions. No hiding behind tied scores.
When it doesn't: Doesn't explain why. Can feel arbitrary.
How to Use Frameworks Well
Use multiple lenses: Don't rely on just one framework. RICE for quantifiable features, strategic alignment for initiatives, customer urgency for support issues.
Be honest about confidence: If you're guessing, say so. Don't pretend certainty you don't have.
Expose the assumptions: Share the inputs, not just the outputs. Let people challenge your estimates.
Don't worship the score: The framework is an input to judgment, not a replacement for it. If the score says one thing and your gut says another, dig into the gap.
Revisit regularly: Priorities change. Last month's scoring might be outdated.
When to Abandon the Framework
Sometimes frameworks don't help:
Strategic decisions: "Should we build a mobile app?" isn't a RICE question. It's a strategy question.
Customer promises: You committed to something. The framework score doesn't matter—you have to deliver.
Team morale: Sometimes you do something because the team needs a win, not because it scored well.
Technical necessity: Infrastructure work often scores poorly on user-facing frameworks. Do it anyway.
Executive mandates: Sometimes leadership decides something. You can disagree, but ultimately you might have to execute.
In these cases, be transparent: "We're doing this for strategic reasons, not because it scored highest."
The Real Prioritization Skill
Frameworks are scaffolding. The real skill is judgment.
Judgment means:
- •Understanding the business context
- •Knowing what matters strategically
- •Balancing short-term and long-term
- •Making tradeoffs under uncertainty
- •Being decisive when evidence is incomplete
You build judgment through experience. Frameworks can help you think, but they can't think for you.
The Bottom Line
Use frameworks. They're useful tools.
But don't confuse the framework with wisdom. The numbers don't make decisions—you do.
The best PMs use frameworks as inputs to judgment, not substitutes for it.
Related reading: Saying No as a PM and Writing PRDs.