RICE scoring is a prioritization framework that assigns a numerical score to each feature or initiative so teams can compare options without relying purely on gut feel.
The formula is: (Reach x Impact x Confidence) / Effort. Reach is how many users are affected per quarter. Impact is a multiplier (3 = massive, 0.25 = minimal). Confidence is a percentage of how certain you are about your estimates. Effort is person-months to ship. Higher score means higher priority.
When it's useful
RICE works best when you have a large backlog and need a starting point for prioritization conversations. The real value isn't the number. It's the process of writing down assumptions. When you fill in the inputs, you'll often find the team disagrees on what "Reach" even means. That conversation is where the clarity comes from.
Where it breaks down
RICE rewards high-reach, low-effort work. That consistently deprioritizes foundational fixes that matter deeply to your best users but don't touch many accounts. Confidence scores are also largely invented. Being precise about things you're uncertain about is a limitation, not a feature.
Use RICE alongside customer feedback from your roadmap. Don't treat the score as a verdict.