Prioritization
56 bites tagged Prioritization — interview questions with model answers, and 60-second explainers.
The PIE Framework: Prioritizing What to Test Next
The PIE framework ranks A/B test ideas by scoring them on Potential, Importance, and Ease. It helps teams decide where to experiment first, focusing limited resources on high-impact changes.
The RICE Scoring Model: Prioritize with Data, Not Feelings
RICE is a formula—(Reach × Impact × Confidence) / Effort—for scoring competing features. It replaces gut feelings with a data-driven framework for prioritizing product roadmaps. The biggest footgun is treating the score as gospel, not a conversation starter.
ICE Score: A Quick Framework for Prioritizing Ideas
The ICE score is a quick framework for ranking ideas by asking: what's the potential Impact, our Confidence in the outcome, and the Ease of implementation? Growth teams use it to prioritize experiments, balancing big bets with quick wins.
The Kano Model: Not All Features Are Created Equal
The Kano model sorts features by how they impact user satisfaction. Use it to prioritize a product roadmap, deciding between fixing basic needs, improving core features, or adding delightful surprises.
Cost of Delay: Quantifying the Price of Waiting
Cost of Delay puts a price tag on waiting, quantifying the value lost for every week a feature isn't shipped. It helps prioritize work by its economic impact, not just effort.
Buy a Feature: Prioritize by Making Customers Spend
Buy a Feature turns prioritization into a game where customers spend a limited budget on their desired features. It's used in product planning to force trade-offs and reveal true value.
Weighted Shortest Job First (WSJF): Prioritizing for Economic Impact
WSJF prioritizes work by its economic impact over time, not just its total value. It sequences backlogs in SAFe by dividing the "cost of delay" by job size. The footgun is getting bogged down in precise estimates instead of using relative sizing.
The MoSCoW Method: Prioritizing for Fixed Deadlines
The MoSCoW method protects deadlines by sorting work into four buckets: Must Have, Should Have, Could Have, and Won't Have this time. It's used in agile projects with fixed timelines to ensure critical features ship.
Get Prioritization bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.