All templates

Priority Matrix Template

Sort any list of tasks, features, or decisions across four quadrants by impact and effort. Instantly see what to do first, schedule, delegate, or drop.

Use this template

What you get

  • Four color-coded quadrants: Do First, Schedule, Delegate, Reconsider
  • Pre-filled example items in each quadrant — swap in your own tasks
  • Impact and effort axes with high/low labels for instant orientation

What this template is for

A priority matrix (also called an impact-effort matrix or 2×2 matrix) helps teams cut through a backlog of tasks and decisions by plotting each item against two axes: impact and effort. Items that fall in the high-impact, low-effort quadrant get done first. Items in the high-impact, high-effort quadrant get scheduled. Low-impact items get delegated or dropped. This template gives you a ready-made four-quadrant grid with labeled sections and example items — swap in your own tasks and make faster, more defensible prioritization decisions.

When to use this template

  • Sprint planning: plot all candidate features by impact and effort before deciding what goes in the next sprint.
  • Backlog grooming: use the matrix to surface quick wins that have been buried under large, complex requests.
  • Stakeholder alignment: show the full task landscape visually so everyone agrees on what gets deprioritized and why.
  • Personal productivity: map your own to-do list when everything feels equally urgent.
  • Post-mortem action items: sort follow-up tasks after an incident to decide what to fix immediately vs. later.

How to use it

  1. 1List all the tasks, features, or decisions you need to prioritize — aim for 8–16 items.
  2. 2For each item, estimate impact: how much value does completing this create for users or the business?
  3. 3Estimate effort: how much time and resources does this require to complete?
  4. 4Place each item in the appropriate quadrant based on its impact-effort combination.
  5. 5Work through the matrix quadrant by quadrant: Do First → Schedule → Delegate → Reconsider.
  6. 6Review the matrix with your team and resolve any disagreements about placement before committing.

Quick example

Product backlog prioritization

Do First (High Impact, Low Effort):
- Fix critical bug in core user flow
- Complete high-value customer feature request
Schedule (High Impact, High Effort):
- Refactor auth module for security
- Build new analytics dashboard
Delegate (Low Impact, Low Effort):
- Update internal documentation
Reconsider (Low Impact, High Effort):
- Rewrite legacy codebase with no clear benefit

Start editing online

Open the template in CodePic, replace the sample nodes, and turn it into your own study board in a few minutes.

See examples: /templates/priority-matrix/examples

More templates you might like