Prioritization Matrix Template

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

• Quick wins (high impact, low effort): Do these now. If you're not, the meeting that produced the matrix has failed.
• Big bets (high impact, high effort): The strategic ones. Sequence carefully. These are usually 1-2 per quarter, max.
• Fill-ins (low impact, low effort): Cheap enough to do in the gaps, for momentum or for a stakeholder who needs to see movement. Don't let them eat the time meant for the big bets.
• Time sinks (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.

Building a prioritization matrix in Excel

Most people build the 2x2 as a picture: a chart with four boxes drawn on it, initiatives dragged around by hand. That version cannot be sorted, filtered, or defended. A prioritization matrix Excel template should compute the quadrant, not draw it. Here is the wiring.

Columns. A is the initiative, B impact scored 1 to 5, C effort scored 1 to 5, D the quadrant, E the score, F the rank, G the owner, H the one-line rationale. Select B4:C40 and apply Data › Data Validation › Allow: Whole number, between 1 and 5. A 1-to-5 field that accepts 7 or "high-ish" will produce a ranking, and the ranking will be wrong in a way nobody spots.

Quadrant placement. One nested IF on impact and effort, no lookup table:

=IF($B4>=4,IF($C4<=2,"Quick win","Big bet"),IF($C4<=2,"Fill-in","Time sink"))

Read it as two questions in order. Is the impact high? Then is the effort low? The nesting matters: impact is the outer test because impact is the question the room should answer first. Set the thresholds deliberately. I use 4 and 2 rather than splitting at 3 on both axes, because a 3-and-3 split puts half the portfolio in "Quick win" and the sheet stops discriminating.

Score and rank. Weight impact double, subtract effort, then rank:

=($B4*2)-$C4

and in column F, =RANK($E4,$E$4:$E$40). The absolute range on the second argument is what stops the rank from sliding as you fill down. If you want ties broken by lower effort instead of arbitrarily, use =RANK($E4,$E$4:$E$40)+COUNTIFS($E$4:$E4,$E4,$C$4:$C4,"<"&$C4).

Conditional formatting, one rule per quadrant. Select A4:H40 and add four formula rules, each coloring the whole row: =$D4="Quick win" in green, =$D4="Big bet" in blue, =$D4="Fill-in" in pale amber, and =$D4="Time sink" in grey with strikethrough. The dollar sign on D and the bare row number are load-bearing: lock the column, let the row travel. Grey the time sinks rather than deleting them. A prioritization sheet that shows only survivors cannot answer the question you will actually be asked in October, which is why something did not make the list.

The chart, and the one thing that breaks. Select the impact and effort columns, Insert › Scatter, put effort on the X axis and impact on Y, then set both axis bounds to 0 and 6 with major gridlines every 1. Right-click the series, Add Data Labels, then Format Data Labels › Value From Cells and point it at the initiative names in column A. That last step is the whole trick, and it is the thing that does not survive a trip to Google Sheets: Sheets has no "value from cells" labelling on a scatter chart, so you either label the points by hand or split the series. Everything else moves cleanly between Excel and Google Sheets. IF, RANK, COUNTIFS, the 1-to-5 validation, and all four formatting rules import intact.

Freeze panes. Click B4, View › Freeze Panes. Initiative names stay visible while you argue about the numbers, which is the entire reason anyone is looking at the sheet.

A worked prioritization example

Six initiatives from one quarter's planning session, scored by the room in about forty minutes. Quadrant and score are formulas, not opinions.

At a glance, two things are true that nobody said out loud in the session. The replatform and the currency display tie at 5, which is exactly why you rank inside a quadrant and never across the sheet: one is a quarter of engineering and the other is a week. And the loyalty item scored a 0 while carrying the most senior name on the list. That is the row the meeting was really about.

The matrix did not make that decision. It just made the decision visible in a place where refusing to make it looks worse than making it.

Questions PMs ask

Is this RICE, MoSCoW, or value-vs-effort?

Closest to value-vs-effort (impact vs effort 2×2), but with a transparent rubric and a decision log. Simpler than RICE, more rigorous than MoSCoW. The cheat sheet covers when to use each framework.

How do I score 'impact' without arguing about it?

The template includes a pre-built rubric with anchored definitions: revenue impact, customer impact, strategic alignment, risk reduction. Score each, take the max. Removes the 'because I said so' problem when stakeholders push back.

Can I use this for product roadmap prioritization?

Yes. The template is built for any forced-ranking decision: product features, program initiatives, OKR candidates, vendor selection. The cheat sheet has examples of each.

What's the difference vs. the interactive version?

The Excel template is for solo work, async scoring, and archival. The interactive web app is for live workshops where you score together on a screen-share. Same model, different surface. Many teams use both.