How to score impact and effort with your team

Define the decision before the scale

Start with one outcome, one audience and a time horizon. “Help new workspaces create their first shared project this month” gives people something specific to judge. “Make the product better” leaves each person scoring a different goal.

Compare initiatives at a similar level. Break a full onboarding redesign into testable changes before comparing it with a small message update. Set aside required commitments and reserve their capacity first. The matrix helps choose among optional alternatives; it should not make a mandatory deadline disappear.

• Review how the impact effort matrix works

Anchor impact to a shared outcome

The following 1–5 scale is a starting point for discussion, not a standard or a prediction of percentage improvement. Adapt the descriptions to your goal and agree on one or two reference initiatives before rating the rest.

Ask who would benefit, what would change and why the proposed work could cause that change. A request from an influential person is not evidence of impact by itself. Keep the expected size of the contribution separate from how confident you are in it.

Estimate all the work, not just implementation

Count research, design, implementation, coordination, quality checks and rollout. Estimate with the people who will do the work. A person-day measures work: two people working for a day contribute two person-days. It does not tell you the elapsed delivery time.

Use resource bands that distinguish the initiatives you actually have. Here is a continuous set of example bands. If most options exceed five days, split the work or agree on a more suitable scale before scoring. Do not change the definition halfway through the list.

Keep uncertainty visible

For each initiative, write down the evidence, the main assumption and a plausible range. “Impact 4, possibly 2–4; three interviews suggest the problem but we do not know its frequency” is more informative than an unexplained 4. Qualitative confidence labels describe the strength of the evidence, not a calculated probability.

Ask whether that uncertainty could change the choice. If yes, define the smallest useful investigation, with its own time limit and owner. If not, avoid delaying a reversible decision just to make the score feel more precise.

Resolve disagreements by examining assumptions

Have contributors estimate independently before sharing. Discuss the largest differences first. Ask each person which audience, outcome and scope they assumed. An impact score of 2 and a score of 5 may describe different user groups rather than different judgments about the same work.

For effort, compare what each estimate includes. One person may count coding while another includes migration and support. Align the scope and record the updated range. If the team still disagrees, keep the disagreement explicit and name who will decide or gather more evidence. Averaging two incompatible assumptions does not resolve them.

1. Restate the outcome and the initiative's boundaries.
2. Ask for the observations behind each estimate.
3. Separate uncertainty about impact from uncertainty about delivery.
4. Agree on a score or retain a range with a next action.
5. Record the decision owner and when the estimate will be revisited.

Use the scores to compare, then commit with real estimates

For the worked examples, 4–5 is high and 1–3 is low on each axis. Choose and explain the boundary before discussing quadrants. An initiative near it deserves a closer look; moving from 3 to 4 is not a sudden change in the real world.

These impact scores are ordinal: a 4 is not twice the benefit of a 2. Dividing impact by effort produces a neat number without establishing that precision. Use the matrix to identify trade-offs, then check the underlying work estimates, dependencies and capacity. Add person-days for planning; do not add effort scores as if they were days.

A high-impact, high-effort project can be the right choice. Consider whether a smaller first step can test its central assumption without presenting that smaller step as delivery of the whole outcome.

• See how three teams turn scores into decisions

Review the estimates when you learn something

Keep a short record of the original estimate and the reason for changing it. Revisit the scores when research contradicts an assumption, a dependency changes or the goal moves. At the agreed review date, compare the expected outcome with what you observed, as well as estimated and actual work.

In Plotwins, organize priorities on the matrix and describe assumptions in the relevant tasks. Use subtasks and responsibility to make the selected work followable. These example scales are a team convention; they do not imply that Plotwins calculates impact or confidence automatically.

• Explore prioritization on the Plotwins matrix
• Apply shared estimates to a marketing campaign plan