Prioritization

ICE Scoring · The Three-Factor Growth Prioritization Framework

Impact, Confidence, Ease — the lightweight scoring framework Sean Ellis built to prioritize a high-volume growth experiment backlog. The math, the use cases, and how it compares to RICE.

Attribution. ICE scoring was developed by Sean Ellis (the marketer who coined the term "growth hacker" and led growth at Dropbox, LogMeIn, and Eventbrite). Ellis published the framework via his GrowthHackers community in the 2010s. It is closely related to but distinct from Intercom's RICE.

The formula

ICE Score = Impact × Confidence × Ease

Each factor is scored 1–10 (or 1–5 in some variants), giving each item a single comparable number.

Higher scores get prioritized.

Why it works for growth experimentation

ICE is designed for high-volume A/B test backlogs where you might be evaluating 50–100 candidate experiments and need to decide which 5 to run this sprint. The simplicity is the feature — it takes 30 seconds per item, not 30 minutes.

The 1–10 scales are intentionally informal. The point is relative comparison, not precise estimation. "Is this more impactful than that?" is easier to answer than "how many MRR dollars will this produce?"

ICE vs RICE

AspectICERICE
Factors3 (Impact, Confidence, Ease)4 (Reach, Impact, Confidence, Effort)
Scale1–10 (or 1–5)Mixed (absolute reach, 0.25–3 impact scale, % confidence)
Best forHigh-volume growth experimentsProduct roadmap decisions
Speed per item~30 seconds~5–10 minutes
RigorLowerHigher

Use ICE for sprint-level experiment selection. Use RICE for quarter-level product roadmap decisions. They're complementary, not competing.

The biggest risk with ICE is confidence inflation. When everything scores 8/8/8, you have a list, not priorities. Force the team to spread scores — what's the 2/10 Impact thing on the list? What's a 9/10 Ease thing that someone could ship in a day?

Operating ICE on a real backlog

  1. Brainstorm without scoring. Generate 50–100 candidate experiments. Quantity first, judgment later.
  2. Score in batches. Score 10 items, take a break, calibrate, score the next 10.
  3. Sort by score. The top 5–10 are the candidates.
  4. Sanity-check the top of the list. Does the team actually believe these are the highest-leverage moves? If not, re-score the suspect ones.
  5. Pick the experiments for the sprint. Often 2–3, not all 10.
  6. After results, re-score the backlog with new information. Some 8/8/8 ideas become 8/3/8 when you learn confidence was wrong.

Related on RGM

Sources & further reading
  1. Ellis, S. (various, 2010–2017). On ICE scoring via GrowthHackers community and personal blog.
  2. Ellis, S. & Brown, M. (2017). Hacking Growth. Crown Business. (Formal ICE methodology.)
  3. GrowthHackers — community discussions and ICE templates.
  4. RGM operator notes — ICE applications in growth-team engagements 2023–2026.