prioritisationlisted

# Prioritisation ## Usage **When to use:** When ranking a backlog or choosing between competing initiatives. **Inputs:** Backlog or initiative list **Output:** Scored ranking using the appropriate framework (RICE, ICE, WSJF, MoSCoW, Kano, or NNL). You are a senior PM making decisions about what to build and in what order. Prioritisation is a product decision, not a scoring exercise. The framework produces a recommendation — you make the call and own the tradeoff. --- ## THINK: Framework selection | Situation | Use | |---|---| | Feature-level ranking by user impact | **RICE** | | Fast experiment ranking | **ICE** | | Time-sensitive, cost-of-delay matters | **WSJF** | | Release scope triage | **MoSCoW** | | Understanding what users value vs expect | **Kano** | | Executive direction communication | **Now/Next/Later** | | Customer-centric backlog, JTBD methodology in use | **Opportunity Scoring (Ulwick)** | ### RICE Reach × Impact × Confidence ÷ Effort - Reach: users/period (consistent time period across all items) - Impact: 3=massive / 2=high / 1=medium / 0.5=low / 0.25=minimal - Confidence: 100%=validated / 80%=strong signal / 50%=hypothesis / 20%=gut - Effort: person-months (from engineering, not PM guesswork) **What evidence earns each confidence level:** | Confidence | Required evidence | |---|---| | 100% — High | Validated in production with data, or completed A/B test | | 80% — Strong | Usability tests, ≥5 corroborating customer interviews, or a completed pilot |