capability-prioritization

RICE scoring multiplies Reach (1-10), Impact (0.5-3), and Confidence (20%-100%), then divides by Effort in person-weeks (0.5-10). Higher scores indicate capabilities delivering more value per unit of work, ranking them earlier in the roadmap.

MoSCoW categorizes features into Must, Should, Could, and Won't buckets based on criticality, while RICE produces a numeric score from reach, impact, confidence, and effort. Using both together gives categorical clarity plus quantitative ranking.

Capabilities with value above 7 and complexity below 4 are Quick Wins to do first. High value with high complexity are Strategic Bets, low value with low complexity are Fill-ins, and low value with high complexity are Time Sinks to avoid.

Use the Kano model to classify features as Basic, Performance, Excitement, Indifferent, or Reverse based on customer satisfaction impact. It complements scoring frameworks by revealing which features users expect versus which delight them.

A confidence score below 0.8 means too many inputs are unknowns or guesses, so the ranking is unreliable. Scores of 1.0 indicate fully data-backed inputs, while 0.8-0.9 reflect reasonable estimates with some educated guesses.