Impact/Effort Matrix

A 2×2 grid for comparing expected impact and effort.

When to use this

You have a batch of 6-15 features and you want a visual sort that a stakeholder meeting can react to in 5 minutes. You need rough alignment ("we agree these four are Quick Wins"), not a precise ordering. You're new to prioritization and want a starting point.

Limits

A quadrant alone does not provide a precise ranking. Large batches can make the chart crowded, and low effort alone does not justify shipping an item.

Inputs

• Impact: How much each feature moves your primary goal. Use the same goal across all features, or the comparison is meaningless.
• Effort: Rate the total work to ship, including design, engineering, QA, and launch. PM Toolkit uses a 1–10 rating, not a duration.

Use the same rating definitions for every item.

The math

PM Toolkit uses fixed boundaries: Impact of 6 or more is high; Effort of 5 or less is low. The quadrants are:

            Low Effort     High Effort
High Impact   QUICK WINS     BIG BETS
Low Impact    FILL-INS       TIME SINKS

• Quick Wins: review for early delivery, considering evidence and dependencies.
• Big Bets: review the scope, dependencies, and capacity needed.
• Fill-ins: consider them when capacity allows and the benefit justifies the work.
• Time Sinks: review whether the expected value justifies the effort or whether the scope can change.

For a manual matrix, define the boundaries before classifying items.

A worked example

Say you're a growth PM at a 50-person startup with 5 ideas for Q3. The following example uses Impact ratings and person-week estimates for a manual matrix.

For this manual example, use median Impact (6) and median Effort (3 person-weeks) as the splits. This differs from the calculator's fixed 1–10 rating boundaries.

• Referral incentive (8, 2): Quick Win. The estimate is two person-weeks, not necessarily two calendar weeks.
• Email templates (6, 1): Quick Win under the example's boundary convention.
• Native mobile app (9, 40): Big Bet. Worth the discussion, but it's not a "decide today" item.
• Rebuild billing UI (5, 12): Time Sink. Below-median impact and well above-median effort; review its scope and expected benefit.
• CSV export (4, 3): Fill-in. Lower impact with effort at the example's low-effort boundary.

The example suggests reviewing referral incentives and email templates first. Confirm capacity, dependencies, and expected value before scheduling them.

In PM Toolkit

The UI and MCP tool use fixed rating boundaries: high Impact starts at 6, and low Effort ends at 5. The MCP tool also ranks within quadrants using Impact × (11 − Effort). This is a sorting aid, not a measured return on investment.

Common mistakes

• Mixing boundary rules. Document whether a manual matrix uses fixed thresholds or batch medians.
• Treating "low effort" as "should ship." A Fill-in is still low impact. Cheap and useless is not the same as valuable.
• Confusing effort with elapsed time. Include all contributors and use one consistent unit before translating estimates to ratings.
• Plotting features without naming the goal. "Impact on what?" If the team can't answer that in one sentence, the matrix is decoration.

Try it

• Live calculator
• MCP tool: pm_classify_impact_effort
• Related: RICE Scoring
• Related: ICE Scoring