RICE Prioritization
RICE ranks product initiatives by combining estimated reach, impact, confidence, and effort in a comparable score.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/rice-prioritization/
01What it means
RICE is a prioritization framework developed at Intercom to make competing product ideas easier to compare. Its name represents four inputs: reach, impact, confidence, and effort. The score is a decision aid, not an objective measure of value.[1][2]
- Reach
- How many in the chosen period
- Impact
- Expected effect per person
- Confidence
- Strength of the evidence
- Effort
- Total work required
Use consistent periods, scales, and effort units. The result supports judgment; it does not replace strategy.
02Why it matters
Product teams often compare ideas using inconsistent arguments: one proposal emphasizes customer demand, another strategic importance, and another implementation speed. RICE creates a shared structure for exposing those assumptions and discussing where estimates are weak.
03When to use it
Use RICE when a backlog contains several initiatives that can be estimated over the same time horizon and the team needs a transparent first-pass ranking. It is especially useful before roadmap discussions, not as an automatic roadmap generator.
04How it works
- Choose a consistent period and estimate how many users or events each initiative will reach.
- Estimate the impact on the chosen outcome using a clearly defined scale that is shared across all candidates.
- Assign confidence to reflect the strength of the evidence behind the reach and impact estimates.
- Estimate total effort across the people and disciplines required, using the same unit for every initiative.
- Calculate the score as reach multiplied by impact and confidence, divided by effort, then review the ranking alongside strategy and dependencies.
05A practical example
A team compares an onboarding checklist with a major account-settings redesign. The checklist reaches more new users, has moderate evidence from usability tests, and requires less effort, so its RICE score is higher. The team schedules it first but keeps the redesign because it addresses an important enterprise commitment that the score does not capture.
06Where it breaks
RICE can create false precision from uncertain inputs, favor broadly distributed incremental work over necessary infrastructure, and underrepresent strategic commitments or risk reduction. Scores are only comparable when teams use consistent definitions, time windows, and effort units.
Common mistakes
- Treating decimal scores as precise facts rather than estimates.
- Using different reach periods or effort units across candidates.
- Letting a high score override legal, ethical, strategic, or dependency constraints.
07Sources
- RICE: Simple prioritization for product managersIntercom · Original framework articleRICE: Simple prioritization for product managers
- RICE Prioritization Framework for Product ManagersIntercom · Practitioner guideRICE Prioritization Framework for Product Managers