GraphedMinds
The Startup Ideas Podcast

The Startup Ideas Podcast

The best businesses are built at the intersection of emerging technology, community, and real human needs.

Back to Frameworks

ICE Score Feature Prioritization

Reusability

A scoring system for prioritizing product features using Impact × Confidence ÷ Effort to determine what to build next

How It Works

Forces teams to quantify expected impact, confidence in assumptions, and development effort for each feature idea to create objective prioritization scores

Components

1

List all potential feature ideas

2

Rate Impact (1-10): How much will this move key metrics?

3

Rate Confidence (1-10): How sure are you this will work?

4

Rate Effort (1-10): How much development time needed?

5

Calculate: (Impact × Confidence) ÷ Effort

6

Rank by score and ship top 3 per week maximum

When to Use

When you have multiple feature ideas competing for development resources and need to focus on highest-value work

When Not to Use

For urgent bug fixes, compliance requirements, or when you have unlimited development capacity

Anti-Patterns to Avoid

Building features without scoring them firstShipping more than 3 things per weekLetting subjective preferences override data-driven scores

Example

Mobile app team has 10 feature ideas: push notifications score 8×9÷3=24, social sharing scores 6×5÷8=3.75, leaderboards score 7×8÷4=14. Build push notifications first.

Related Knowledge