Use when ranking backlogs, deciding what to do first based on effort vs impact (quick wins vs big bets), prioritizing feature roadmaps, triaging bugs or technical debt, allocating resources across initiatives, identifying low-hanging fruit, evaluating strategic options with 2x2 matrix, or when user mentions prioritization, quick wins, effort-impact matrix, high-impact low-effort, big bets, or asks "what should we do first?".
Transform overwhelming backlogs and option lists into clear, actionable priorities by mapping items on a 2x2 matrix of effort (cost/complexity) vs impact (value/benefit). Identify quick wins (high impact, low effort) and distinguish them from big bets (high impact, high effort), time sinks (low impact, high effort), and fill-ins (low impact, low effort).
Use this skill when:
Common triggers:
Effort-Impact Matrix (also called Impact-Effort Matrix, Quick Wins Matrix, or 2x2 Prioritization) plots each item on two dimensions:
Four quadrants:
High Impact │
│ Big Bets │ Quick Wins
│ (do 2nd) │ (do 1st!)
│─────────────────┼─────────────
│ Time Sinks │ Fill-Ins
│ (avoid) │ (do last)
Low Impact │
└─────────────────┴─────────────
High Effort Low Effort
Example: Feature backlog with 12 items
| Item | Effort | Impact | Quadrant | |------|--------|--------|----------| | Add "Export to CSV" button | Low (2d) | High (many users) | Quick Win ✓ | | Rebuild entire auth system | High (3mo) | High (security) | Big Bet | | Perfect pixel alignment on logo | High (1wk) | Low (aesthetic) | Time Sink ❌ | | Fix typo in footer | Low (5min) | Low (trivial) | Fill-In |
Decision: Do "Export to CSV" first (quick win), schedule auth rebuild next (big bet), skip logo perfection (time sink), batch typo fixes (fill-ins).
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 resources/methodology.md 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:
npx skills add nicepkg/prioritization-effort-impact下载完整 Skill 目录，包含 SKILL.md 及所有相关文件
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
Manage Trello boards, lists, and cards via the Trello REST API.
Category:productivity