prioritizelisted

# Prioritize Prioritization fails in two ways: a gut-feel ranking nobody can defend, or a precise-looking spreadsheet built on guesses. This skill avoids both. You pick the framework that fits the decision, define the scoring scale before you score anything, score every item against the same goal, then sanity-check the result against your gut. The number is an input to the call, not the call itself. **Grounded in:** *Escaping the Build Trap* — Melissa Perri: prioritize by outcome with RICE/Kano as inputs, not as the decision. **Go deeper (The Product Channel):** [6 Prioritization Frameworks](https://sidsaladi.substack.com/p/week-17-6-most-effective-problem) ## When to use this - A backlog or idea list is too long and you need a build order you can defend to eng and leadership. - Stakeholders disagree on what's most important and you need a shared, transparent rubric. - You're choosing between a few big bets and want to compare them on the same axes. - Someone asks "why is X above Y?" and you need a real answer, not "it felt right." - You're deciding scope for a release, sprint, or quarter against a specific goal or metric. ## Pick the right framework - **RICE** — many comparable features competing for the same roadmap; you have rough reach data. The default for ongoing backlog triage. - **ICE** — RICE without trustworthy reach data, or you need a fast first-pass cut. Lighter, more subjective. - **Value vs Effort (2x2)** — small list, mixed audience, you need a fast visual