Skip to content
Free tools

Score your features using RICE, ICE, or Value vs Effort. Get an auto-ranked priority list you can export.

Scoring framework

Reach x Impact x Confidence / Effort

Add features above to start scoring and ranking them.

All scores use a 1-10 scale.

Frameworks Explained

RICE Scoring

Reach x Impact x Confidence / Effort. Sean McBride and the team at Intercom created RICE because they needed a way to compare very different feature ideas on the same scale. The multiplication means a feature that scores high on all three value dimensions but takes little effort will dominate the ranking. It's the go-to for teams that want numbers they can point to in a planning meeting.

ICE Scoring

(Impact + Confidence + Ease) / 3. ICE treats all three dimensions as equally important and averages them. "Ease" is the flip side of effort - a 10 means it's trivial to build. Because it's an average instead of a product, the scores cluster tighter together. Good for quick triage when you need a rough ranking and don't want to debate exact numbers.

Value vs Effort

(Reach + Impact) / 2 / Effort. The simplest of the three. It boils down to one question: how much value per unit of effort? Features that are high-value and cheap to build float to the top. Small teams and early-stage products tend to gravitate here because it requires the fewest judgment calls.

Frequently Asked Questions

Common questions about feature prioritization frameworks.

Have more questions?

RICE stands for Reach, Impact, Confidence, and Effort. Sean McBride and the product team at Intercom built it because they needed a way to compare wildly different feature ideas on equal footing. The formula multiplies Reach, Impact, and Confidence, then divides by Effort.

Depends on your team and how much data you have. RICE works well when you can estimate reach numbers and have confidence levels to back up your guesses. ICE is faster for quick triage - good when precision isn't critical. Value/Effort is the simplest option, great for small teams or hackathon-style planning.

No, and don't try. A RICE score of 25 and an ICE score of 7.3 live on completely different scales. Pick one framework per prioritization session and stick with it. You can always re-run the same features through a different framework later.

There's no universal standard. For Reach, a 10 might mean "all active users" while a 1 means "a handful of power users." For Impact, think about how much the change matters to those affected. The key is that your team agrees on what each level means before you start scoring.

Ties happen often, especially with ICE since it averages just three numbers. When two features tie, go with the one that has lower effort - it'll ship faster and give you real data sooner. Or just pick the one your team has stronger conviction about.

Updated March 2026