Every Framework Is Wrong. Some Are Useful.
RICE, MoSCoW, OKRs, JTBD. None of them capture reality. All of them beat gut instinct.
Product management has more frameworks than any discipline needs. RICE scoring. ICE scoring. MoSCoW prioritization. WSJF. Kano analysis. Opportunity Solution Trees. Jobs to be Done. Story mapping. Impact mapping. The list grows every year.
Here is the truth: every one of these frameworks is a simplification. RICE reduces a complex prioritization decision to four numbers. OKRs compress an entire strategy into objectives and key results. The Kano model sorts features into five categories as if customer preferences were that clean. Reality is messier than any framework can capture.
But here is the other truth: using a framework, any framework, beats using nothing. Without a structured approach, prioritization becomes a political exercise. The loudest stakeholder wins. The most recent customer complaint gets built. The CEO's pet project jumps the queue. Frameworks create a shared language and a repeatable process that makes decisions more transparent, even when they are imperfect.
The mistake is treating frameworks as truth instead of tools. RICE does not tell you the correct priority. It tells you one way to think about priority. Use it as a starting point for conversation, not an ending point for debate. The score is less important than the discussion it creates about reach, impact, confidence, and effort.
The best PMs use multiple frameworks as lenses. They might RICE-score a feature set, then map it against OKRs, then pressure-test with JTBD interviews. Each framework reveals something the others miss. None of them are right. All of them are useful.
“The score is less important than the discussion it creates about reach, impact, confidence, and effort.”
When this goes wrong
Treating RICE scores as absolute truth. Spending more time debating the framework than the actual decision. Using a framework to justify a decision you already made. Framework paralysis: trying five different methods and picking the one that supports your bias.
In practice
- ✓Pick one primary framework for prioritization, but validate with a second lens
- ✓Use frameworks to structure discussion, not end it
- ✓Document when you override a framework score, and why
- ✓Teach your team the framework so decisions are transparent