Why "we'll prioritize later" never works
Every PM has been in the meeting where 14 initiatives are on the table, everyone agrees they can't all ship this quarter, and the meeting ends with "let's prioritize offline." Then nothing happens, and at the next meeting you're still trying to do all 14, just slower.
Prioritization fails when it's done in someone's head with no shared rubric. Two people scoring "impact" can disagree by an order of magnitude and not know it. Without a structured score, the loudest voice wins, which is usually the most senior person in the room, which is usually wrong on this question.
"Prioritization is the job. If you're not saying no to something, you're not prioritizing."
This template forces a shared score, surfaces the trade-offs visually, and logs the decision so three months later, when someone asks "why didn't we do X?", you can show them.
Why a 2×2 beats more sophisticated frameworks
You've probably seen RICE, ICE, MoSCoW, value-vs-complexity, weighted-shortest-job-first. They have their place. For most program-level prioritization, the 2×2 (impact vs effort) wins because:
- Two axes a non-PM can argue with. The minute you introduce a third or fourth dimension, you lose the ability to facilitate the conversation in a room with executives and engineers.
- Visual clustering surfaces the trade-off. The quadrant view makes "we'd love to do all of this but we have to pick the top-right" obvious in 30 seconds.
- The score is a starting point, not the answer. A 2×2 leaves room for the strategic override ("yes the score says no, but the CEO promised this in the all-hands"). More elaborate frameworks pretend that override doesn't happen.
The four quadrants and what to do with each
- Top-right (high impact, low effort): Do these now. If you're not, the meeting that produced the matrix has failed.
- Top-left (high impact, high effort): The strategic bets. Sequence carefully. These are usually 1-2 per quarter, max.
- Bottom-right (low impact, low effort): Quick wins for momentum or stakeholder management. Do them in the gaps. Don't let them eat the time meant for top-left.
- Bottom-left (low impact, high effort): Kill these. The hardest move politically; the easiest move analytically. The decision log captures the reasoning so the conversation isn't relitigated.
Once the matrix produces a ranked list, it feeds into the roadmap tracker for sequencing and the program charter's in-scope/out-of-scope sections.
