A roundup of the five frameworks PMs reach for most: RICE, ICE, Weighted Scoring, Impact/Effort, and Kano. Pick the lightest one that produces a defensible decision.
Last updated: 2026-04-01
Designed for speed. Score in seconds, sort the result, move on. ICE uses Impact x Confidence x Ease on a 1-10 scale. Impact/Effort is a 2x2 matrix you fill out in a workshop.
Best for early-stage teams, growth experiments, and any moment when the cost of a slightly wrong decision is less than the cost of a long deliberation.
Designed for defensibility. RICE was created by Sean McBride at Intercom and uses Reach, Impact, Confidence, and Effort. Weighted Scoring is a custom matrix where you pick the criteria.
Best for mature teams, cross-functional initiatives, and any moment when stakeholders will scrutinize the priority order.
ICE = Impact x Confidence x Ease (each 1-10). Impact/Effort = 2x2 grid.Both are subjective by design. The strength is speed. ICE was developed by Sean Ellis. Impact/Effort traces back to action priority matrices in operations research.
RICE = (Reach x Impact x Confidence%) / Effort. Weighted = sum of (criterion score x weight).RICE grounds the score in user reach data. Weighted Scoring grounds it in strategic weights set by leadership.
| Criteria | Lightweight | Structured |
|---|---|---|
| Speed | Seconds to minutes per item | Minutes to a quarter-hour per item |
| Data needed | None beyond team judgment | Reach analytics (RICE) or strategic weights (Weighted) |
| Best backlog size | Under 20 items | 30 to 100+ items |
| Defensibility | Lower. Subjective inputs | Higher. Math is in the open |
| Stakeholder fit | Internal team | Cross-functional, leadership, investors |
| Where they break | Long backlogs, contentious decisions | Tiny teams, no analytics, fast iteration |
| Origin | ICE: Sean Ellis. Impact/Effort: action priority matrix | RICE: Sean McBride at Intercom. Weighted: long history in operations |
| Pairs well with | Each other; Kano for strategy | Each other; Kano for strategy |
Pros
Cons
Pros
Cons
Score your own data with both frameworks. Compare results and pick the one that fits your team.
ICE if you have data and time. Impact/Effort if you don't. Both produce a decision faster than RICE or Weighted Scoring. Move to RICE once you have analytics for Reach. Move to Weighted Scoring once your strategy outgrows the four RICE factors.
Yes, and most teams do. Impact/Effort for the workshop, RICE for the formal backlog, Kano for strategy decisions. Each framework answers a different question. Stack them, don't replace one with another.
RICE adds a Reach component that ICE doesn't have. RICE uses mixed scales (numbers, percentages, person-months). ICE uses a uniform 1-10 scale. RICE is more rigorous and slower. ICE is faster and more subjective.
When two of your most important items can't be distinguished by Reach, Impact, Confidence, and Effort alone. If "regulatory risk" or "platform investment" is the deciding factor, you've outgrown RICE and need Weighted Scoring. Adding a fifth factor to RICE turns it into Weighted Scoring anyway.
Sort of. Kano sorts features into satisfaction categories (must-be, performance, attractive, indifferent, reverse) based on user surveys. It tells you what to invest in but not the order to ship. Pair it with RICE or Weighted Scoring to get from category to ranked list.
Different frameworks for different sizes. ICE and Impact/Effort handle 50 items in a workshop. RICE handles 30 to 100 items as a longer scoring exercise. Weighted Scoring is best for 3 to 15 finalists, often after RICE has filtered the backlog.
Trust the framework. Then question the inputs. If the score puts an item at the top that everyone in the room knows is wrong, the inputs are wrong. Re-score, don't override. Persistent gut overrides defeat the purpose of having a framework.