Definition
ICE Scoring
ICE is a lightweight prioritization framework that scores each idea on three factors — Impact (how much it will move the goal), Confidence (how sure you are in the estimate), and Ease (how simple it is to implement) — usually on a 1–10 scale. The ICE score is Impact × Confidence × Ease, giving a fast, comparable number for ranking competing experiments.
Key takeaways
- ICE scores ideas as Impact × Confidence × Ease (each ~1–10), giving a fast, comparable number for ranking experiments.
- It was popularized by Sean Ellis for triaging growth experiments quickly — only three inputs, so a long list scores in minutes.
- The Confidence factor discounts speculative bets, pulling hoped-for impact below smaller ideas backed by evidence.
- Its weakness is subjectivity; it's best for rapid triage, with teams graduating to RICE (which adds Reach) for higher-stakes roadmap calls.
ICE was popularized by Sean Ellis, the originator of growth hacking, as a way to triage growth experiments quickly at companies like Dropbox and LogMeIn. Each candidate is rated on Impact, Confidence, and Ease — typically 1 to 10 — and the three are multiplied. Because it needs only three inputs, a team can score a long list of ideas in minutes and sort by the result, which is exactly what makes it popular with fast-moving growth and experimentation teams.
The Confidence factor is what distinguishes ICE from a naive impact-versus-effort ranking. It discounts ideas whose impact is merely hoped for, pulling speculative bets down below smaller ideas backed by evidence. Ease, meanwhile, keeps the framework biased toward quick wins — the experiments most likely to deliver a learning soon rather than the biggest swing that takes a quarter.
ICE's weakness is its subjectivity. The same idea can score very differently depending on who rates it, and few people hold enough context to judge Impact, Confidence, and Ease all at once — Impact and Confidence are business calls while Ease is technical. It is best treated as a conversation-forcing tool for rapid triage, not a precise ranking; for higher-stakes roadmap decisions, teams often graduate to RICE, which adds an explicit Reach term.
Planoda can store ICE inputs as structured fields on issues and initiatives and rank them automatically, so experiment triage stays transparent and recomputes as confidence changes.
Related terms
- RICE PrioritizationRICE is a prioritization framework that scores each initiative by Reach (how many people it affects), Impact (how much it moves the needle per person), Confidence (how sure the estimates are), and Effort (the work required). The score is Reach × Impact × Confidence ÷ Effort, producing a comparable number that ranks competing ideas by expected value per unit of work.
- WSJF (Weighted Shortest Job First)WSJF is a prioritization model from SAFe that sequences work for maximum economic benefit by dividing the Cost of Delay by the job's duration or size. The shortest jobs with the highest cost of delay rank first. Cost of Delay itself sums user/business value, time criticality, and risk reduction or opportunity enablement, each scored on a relative scale.
- MoSCoW PrioritizationMoSCoW is a prioritization method that sorts requirements into four categories — Must have, Should have, Could have, and Won't have (this time). The capitalized letters form the name; the lowercase o's make it pronounceable. It forces a team to agree explicitly on what is essential versus deferrable, rather than treating every request as equally urgent.
- Kano ModelThe Kano model classifies product features by how their presence or absence affects customer satisfaction, sorting them into five types: Must-be (basics expected by default), Performance (more is better), Attractive (delighters), Indifferent (no effect either way), and Reverse (please some, annoy others). Its core insight is that satisfaction is asymmetric — a missing basic angers users while its presence earns no credit.
- North Star MetricA North Star metric is the single measure that best captures the core value a product delivers to customers — and that, when it grows, reliably pulls revenue and retention up with it. It aligns an entire company on one number, cutting through competing departmental metrics so every team can see how its work moves the thing that matters most.