A prioritization scoring framework that ranks opportunities by four factors: Reach (how many users are affected), Impact (how much it improves the experience per user), Confidence (how certain the team is in its estimates), and Effort (how much work is required). RICE scores create a defensible, consistent basis for prioritization discussions that would otherwise devolve into subjective debate.
Common contexts
- Scoring a backlog of twelve feature requests before a quarterly roadmap planning session to create a ranked, defensible priority list
- Using the Confidence score to flag that a high-RICE item is based on a single stakeholder assumption rather than validated user data
- Recalculating RICE after a usability study upgrades the Impact estimate for an accessibility fix that was previously deprioritised
Use when
Use RICE when a team has more good ideas than capacity and needs a shared, repeatable method for ranking them — particularly when stakeholder seniority or loudness is currently driving prioritization rather than user evidence.
Avoid when
Don't use RICE to create false precision around decisions that are fundamentally strategic — a product direction choice between two market segments can't be resolved by scoring, and applying the framework to it gives numerical legitimacy to what is really a values-based decision.
The Confidence multiplier is the most honest part of RICE — teams that consistently assign 100% confidence to every item are using the framework as a post-hoc justification tool rather than a genuine prioritisation one.
Real-world examples
- Intercom publicly documented their RICE scoring framework in 2016 and credits it with reducing roadmap debates from multi-hour arguments to 30-minute structured scoring sessions across their product organisation.
- Linear, the project management tool, uses RICE scoring internally for feature prioritisation, with product managers assigning Reach estimates from user research and Effort estimates from engineering leads.
- A growth team at Dropbox used RICE to deprioritise a referral programme redesign (high effort, uncertain impact) in favour of a simpler email reminder flow (low effort, high reach), increasing referrals by 8% with less engineering.