Ehsan Jahandarpour
ICE Scoring FrameworkSaaSSeries A

ICE Scoring Framework: ICE for Product Feature Prioritization

Adapting ICE scoring to prioritize product features and improvements based on their expected impact on key metrics.

How to Apply

1

Impact = expected improvement to North Star Metric if feature is successful.

2

Confidence based on user research, data analysis, and competitive evidence.

3

Ease = engineering effort in story points or days. Include testing and deployment.

4

Calculate average ICE score. Weight toward high-impact items.

5

Top ICE items form the product roadmap. Review monthly.

Expected Outcomes

  • ✓ Evidence-based product roadmap
  • ✓ Better engineering resource allocation
  • ✓ Higher feature success rate

Real-World Examples

Common Pitfalls

⚠Ease scores that are too optimistic
⚠Not validating impact estimates with actual data

Ehsan's Insight

Using ICE for product feature prioritization reveals a consistent bias: product managers inflate Ease scores for features they personally want to build. Instagram's growth team solved this by separating ICE scoring into two groups — PMs scored Impact and Confidence, while engineering leads scored Ease independently, without seeing the other scores first. When combined, the rankings shifted dramatically: 40% of "top priority" features dropped to the bottom third. The other fix: time-box Ease strictly. Instead of "how hard is this?" (which is subjective), ask "can a single engineer ship this in under one sprint?" If yes, Ease = 8+. If it requires cross-team coordination, Ease = 3 maximum. This binary approach eliminates the 4-6 range where all the self-deception lives.

EJ

Ehsan Jahandarpour

AI Growth Strategist & Fractional CMO

Forbes Top 20 Growth Hacker · TEDx Speaker · 716 Academic Citations · Ex-Microsoft · CMO at FirstWave (ASX:FCT) · Forbes Communications Council

Frequently Asked Questions

When should I use ICE Scoring Framework for product features?
Adapting ICE scoring to prioritize product features and improvements based on their expected impact on key metrics.
What are the steps in ICE for Product Feature Prioritization?
There are 5 key steps: Define impact criteria, Assess confidence levels, Estimate ease accurately, Score and prioritize, Build roadmap from scores.
What results can I expect from ICE for Product Feature Prioritization?
Evidence-based product roadmap. Better engineering resource allocation. Higher feature success rate.
What are common mistakes with ICE for Product Feature Prioritization?
Ease scores that are too optimistic. Not validating impact estimates with actual data.
Can I combine ICE Scoring Framework with other frameworks?
Yes, ICE Scoring Framework works well with other growth frameworks. Many teams combine it with AARRR metrics and ICE scoring for a comprehensive growth system.