ICED: Balanced Prioritization Framework
ICED is a balanced prioritization framework that scores features on Impact, Confidence, Ease, and Delight—explicitly factoring customer joy into the prioritization equation alongside business value.
What Is It?
ICED is a prioritization framework that emerged from the product management community around 2010. It evaluates features across four dimensions: Impact, Confidence, Ease, and Delight.
What distinguishes ICED from RICE is the addition of the "Delight" factor, which attempts to capture the emotional or experiential impact on users—not just the business value. This makes it particularly useful for consumer products where user experience is a key differentiator.
The framework strikes a balance between quantitative rigor (like RICE) and customer-centricity (like Kano) while remaining relatively quick to apply.
Quick Reference
Core Features
- Impact: Business value and strategic importance (1-10 scale)
- Confidence: How certain are you about your estimates? (1-10 scale)
- Ease: Inverse of effort—how easy is this to implement? (1-10 scale)
- Delight: Will this create customer joy? (1-10 scale)
- ICED Score = Impact × Confidence × Ease × Delight
- Balances business value with user experience
- Faster than Kano, more nuanced than Value/Effort
When to Use
- Consumer products where UX matters
- Balancing business needs with user delight (more explicitly than RICE)
- Teams that want more nuance than Value vs Effort
- When you don't have time for full Kano analysis
- Products competing on experience
- Feature prioritization with cross-functional input
- When you want to explicitly value customer delight
When NOT to Use
- Pure B2B tools where delight is less relevant (use RICE instead)
- Emergency fixes or critical bugs (use Priority Matrix)
- When you have strong customer research (use Kano instead)
- Very early stage with high uncertainty
- Internal tools with captive users (use MoSCoW)
Key Strengths
- Incorporates customer delight explicitly
- Faster than Kano while more balanced than RICE
- Four dimensions provide good coverage
- Works well for consumer products
- Encourages discussion about user experience
Key Weaknesses
How It Works
| 1 Primary Input | List of features or initiatives to prioritize |
|---|---|
| 2 Data You Need | Numerical estimates (1-10) for Impact, Confidence, Ease, and Delight |
| 3 Primary Output | Single score per item (I × C × E × D), enabling a ranked priority list |
Comparison with Related Frameworks
ICED bridges the gap between business-focused RICE and customer-focused Kano. Here's how it compares:
ICED vs RICE
RICE Score uses Reach instead of Delight and divides by Effort (vs ICED's Ease multiplication). Use RICE when reach metrics matter, ICED when customer delight is a key differentiator.
ICED vs MoSCoW
MoSCoW is faster and categorical, while ICED provides numerical rankings. Use MoSCoW for quick scope decisions, ICED when you need ranked priorities with delight consideration.
ICED vs Kano
Kano Model validates delight through customer research, while ICED estimates it. Use Kano when you can invest 3-4 weeks in research, ICED for faster team-based assessment.