Decision-making & prioritisation
Impact-Effort Matrix
A 2x2 grid that sorts candidate actions by expected impact against effort required, separating quick wins and major projects from fill-ins and thankless tasks, so a team spends its limited capacity where it counts and gains licence to stop work that earns nothing.
Also known as Action Priority Matrix, Impact vs Effort grid, Effort-Impact Matrix. First set out by No single originator; codified through quality-improvement and Lean Six Sigma practice in 1990; the primary source is cited in full below.
Where this is contested
No single originator or primary source exists, and dating is approximate. The grid emerged from quality-improvement and Lean Six Sigma practice, Mind Tools popularised the quadrant names under the Action Priority Matrix label, and the closely related PICK chart (Possible, Implement, Challenge, Kill) was developed at Lockheed Martin for sorting process-improvement ideas.
- Format
- 2×2 matrix
- Level
- Team · Product
- Best for
- Prioritise · Allocate resources · Evaluate options
- Decision stage
- Decide · Plan
- Difficulty
- Introductory
- Time to apply
- Sixty to ninety minutes for a team to plot and argue over a twenty-item list.
Plate · The model
The components
Quick wins
High impact for low effort. The best return on capacity available and the right place to start, both for the value itself and for the momentum and credibility early results buy. Genuinely rare, which is worth remembering when this quadrant looks crowded.
Signals of strength
Deliverable in days with people and tools you already have · No new budget, approvals or dependencies · Impact traceable to the agreed goal, not just visibility · Someone can own it this week
Major projects
High impact for high effort. The strategic quadrant, where the big returns live, funded and planned properly rather than started casually. The discipline is concurrency: a team that runs many major projects at once usually finishes none of them.
Signals of strength
Needs sponsorship, budget or cross-team coordination · Months rather than days, with real delivery risk · Payoff justifies a plan, milestones and a named owner · Would be damaged by being squeezed into spare time
Fill-ins
Low impact for low effort. Harmless improvements worth doing when capacity is idle, batched or delegated, and never allowed to displace higher-value work merely because they are easy and pleasantly finishable.
Signals of strength
Nice-to-have that nobody would miss if it never happened · Minutes or hours of effort, no coordination needed · Suitable for quiet periods, onboarding tasks or batching · Its main attraction is being easy
Thankless tasks
Low impact for high effort. The capacity sink: inherited routines, reports nobody reads, processes that outlived their purpose. The quadrant's job is to generate a stop-doing list, and retiring one thankless task often funds a quick win several times over.
Signals of strength
Large recurring effort whose beneficiary nobody can name · Survives on habit, precedent or fear of stopping · 'We've always done it' is the strongest argument offered · Stopping it would free meaningful capacity within weeks
When it earns its keep
- You have more candidate actions than capacity, typically after a brainstorm, retrospective or improvement workshop, and need a fast, shared first cut.
- A team is busy but not productive, and you want to make visible how much effort is flowing into work that nobody can connect to an outcome.
- A change programme needs early momentum, and identifying genuine quick wins will buy credibility for the longer bets.
- You need a defensible triage of a backlog or idea list and lack the data for heavier scoring methods, or the decision does not warrant them.
And when it doesn't
- The decision is large, irreversible or safety-critical. Two subjective axes are far too crude; use proper cost-benefit analysis, a risk assessment or a business case.
- Impact can actually be quantified. If you can model revenue, cost or risk per option, weighted scoring or unit economics will beat gut placement on a whiteboard.
- The options have strong dependencies or sequencing constraints. The matrix is order-blind, and 'do quick wins first' can be exactly wrong when a major project unlocks everything else.
- Urgency is the real discriminator. Impact and effort say nothing about deadlines; the Eisenhower Matrix handles urgent-versus-important trade-offs.
How to run it
Before starting, gather the inputs the analysis depends on:
- A defined list of candidate actions at roughly comparable granularity, since plotting 'fix the newsletter' against 'transform the operating model' produces nonsense.
- A shared definition of impact: on which goal, over what time horizon, for whom. Unstated horizons are where these workshops quietly go wrong.
- Effort estimates from the people who would actually do the work, covering time, money and attention rather than time alone.
- Willingness to act on the bottom-right quadrant, because a matrix that never kills anything is a poster, and enough time to argue placements honestly.
- 1
Define the goal and the horizon
Agree what impact means before rating anything: which objective, measured how, over what period. A one-year revenue lens and a five-year capability lens will place the same item in different quadrants, and both placements will be defended sincerely.
- 2
Assemble the candidate list
Gather the actions, de-duplicate, and normalise granularity so items are comparable. Split anything that is really a programme into its separable parts; bundles always plot flatteringly.
- 3
Rate impact and effort
Place each item relative to the others, with the doers estimating effort and the goal-owners arguing impact. High-low bands are usually enough; false precision on subjective axes is effort spent decorating a guess.
- 4
Read the quadrants and assign treatments
Quick wins get done now and publicised. Major projects get planned properly, few at a time. Fill-ins get batched for slack time or delegated. Thankless tasks get killed, shrunk or automated, and killing them is the matrix's highest-value output.
- 5
Challenge the placements
Interrogate the crowd in the quick-wins corner, because optimism about effort is the most reliable bias in the room. Ask whose impact each item serves, and move anything whose placement rests on hope rather than evidence.
- 6
Revisit as reality reports back
Re-plot when estimates meet actuals. A quick win that has taken six weeks is a major project mislabelled, and the list itself decays as the goal moves.
Reading the result
A plotted map of candidate actions across the four quadrants, a treatment per quadrant (do now, plan properly, batch, stop), and, if the exercise was honest, a stop-doing list that releases the capacity the rest of the plan requires.
- The top half is where value lives and the left half is where speed lives; the top-left corner is both, which is why it fills up with wishful thinking and deserves the hardest scrutiny.
- Placements are relative judgements, not measurements. The argument that moves an item between quadrants is usually worth more than the final picture.
- Read the bottom-right as the budget line. Work stopped there is the cheapest capacity you will ever find, and a session that kills nothing has probably failed.
A worked example
A hospice fundraising team triages its away-day idea list
The four-person fundraising team of a medium-sized UK hospice charity returns from an away day with 23 ideas, no additional budget, and an unrestricted-income target up 8% on last year. They define impact as unrestricted income within the financial year, estimate effort in staff-days with the person who would do each task, and plot the list.
- Quick wins
- Adding Gift Aid prompts to the online donation journey (the charity's claim rate is around 40% against a sector norm nearer 55%), a legacy-giving paragraph in the existing supporter newsletter, and a stewardship call to reactivate a lapsed corporate donor. A few days of combined effort against thousands of pounds of near-certain income. All three are owned and dated before the meeting ends.
- Major projects
- A regular-giving acquisition campaign and a full overhaul of the Christmas appeal. Both score high on impact with strong sector evidence, and both consume weeks of work plus trustee sign-off on spend. The team commits to the regular-giving campaign alone and schedules the Christmas overhaul for next year, on the grounds that starting both would finish neither.
- Fill-ins
- Refreshing the supporter thank-you letters and de-duplicating CRM records. Worth doing, invisible to income this year, and assigned as background tasks for quiet weeks with no deadlines attached, so they can never displace campaign work.
- Thankless tasks
- The monthly street collection, which raises roughly 200 pounds for two staff-days including permits, float and cash handling, and a bespoke sponsorship brochure produced for an audience of six local companies. Both had survived for years on habit and guilt. The collection is retired with thanks to its volunteers; sponsors get a two-page PDF instead.
The read. The matrix's real work was granting licence to stop things: retiring the street collection alone recovers around 24 staff-days a year, most of what the regular-giving campaign needs. The team also reads the tool's limits honestly. Legacy marketing scored low on a one-year income lens but compounds over a decade, so it is held as a deliberate exception rather than killed by the horizon the team happened to choose. The matrix decided the year; it was not allowed to decide the decade.
Pitfalls
- Rating impact without first agreeing impact on what and by when. Half the disagreements in these sessions are two unstated time horizons talking past each other.
- Letting managers estimate effort for work other people will do. Effort scores belong to the doers, or the quick-wins quadrant becomes fiction.
- Optimism migration: most of the list drifting to quick wins because impact is imagined generously and effort hopefully. If a third of your list is quick wins, your ratings are wrong.
- Treating placements as measurements and skipping the argument. On subjective axes the discussion is the analysis; the chart is just its receipt.
- Filing the matrix without killing anything. The bottom-right quadrant is where the capacity comes from, and ignoring it turns the exercise into decoration.
- Punishing compounding or enabling work. Infrastructure, relationships and legacy pipelines score badly on short-horizon impact and must be judged as exceptions, or the matrix will strip the future to feed the quarter.
What the critics say
Both axes are subjective judgements, and the effort axis is systematically biased. Research on the planning fallacy shows people reliably underestimate the time and cost of their own plans, so the quick-wins quadrant is predictably overpopulated and the matrix inherits the very optimism it is meant to discipline.
Kahneman, D. and Tversky, A. (1979) 'Intuitive Prediction: Biases and Corrective Procedures', TIMS Studies in Management Science, 12, pp. 313-327.
The matrix is blind to sequencing, dependency, risk and reversibility. 'Quick wins first' is locally rational and can be globally wrong, and a standing bias towards low-effort work starves the compounding, high-effort initiatives that produce most long-run value.
It rewards confident guessing because it carries no confidence dimension. Successor schemes in product management, such as ICE and RICE scoring, added confidence (and reach) precisely to correct impact-effort's tendency to treat a hunch and a measurement as the same input.
Ellis, S. and Brown, M. (2017) Hacking Growth. New York: Currency, which popularised ICE scoring.
Work it through
List your candidate actions, agree what impact means and over what horizon, then place each item in a quadrant with a note on why. Your entries persist for this browser session and can be copied out as Markdown or printed.
0 of 4 blocks filled
Sources and further reading
- American Society for Quality, 'Impact Effort Matrix', ASQ Quality Resources. ↗
- Mind Tools Content Team, 'The Action Priority Matrix: Making the Most of Your Opportunities', Mind Tools. ↗
- 'PICK chart', Wikipedia, documenting the Lockheed Martin origin of the closely related Possible-Implement-Challenge-Kill variant. ↗