Cheat sheet
Prioritization frameworks cheat sheet
No framework decides for you. Each makes a different assumption visible so the argument is about the right thing.

Scoring models
- RICE
- Reach × Impact × Confidence ÷ Effort. Good for comparing many small bets.
- ICE
- Impact × Confidence × Ease. Faster, rougher than RICE.
- Cost of delay
- Value lost per week of waiting.
- CD3
- Cost of delay ÷ Duration. Do the highest first.
- Value vs effort
- 2×2: quick wins first, money pits never.
Categorization
- MoSCoW
- Must, Should, Could, Won't (this time). Good for fixed-scope releases.
- Kano
- Basic needs, performance features, delighters.
- Eisenhower
- Urgent × Important: do, schedule, delegate, drop.
- Now / Next / Later
- Roadmap without false dates.
Blind spots
- False precision
- Scores are guesses; compare in bands, not decimals.
- Effort bias
- RICE favors small work; strategic bets need a separate lane.
- Keep-the-lights-on
- Reserve capacity for reliability before scoring features.
- Dependencies
- A low-scoring item may unblock high-scoring ones.
Try it — Cost of delay
CD3 of A
5,000
CD3 of B
7,500
Delay cost, A first
$470,000
Delay cost, B first
$430,000
Do B first: the order with the higher CD3 saves $40,000 in value lost while waiting. One team, one project at a time; each project loses its weekly value for every week until it ships.
Test yourself
Questions from the lessons behind this sheet, explained when you check them.
Learn the ideas behind it
- Prioritization →Every yes is a no to something else. Make the trade explicit.
- Roadmaps & discovery →A roadmap is a statement of intent. Discovery is how you avoid building the wrong thing.
- Strategy basics →A strategy is a set of choices — including what you will not do.
