# Impact Effort Matrix Template

Source: https://affine.pro/blog/impact-effort-matrix (AFFiNE, 2026). Free to copy and adapt.

How to use: fill in the setup, agree the rubric before anyone scores, list initiatives in the register, then copy each ID into one quadrant. Anything that scores 3 on either axis goes into the borderline list until a test or tie-break decides it.

## 1. Setup

| Field | Your answer |
|---|---|
| Goal this matrix serves | |
| Horizon (when impact is measured) | e.g. month 6 after launch |
| Impact unit | e.g. net monthly value in $, hours saved, tickets avoided |
| Effort unit | e.g. person-weeks including launch and first month |
| Capacity for new work in this horizon | e.g. 65 person-weeks |
| Facilitator | |
| Date scored | |
| Next re-score date | |

## 2. Scoring rubric (edit the bands before scoring)

| Score | Impact band | Effort band |
|---|---|---|
| 1 | Under $300 a month | Under 1 person-week |
| 2 | $300 to $999 a month | 1 to under 3 person-weeks |
| 3 (borderline) | $1,000 to $2,499 a month | 3 to under 6 person-weeks |
| 4 | $2,500 to $4,999 a month | 6 to under 12 person-weeks |
| 5 | $5,000 a month or more | 12 person-weeks or more |

Rules:

- Score impact as net value at the horizon, after costs such as discounts, fees or extra staff time.
- Count effort for design, build, QA, launch and the first month of care.
- Add any prerequisite that no other funded initiative pays for.
- Legal, security and safety obligations skip the matrix and go straight onto the plan.

Evidence grade:

- A = measured in your own data or a pilot
- B = reasoned model with checked inputs, or comparable data
- C = opinion, survey intent or copying a competitor

## 3. Initiative register

| ID | Initiative | Outcome metric | Evidence | Grade | Value calculation | Net value | Impact (1-5) | Person-weeks | Effort (1-5) | Depends on | Quadrant | Strategic fit | Owner | Next action | Re-score date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | | | | | | | | | | | | | | | |
| 2 | | | | | | | | | | | | | | | |
| 3 | | | | | | | | | | | | | | | |
| 4 | | | | | | | | | | | | | | | |
| 5 | | | | | | | | | | | | | | | |
| 6 | | | | | | | | | | | | | | | |
| 7 | | | | | | | | | | | | | | | |
| 8 | | | | | | | | | | | | | | | |
| 9 | | | | | | | | | | | | | | | |
| 10 | | | | | | | | | | | | | | | |
| 11 | | | | | | | | | | | | | | | |
| 12 | | | | | | | | | | | | | | | |

## 4. The matrix

| | Low effort (1-2) | High effort (4-5) |
|---|---|---|
| High impact (4-5) | Quick wins (candidates to do first): | Major projects (plan, staff, or test first): |
| Low impact (1-2) | Fill-ins (only when there is slack): | Thankless tasks (drop, park or shrink): |

Borderline (a 3 on either axis), with the test or tie-break that will decide it:

-
-

## 5. Before you commit

- [ ] Every quick win fits the current strategy
- [ ] Every quick win has its prerequisites funded or counted in its effort
- [ ] Committed effort is below about half of capacity, leaving room for estimates that run long
- [ ] Every grade C item in a top quadrant has a cheap test before a build
- [ ] Every item has one owner, one next action and a re-score date

## 6. Re-score log

| Date | ID | Old score (I/E) | New score (I/E) | What changed | Decision |
|---|---|---|---|---|---|
| | | | | | |
| | | | | | |

Re-score when a test or pilot reports, actual effort passes 1.5 times the estimate, a dependency slips, strategy or capacity changes, or at least every 6 weeks.
