An empty 2x2 earns almost nothing. In a first round of eight cases, I typically hear two or three candidates name "quick wins" without a single dollar or person-month attached. The sheet rewards the opposite: axes you can defend, a sequence that respects dependencies, and an explicit reject list.
The thesis is simple. The impact-effort matrix only scores when both axes are quantified, then turned into a ranked plan—not a pretty four-box slide. After this piece you should be able to take a brainstormed list, put numbers on impact and effort in under two minutes, and say out loud where the matrix would mislead you.
What the interviewer is actually scoring
At synthesis, the interviewer is not grading geometry. They are listening for three behaviors:
- You sized the prize (impact) against the problem you diagnosed.
- You sized the cost (effort) in a unit the client would recognize.
- You sequenced work so week-one actions do not assume month-six enablers.
A blank grid with "High / Low" labels is folklore dressed as structure. Eisenhower's 1954 distinction between the urgent and the important—quoted from a former college president in his Evanston address—was about attention, not resource allocation (American Presidency Project transcript). Consulting prioritization is closer to portfolio math: expected value versus resources consumed, with capacity as a hard constraint.
McKinsey's public writing on project–resource matching describes rules-based ranking that starts from financial value and ease of implementation, then overlays strategy and capacity (Matching the right projects with the right resources). HBR's guidance on project prioritization makes the same demand in plainer language: without a clear hierarchy of purpose, teams cannot rank work when resources are finite (How to Prioritize Your Company's Projects). Neither source asks you to invent adjectives. They ask you to score.
How to put numbers on impact
Pick one unit and stick to it for the whole list. In interviews, the clean units are:
| Case type | Impact unit (12-month) | High bar (rule of thumb) |
|---|---|---|
| Profit / cost | $ of EBITDA or margin recovered | ≥25% of the gap you diagnosed |
| Growth | $ of incremental revenue (or contribution) | ≥20% of the growth target |
| Risk / ops | $ of expected loss avoided, or hours of downtime cut | Large enough to move the client's stated KPI |
If the profitability gap is $24M and an idea recovers $2M, call it low impact even if the idea sounds clever. Percent of the problem is the anchor. When you lack a precise estimate, state a range and the midpoint you will use for ranking: "I am calling this $4–6M, so I will score $5M."
Avoid scoring "strategic importance" as a separate floating axis unless the interviewer gave you a non-financial objective. In most commercial cases, strategy shows up as a constraint ("must protect the franchise brand") rather than a third number.
How to put numbers on effort
Effort is not "hard" or "easy." Use a composite you can say in one breath:
Effort score ≈ person-months × (1 + friction), where friction is 0 for one-team decisions and 0.5–1.0 when procurement, IT, or regulators must move.
| Effort band | Typical signal | Interview label |
|---|---|---|
| 1–3 person-months | One owner, existing tools, <30 days | Low |
| 4–9 person-months | Cross-functional, light systems work, 1–3 months | Medium |
| 10+ person-months | Capex, vendor RFP, org redesign, 6+ months | High |
Relative ranking beats fake precision. If you have six ideas, you only need them ordered. Still say the unit out loud so the interviewer hears you thinking in resources, not vibes.
Ned's rule. If you cannot name a dollar (or other impact unit) and a person-month estimate for an idea, you do not get to call it a quick win. Label it "unscored" and keep talking—or drop it.
Where the matrix misleads
Three failure modes show up in almost every weak synthesis. Name them before the interviewer does.
Dependencies. Idea B scores as a quick win only if Idea A already built the data feed. Plotting both as independent high-impact / low-effort boxes is fiction. Sequence A before B, or treat B's effort as A plus B.
Sequencing and capacity. Two medium-effort projects that each need the same three analysts are not both "doable in parallel." Capacity is a third constraint the 2x2 ignores. McKinsey's capital-allocation guidance stresses focusing senior attention on a short list of essential initiatives—on the order of tens, not hundreds—so resources are not diffused (Keep calm and allocate capital). In a case, say: "With one ops team, I would run one major project at a time."
Risk and irreversibility. A high-impact / low-effort price cut may destroy brand equity or trigger a competitor war. Score expected impact net of downside, or flag the option as high-risk even if the effort looks light. The matrix does not show downside; you must.
When any of these bite, the ranked plan should diverge from a naive quadrant sort. That divergence is the point—it shows judgment.
Worked example: brainstorm to ranked plan
Prompt. Northline Grocery operates 85 stores in the Midwest. Same-store sales are flat. Operating margin fell from 4.2% to 2.8% on $1.2B revenue—an $16.8M EBITDA gap. The CEO wants a 12-month recovery plan the board can fund.
Diagnosis (already done in the case). Roughly $9M from promotional over-discounting in the center store, $5M from shrink and spoilage in fresh, $2.8M from underutilized private-label mix in dry grocery.
Brainstormed list (eight ideas, not yet scored):
- Cut promotional depth on the top 40 SKUs
- Renegotiate slotting fees with two national brands
- Roll out dynamic markdowns in fresh (new software)
- Hire 40 part-time stockers for evening resets
- Expand private-label SKU count by 200 items
- Close four lowest-traffic stores
- Launch a regional loyalty app rewrite
- Centralize produce buying across all 85 stores
Step 1 — Quantify.
| Idea | Impact ($M / yr) | Effort (person-months) | Notes |
|---|---|---|---|
| A. Promo depth cut (top 40) | 7.5 | 2 | Merch + finance, 6 weeks |
| B. Slotting renegotiation | 2.0 | 4 | Legal + category; uncertain |
| C. Dynamic fresh markdowns | 4.0 | 14 | Software + store training |
| D. 40 part-time stockers | 1.2 | 3 | Labor cost nearly offsets |
| E. +200 private-label SKUs | 2.5 | 12 | Depends on buyer capacity |
| F. Close 4 stores | 3.5 | 18 | Severance, leases, PR risk |
| G. Loyalty app rewrite | 0.8 | 20 | Multi-vendor IT |
| H. Centralize produce buying | 3.0 | 8 | Depends on A for clean promo data |
Step 2 — Naive matrix.
| Quadrant | Ideas |
|---|---|
| High impact, low effort | A |
| High impact, high effort | C, F |
| Low impact, low effort | B, D |
| Low impact, high effort | E, G |
H sits on the boundary (medium impact, medium–high effort).
Step 3 — Correct for where the matrix misleads.
- H depends on cleaner promotional and shrink data from A and early C pilots; treat H as phase 2, not a parallel "fill-in."
- C and F both consume the same ops leadership bench; pick one major project. C recovers more margin with less irreversible damage than store closures, so F moves to reject for year one.
- D looks low effort but nets little after wage cost—call it fill-in only if store managers have idle budget, not a headline.
Step 4 — Ranked plan (what you say).
- Weeks 1–8: Execute A (promo depth). Modeled $7.5M. Assign one category director.
- Months 2–4: Start B in parallel ($2M). Low coordination with A.
- Months 3–9: Fund C as the single major project ($4M). Pilot in 15 stores before chain-wide.
- Months 6–12: Launch H once promo and fresh data stabilize ($3M).
- Park: D as capacity allows; E after private-label buyer bandwidth opens.
- Reject for year one: F (irreversible, high effort) and G (tiny impact relative to $16.8M gap).
Modeled recovery if A+B+C+H land: about $16.5M, essentially closing the gap. That is the interview answer: numbers, sequence, named rejects—not four colored boxes.
A 90-second scoring habit you can reuse
When the interviewer asks for a recommendation:
- Restate the gap in one number.
- List 5–7 MECE options (see MECE in case interviews).
- Score impact as % of gap; score effort in person-months.
- Sort, then adjust for dependency, capacity, and risk.
- Lead with the first 90-day moves, commit to one major project, name what you cut.
If you skip step 4, you sound like every other candidate who memorized quadrant names.
Practice this today
Take any profitability case you have already structured. Spend ten minutes writing eight raw ideas, then force a table with impact ($), effort (person-months), and a one-line dependency note. Deliver a 90-second ranked plan out loud.
For a timed rep with scoring, start a free structure drill or a full case: everything on CoachNed is open for seven days, no card; then $120 for a recruiting season or $49 a month.
Try /start for three typed turns, /drills/brainstorming if your weak spot is idea generation, or /interview for the live CopperCup voice case.
Frequently asked questions
What is the impact-effort matrix in a case interview?
It is a prioritization tool that ranks options by expected value versus implementation cost. In interviews it only helps when you quantify both axes and turn the plot into a sequenced recommendation with explicit rejects.
How do you calculate impact and effort quickly?
Anchor impact to the problem size (for example, dollars of the EBITDA gap over 12 months). Score effort in person-months, adjusting upward for cross-functional friction. Relative order matters more than decimal precision.
What are the four quadrants of an impact-effort matrix?
High impact / low effort (do first), high impact / high effort (one major project, phased), low impact / low effort (optional fill-ins), and low impact / high effort (reject). Treat the labels as a sorting aid, not the answer.
When should you not use an impact-effort matrix?
Skip or override it when options are tightly dependent, when one scarce team is the real bottleneck, or when downside risk dominates expected upside. In those cases, state the constraint and sequence accordingly.
Is the impact-effort matrix the same as the Eisenhower matrix?
No. Eisenhower's framing (urgent versus important) is about attention management, as in his 1954 Evanston remarks. Impact versus effort is about value and resources. Do not mix the axes mid-answer.
Sources
- Address at the Second Assembly of the World Council of Churches, Evanston, Illinois (Eisenhower, 1954) — primary source for the urgent/important distinction often confused with impact-effort. Checked 2026-09-24.
- Matching the right projects with the right resources (McKinsey) — NPV / ease-of-implementation ranking and capacity matching. Checked 2026-09-24.
- Keep calm and allocate capital: Six process improvements (McKinsey) — focus on a short list of essential initiatives so resources are not diffused. Checked 2026-09-24.
- How to Prioritize Your Company's Projects (HBR) — hierarchy of purpose as the precondition for ranking projects under resource constraints. Checked 2026-09-24.
CoachNed is not affiliated with McKinsey, BCG, Bain, Deloitte, or any firm named above.