Prioritization fails when teams rank ideas by loudest stakeholder or nearest deadline instead of outcome impact. Good prioritization makes tradeoffs explicit and repeatable.
Inputs to prioritization:
- Impact: expected user/business value
- Effort: engineering/design complexity
- Confidence: quality of evidence
- Risk: execution and dependency uncertainty
RICE framework:
- Reach: users affected in a time window
- Impact: magnitude of outcome change
- Confidence: certainty in assumptions
- Effort: required team time
RICE works well for comparing growth and optimization initiatives with measurable user volume.
MoSCoW framework:
- Must have
- Should have
- Could have
- Won’t have (this cycle)
MoSCoW is useful for release planning where deadline constraints are fixed.
Kano framework:
- Basic expectations
- Performance features
- Delighters
Kano helps balance hygiene work and differentiators in customer experience decisions.
Choosing the right framework:
- Use RICE for quantitative portfolio ranking
- Use MoSCoW for scope control in fixed delivery windows
- Use Kano for user satisfaction strategy
Example prioritization table (condensed):
- Initiative A: onboarding fix, high reach, medium effort -> high rank
- Initiative B: advanced customization, low reach, high effort -> low rank
- Initiative C: reliability improvement, moderate reach but high risk reduction -> medium-high rank
Communicating tradeoffs:
- Share the criteria, not just the ranking
- Document what is explicitly deferred and why
- Revisit scores when new evidence appears