ICE scoring is the fastest way to rank a backlog. Three numbers per feature, one multiplication, done. For Shortcut teams that want structured prioritization without the overhead of heavier frameworks, ICE hits the right balance.
This guide shows you how to run ICE scoring alongside Shortcut to stop guessing and start shipping the right things.
What ICE Scoring Does
ICE stands for Impact, Confidence, and Ease. Each is scored 1-10. Multiply the three together and you get your ICE score. Higher scores mean better bets.
- Impact: How much will this move your target metric?
- Confidence: How sure are you about the Impact and Ease estimates?
- Ease: How quickly can your team ship this?
ICE was popularized by Sean Ellis for growth experiments, but it works for any backlog. The simplicity is the point. You can score 30 items in 20 minutes.
ICE vs. RICE: Which Fits Shortcut Better?
RICE adds a Reach dimension and divides by Effort. It is more precise but takes longer. ICE works best when your user base is relatively uniform (so Reach is similar across features) or when you want to move fast.
For early-stage teams on Shortcut, ICE is usually the better starting point. You can graduate to RICE or weighted scoring once your product and user base become more complex.
Setting Up ICE in Shortcut
Step 1: Create Custom Fields. In Shortcut, add three Custom Fields to your Stories: "Impact" (number, 1-10), "Confidence" (number, 1-10), and "Ease" (number, 1-10). Optionally add a fourth field for the calculated "ICE Score."
Step 2: Score your backlog. Pull up the ICE Calculator alongside your Shortcut board. For each candidate Story, assign Impact, Confidence, and Ease values. Enter them into the calculator and paste the result into Shortcut.
Step 3: Create a scored view. Save a Shortcut search filtered to Stories with ICE Score > 0, sorted descending. This becomes your prioritized backlog view.
Step 4: Use scores in planning. During Iteration planning, pull from the top of the scored list. When stakeholders ask "why this feature first?", point to the ICE score breakdown.
Calibrating ICE Scores Across Your Team
The biggest risk with ICE is inconsistent scoring. One engineer's "8 Impact" is another's "5." Fix this with a calibration session.
Pick 5 shipped features your team agrees on. Score them together. Use those as reference points. "The checkout redesign was a 9 Impact. Is this new feature really an 8, or is it more like a 5?"
Write the reference scores in a shared doc and link it from your Shortcut workspace description. New team members can calibrate against real examples instead of guessing.
Shortcut Workflow Tips
Use Shortcut's Label system to track scoring status. Create labels for "needs-scoring," "scored," and "re-score-needed." This prevents features from entering an Iteration without a score.
Group your scored Stories by Epic to see which strategic bets have the highest-scoring items. If an Epic's Stories all score below 100, question whether that Epic belongs in your roadmap.
Connect your Iteration velocity data to ICE scores. After each sprint, check whether you shipped high-ICE or low-ICE items. If low-scoring items keep jumping the queue, your planning process has a discipline problem, not a scoring problem.
Explore roadmap templates if you need to connect Shortcut Iteration plans to a longer-term product roadmap.