PM World/Feature Prioritization

📊 Feature Prioritization

Product managers face infinite feature requests but finite resources. Prioritization frameworks provide structured methods to evaluate and rank features objectively. No single framework is perfect — experienced PMs combine multiple frameworks and layer in judgment. The goal is not mathematical precision but disciplined thinking that reduces bias.

Prioritization Frameworks

RICE

Reach × Impact × Confidence ÷ Effort — quantitative scoring for backlog items

MoSCoW

Must Have, Should Have, Could Have, Won't Have — categorical prioritization

Kano Model

Basic, Performance, Excitement — categorizes features by user satisfaction impact

ICE

Impact × Confidence × Ease — simpler alternative to RICE for rapid scoring

Real-World Example

Intercom uses RICE scoring for their product roadmap. When they had to choose between building a chatbot feature and improving their existing inbox, RICE scoring revealed the chatbot had 10x the reach but lower confidence. They chose to prototype the chatbot first (reducing confidence risk) before committing to full development — a nuanced use of the framework.