ICE Calculator - Prioritize Features with Impact, Confidence, Ease

What is ICE? (Impact, Confidence, Ease)

ICE is a lightweight prioritization framework that ranks initiatives by three factors: Impact (how much this moves the needle on your goal), Confidence (how sure you are about your Impact and Ease estimates), and Ease (how straightforward it is to build). Multiply the three together to get an ICE score; higher scores get worked on first.

The ICE model was popularized by growth expert Sean Ellis, who coined the term "growth hacking" and founded GrowthHackers.com. Ellis introduced ICE as a fast way for growth teams to rank experiments when analytics were sparse and decisions had to be made quickly. Product managers have since adopted it as one of the go-to feature prioritization frameworks.

ICE keeps three inputs (versus RICE's four or WSJF's four), which is why teams reach for it when they need to sort a backlog in under 30 minutes. For a slower, more rigorous alternative, see the RICE calculator. For SAFe / large-Agile portfolios, the WSJF calculator models Cost of Delay explicitly.

The ICE Formula

Each input is scored on a 1 to 10 scale (this calculator allows 0.01 to 10 on Confidence so you can express "gut feel" bets as low as 0.05). The absolute number doesn't matter as much as the relative ranking across your backlog.

Note: Sean Ellis's original write-up on GrowthHackers.com used addition ("simply add up the scores to get the total Ice Score"). Modern product management practice almost universally multiplies the three components instead, because multiplication punishes low-confidence bets more aggressively and creates wider separation between strong and weak ideas. Both are considered canonical ICE today. This calculator uses the multiplicative version.

How to Calculate an ICE Score: Step by Step

1. Agree on the goal metric first. ICE only works when everyone scores Impact against the same target (revenue, activation rate, NPS, churn, whatever it is). Skip this and you're scoring apples against oranges.
2. Score Impact (1 to 10). How much will this move the goal metric? 1 to 3 = marginal, 4 to 6 = moderate, 7 to 9 = major, 10 = transformational. Use the FAQ below for a full rubric.
3. Score Confidence (0.01 to 10). How sure are you about the Impact and Ease numbers? 1 to 3 = gut feel only, 4 to 6 = some supporting data, 7 to 9 = validated by users or A/B tests, 10 = near certainty. If you have no data, do not score above 4.
4. Score Ease (1 to 10). How straightforward is delivery? 10 = shipped in under a week, 5 = a couple months, 1 = 26+ weeks. Note: this is Ease, not Effort. High Ease = low effort. If your team uses "Effort" in a spreadsheet, invert the formula.
5. Multiply the three: ICE = Impact × Confidence × Ease. This calculator does it automatically.
6. Sort your backlog by ICE score descending. The item at the top is your next candidate to work on. Re-score whenever new data changes Confidence (usually monthly is enough; do not re-score the whole backlog weekly).

ICE Worked Example: SaaS Backlog

Here's a small SaaS team ranking three candidate initiatives with ICE:

SSO wins with 288 despite being the hardest to build (Ease 4), because Impact (8) and Confidence (9) are both very high. The personalization idea ranks last mostly because Confidence is low (4 = benchmarks from other companies, not validated in-product). This is exactly what the Confidence factor is designed to surface. Get an interactive walkthrough plus a downloadable Excel version at the ICE prioritization template.

ICE vs RICE vs WSJF

ICE is the fastest of the three quantitative frameworks. Here's the trade-off:

Rule of thumb: use ICE when speed matters more than precision (weekly growth experiments, early-stage product). Switch to RICE once you have reliable Reach data. Adopt WSJF if you're operating inside SAFe or Cost of Delay is the dominant factor. For a side-by-side breakdown of all major frameworks, see the prioritization framework comparison and the deeper RICE vs ICE analysis. For team-scale ICE scoring with history, comments, and roadmap linking, use the ICE prioritization tool inside ProductLift.

Frequently Asked Questions