A visual 2x2 matrix or a four-factor score. Both rank product ideas, but they answer different questions and fit different moments in a quarter.
Last updated: 2026-04-01
A 2x2 matrix that plots each item by how much value it creates and how hard it is to deliver. The four quadrants are quick wins, big bets, fill-ins, and thankless tasks.
Best for stakeholder workshops, early roadmap shaping, and any moment you need a decision in the next hour.
Created by Sean McBride at Intercom, RICE turns each item into a numeric score from Reach, Impact, Confidence, and Effort. The output is an ordered list, top to bottom.
Best for teams that need to defend a priority order to leadership or other PM teams.
No formula. Place each item on the grid and discuss the quadrant.The output is a grouping, not a ranked list. The strength is the conversation about where each item belongs.
RICE = (Reach x Impact x Confidence%) / EffortReach is users affected per quarter. Impact is a 0.25 to 3 multiplier. Confidence is 50% to 100%. Effort is in person-months.
| Criteria | Impact/Effort | RICE |
|---|---|---|
| Output | Quadrant grouping | Numeric score, top-to-bottom rank |
| Inputs | Two axes: impact and effort | Four factors: Reach, Impact, Confidence, Effort |
| Time per item | Under a minute in a workshop | 5 to 15 minutes the first time |
| Backlog size | Best for 5 to 20 items | Handles 30 to 100 items |
| Best setting | Live workshop with stakeholders | Async scoring, document-driven |
| Tie-breaking | Discussion, not numbers | The math gives you order |
| Data needed | Rough estimates, gut calls | Reach data from analytics is helpful |
| Easy to communicate | Very high. Anyone reads the chart | Moderate. Score requires explanation |
Pros
Cons
Pros
Cons
Score your own data with both frameworks. Compare results and pick the one that fits your team.
No. If your backlog is short and stakeholders are aligned, the 2x2 is faster and produces the same decision. Reach for RICE when the backlog is too long for a workshop or when leadership wants to see the math.
Yes, and many teams do. Drop the thankless tasks and most fill-ins from the 2x2. Then run RICE on the survivors. You save the 5 to 15 minutes per item that RICE costs by triaging first.
No. Reach is how many people the change touches. Impact is how much it changes things for each one. A bug fix on a checkout page can be high Reach and high Impact. A new feature for power users can be high Impact and low Reach.
Define what "high" means before the workshop. Use a number for effort, like "more than two sprints is high" and a number for impact, like "moves a target metric by more than 5% is high". Then place items against those thresholds, not your gut.
Both, at different stages. Most teams use Impact/Effort early in a quarter to shape direction, then RICE to order the backlog they actually plan to ship. The frameworks are complements, not competitors.