Transforms overwhelming backlogs into clear, actionable priorities by mapping items on a 2x2 effort-vs-impact matrix, identifying quick wins (high impact, low effort), big bets, time sinks, and fill-ins. Use when ranking backlogs, deciding what to do first, prioritizing feature roadmaps, triaging bugs or technical debt, allocating resources across initiatives, identifying low-hanging fruit, evaluating strategic options, or when user mentions prioritization, quick wins, effort-impact matrix, high-impact low-effort, big bets, or "what should we do first?".
Copy this checklist and track your progress:
Prioritization Progress:
- [ ] Step 1: Gather items and clarify scoring
- [ ] Step 2: Score effort and impact
- [ ] Step 3: Plot matrix and identify quadrants
- [ ] Step 4: Create prioritized roadmap
- [ ] Step 5: Validate and communicate decisions
Step 1: Gather items and clarify scoring
Collect all items to prioritize (features, bugs, initiatives, etc.) and define scoring scales for effort and impact. See Scoring Frameworks for effort and impact definitions. Use resources/template.md for structure.
Step 2: Score effort and impact
Rate each item on effort (1-5: trivial to massive) and impact (1-5: negligible to transformative). Involve subject matter experts for accuracy. See for advanced scoring techniques like Fibonacci, T-shirt sizes, or RICE.
Step 3: Plot matrix and identify quadrants
Place items on 2x2 matrix and categorize into Quick Wins (high impact, low effort), Big Bets (high impact, high effort), Fill-Ins (low impact, low effort), and Time Sinks (low impact, high effort). See Common Patterns for typical quadrant distributions.
Step 4: Create prioritized roadmap
Sequence items: Quick Wins first, Big Bets second (after quick wins build momentum), Fill-Ins during downtime, avoid Time Sinks unless required. See resources/template.md for roadmap structure.
Step 5: Validate and communicate decisions
Self-check using resources/evaluators/rubric_prioritization_effort_impact.json. Ensure scoring is defensible, stakeholder perspectives included, and decisions clearly explained with rationale.
By domain:
By stakeholder priority:
Typical quadrant distribution:
Red flags:
Effort dimensions (choose relevant ones):
Impact dimensions (choose relevant ones):
Composite scoring:
Example scoring (feature: "Add dark mode"):
Ensure quality:
Include diverse perspectives: Don't let one person score alone (eng overestimates effort, sales overestimates impact)
Differentiate scores: If everything is scored 3, you haven't prioritized
Question extreme scores: High-impact low-effort items are rare (if you have 10, something's wrong)
Make scoring transparent: Document why each score was assigned
Revisit scores periodically: Effort/impact change as context evolves
Don't ignore dependencies: Low-effort items blocked by high-effort prerequisites aren't quick wins
Beware of "strategic" override: Execs calling everything "high impact" defeats prioritization
Resources:
Success criteria:
Common mistakes:
When to use alternatives: