Impact/effort matrix
The impact/effort matrix is a prioritization tool that sorts tasks or ideas into four quadrants along two axes: expected impact and required effort. It helps teams quickly decide what to do first, what to schedule, what to postpone, and what to drop altogether. It's one of the simplest and most widely used frameworks in product management, UX design, and project management.
Getting priorities right is a key factor in project success. The data shows that most projects fail precisely because of poor decisions about what to do and in what order:
- Only 31% of IT projects succeed. In its CHAOS 2020 study (50,000+ projects, 5 years), the Standish Group found that small projects succeed 90% of the time and large ones less than 10% (Standish Group, 2020)
- 34% of projects suffer from scope creep. PMI's Pulse of the Profession 2024 (2,246 professionals, 25+ countries) found that organizations using prioritization tools see scope creep on only 28% of projects (PMI, 2024)
- Companies with clear priorities complete 40% more strategic initiatives. McKinsey found that fewer than half of companies use a structured prioritization framework (McKinsey, 2012)
- Agile teams are 2x more successful. Agile projects succeed 42% of the time, compared with 13% for waterfall projects (Standish Group, 2020)
FAQ
How do you use an impact/effort matrix correctly?
Start by listing all your tasks or ideas. Then rate each one on two axes: what impact it will have on your goal (e.g., conversions, user satisfaction, revenue) and how much effort it will take (time, money, complexity). The result is four quadrants: “quick wins” (high impact, low effort: do now), “major projects” (high impact, high effort: plan), “fill-ins” (low impact, low effort: do when time allows), and “thankless tasks” (low impact, high effort: drop). PMI recommends this approach as a basis for evaluating a project portfolio (PMI, Evaluation of Strategic Alternatives).
How does the impact/effort matrix differ from other prioritization frameworks?
The impact/effort matrix is the simplest option, scoring only two dimensions. More advanced frameworks like RICE (Reach, Impact, Confidence, Effort) or ICE (Impact, Confidence, Ease) add more variables for more precise scoring. According to Atlassian, the choice depends on context: impact/effort is ideal for quick workshops with clients, while a product backlog with dozens of items calls for a more quantitative approach (Atlassian, Prioritization Frameworks).
When should you use an impact/effort matrix in a web project?
Typically during discovery or when planning iterations. Say user testing leaves you with a list of 20 findings: the matrix helps you decide which to fix first. Standish Group data shows that 64% of features on a typical website are rarely or never used, which means good prioritization saves a huge amount of unnecessary work (Standish Group, CHAOS Report, 2020).
Sources:
- Standish Group, CHAOS Report 2020: Beyond Infinity: analysis of 50,000+ projects, 31% success rate, effect of project size on outcomes
- PMI: Pulse of the Profession (2024): survey of 2,246 professionals in 25+ countries, data on scope creep and project success
- McKinsey: Delivering Large-Scale IT Projects On Time (2012): analysis of 5,400 IT projects, impact of prioritization on success
- Atlassian: Prioritization Frameworks: overview of prioritization methods including impact/effort, RICE, and ICE
%201.webp)