prioritization-effort-impact_skill

Overview

This skill helps teams rank backlogs and decide what to do first using an effort vs impact (2x2) matrix. It turns long lists of features, bugs, or initiatives into clear action: quick wins, big bets, fill-ins, and time sinks. Use it to create a prioritized roadmap, communicate rationale, and align stakeholders around execution order.

How this skill works

Collect all items to prioritize and define scoring scales for effort and impact. Score each item (e.g., 1–5 or T-shirt sizes) across chosen dimensions, plot them on a 2x2 matrix, and group into four quadrants: 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). Validate scores with diverse stakeholders, document rationale, then sequence work: quick wins first, big bets next, fill-ins opportunistically, and avoid time sinks.

When to use it

• You have a large backlog (20+ items) and need a defensible execution order
• Resource constraints force trade-offs across teams or initiatives
• Stakeholders ask “what should we do first?” or want quick visible progress
• Triaging bugs, technical debt, or competing product requests
• Building quarterly/annual roadmaps and comparing strategic options

Best practices

• Include engineering, product, sales, and customer success when scoring
• Use clear scoring scales and document the rationale for each score
• Force differentiation—avoid everyone scoring items as middling
• Revisit and re-score periodically as context or dependencies change
• Account for dependencies so blocked low-effort tasks aren’t mistaken for quick wins

Example use cases

• Prioritizing a mixed backlog of features, bug fixes, and tech debt for the next quarter
• Deciding between a platform overhaul (big bet) and several UX improvements (quick wins)
• Triage of incoming bugs: fix high-impact easy bugs first to reduce user pain
• Allocating limited engineering time across competing sales requests and roadmap items
• Evaluating strategic investments using a simple 2x2 before applying RICE or cost-of-delay