A Client Wanted Everything at Once, the Prioritization Framework That Fixed It

The list arrived as a spreadsheet: 23 items, all marked "must-have," for a sprint that realistically had capacity for five. My first instinct was to push back on scope directly, which almost never works — everyone on a must-have list genuinely believes their item belongs there.

What worked instead was a single working session where we scored every item on two axes together, out loud: estimated business impact and estimated effort, each on a simple 1-5 scale, with the client doing the impact scoring and me doing the effort scoring. Nobody's item got rejected in the abstract — every item got plotted, visibly, against every other item.

Nobody wants to cut their own item from a list. Everybody can look at a 2x2 grid and see which ones don't belong in this sprint.

What the grid actually revealed

• Six items clustered as high-impact, low-effort — the obvious sprint picks, and everyone agreed instantly once they were visualized together.
• Four items were high-effort for genuinely low impact — things that had made the list because someone asked for them once, not because they mattered.
• A surprising number were duplicates of each other phrased differently by different stakeholders, which only became obvious once they were all on one page.
• The exercise took 40 minutes and did more prioritization work than three weeks of email back-and-forth had managed.

The key wasn't the framework itself — impact-versus-effort grids are not a novel idea. The key was doing it live, with the client scoring their own items, instead of me prioritizing on their behalf and presenting a verdict. A prioritized list I hand someone invites debate. A prioritized list they built with me rarely does, because they already watched the tradeoffs get made.

The remaining 17 items didn't disappear — they went into a backlog, visibly ranked, with the client able to see exactly where the line was and why. Nobody felt cut. The sprint just got realistic.