ICE Scoring: Prioritize Features with a Quick Gut Check
ICE scoring is a gut-check for prioritizing features by multiplying Impact, Confidence, and Ease. It helps teams rapidly sort experiments or backlog items. The main footgun is its bias towards easy wins, potentially ignoring high-effort strategic projects.
Why it exists
Teams need a way to quickly decide what to work on next from a long list of ideas. Without a framework, decisions can be chaotic. ICE was created by Sean Ellis for "growth hacking" experiments, where the speed of iteration is more important than rigorous, upfront analysis.
The mental model
Think of ICE as a structured gut-check, not a scientific formula. It forces you to answer three questions for any idea: How much will this matter (Impact)? How sure are we (Confidence)? And how hard is it to do (Ease)? Multiplying the scores gives a single number for quick, relative comparison.
How it works
For each feature, you assign a score from 1 to 10 for three variables. First, Impact: how much will this move a key metric? Second, Confidence: how certain are you about your Impact and Ease scores? Third, Ease: how simple is this to implement, with 10 being very easy and 1 being very difficult. The final score is Impact Confidence Ease. The item with the highest score gets prioritized.
When to use it
Use ICE for quick, relative prioritization when speed is essential. It's great for choosing between a few competing ideas or getting a rough first-pass sort of a large backlog, especially for growth teams that need to run many small experiments.
When not to use it
Avoid using ICE as your sole framework for major strategic initiatives. Its biggest flaw is its bias towards "low-hanging fruit." A difficult but transformative project will get a low 'Ease' score, tanking its rank. The model is also highly subjective; two people can score the same item very differently. For more rigor, consider a weighted scoring model or the RICE model, which adds 'Reach'.
One canonical example
A team considers two features. Feature A has a high Impact of 9 and high Confidence of 7, but is very difficult to build (Ease score of 2). Its ICE score is 9 7 2 = 126. Feature B has a lower Impact of 7 and lower Confidence of 6, but is much easier to implement (Ease score of 5). Its score is 7 6 5 = 210. Despite its lower potential impact, Feature B gets prioritized because it's significantly easier to deliver.
Interview question
What is a significant drawback of relying solely on ICE scoring for product prioritization?
- a.It requires a large amount of historical data to accurately score features.
- b.It often leads to over-analysis, delaying decision-making.
- c.It inherently favors quick, easy wins over potentially transformative, complex projects.Correct
- d.It does not incorporate the team's certainty about the estimated impact.
Why? this is the answer
The card highlights that ICE's biggest flaw is its bias towards 'low-hanging fruit' and that difficult but transformative projects will get a low 'Ease' score, tanking their rank. Option B is incorrect because ICE is designed for rapid, gut-check prioritization, not extensive analysis.
Just read this? Test yourself on what you have been reading.
Read the original → productplan.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on product — each one lists the topics its interview covers.
See open roles