Use RICE for comparable roadmap initiatives with measurable reach, ICE for fast experiment ordering, MoSCoW for fixed-scope delivery, Kano for customer satisfaction research, value-versus-effort for workshop triage, and weighted scoring for decisions with several explicit criteria.
- A framework should match the decision type and available evidence.
- Mandatory work should be gated before optional initiatives are ranked.
- Combining every framework usually adds arithmetic without adding clarity.
Framework comparison
Choose based on the uncertainty you need to reduce. No method can repair unclear strategy or invented evidence.
| Situation | Use | Why |
|---|---|---|
| Quarterly roadmap with reach estimates | RICE | Normalizes impact by reach, confidence, and effort. |
| Fast growth experiment backlog | ICE | Works before reach is known and is quick to update. |
| Fixed deadline or release scope | MoSCoW | Makes minimum viable scope and deferrals explicit. |
| Understanding satisfaction response | Kano | Separates expected basics from performance needs and delighters. |
| Early workshop triage | Value vs. effort | Creates a fast visual map and surfaces disagreement. |
| Several business criteria must stay visible | Weighted scoring | Makes criteria and their relative importance explicit. |
A simple decision sequence
Answer these questions in order. Stop as soon as one clearly describes the decision.
- Is the item mandatory for safety, law, security, or a binding commitment? Gate it before ranking optional work.
- Are you negotiating what fits into a fixed release? Use MoSCoW.
- Are you studying how features affect customer satisfaction? Use Kano research.
- Can you estimate comparable reach and effort? Use RICE.
- Are you ordering small experiments quickly? Use ICE.
- Do several criteria need explicit weights? Use weighted scoring. Otherwise start with value versus effort.
When to combine methods
Combine methods only when each has a distinct job. Relay might use MoSCoW to define the non-negotiable enterprise pilot, then RICE to rank optional activation work outside that pilot. It might use Kano findings as one input to a weighted score. It should not multiply an ICE score by a RICE score; the overlapping assumptions create impressive-looking noise.
Common mistakes
- Choosing the framework with the most columns because it looks rigorous.
- Using a reach-based method when reach estimates are mostly invented.
- Changing frameworks until a preferred initiative reaches the top.
- Mixing mandatory commitments into the same score as optional ideas.
Check your understanding
A team must decide what fits into a release due in six weeks. Reach estimates are weak. Which method is the best starting point?
MoSCoW, because the immediate problem is negotiating fixed-time scope, not estimating broad reach.
Sources
- Intercom: RICE prioritizationReference for RICE inputs and scoring.
- Agile Business Consortium: MoSCoW prioritisationReference for timeboxed scope categories.
- Kano et al.: Attractive Quality and Must-Be QualityPrimary source for the Kano quality categories.