Value-Effort Matrix

Most ways of setting an order assign scores: write a value on each axis, run the arithmetic, read off the ranking. With a lot of candidates, that step alone takes more than a day. Scoring 40 items with RICE, which multiplies reach, impact, and confidence and divides by effort, means filling 160 cells.

Pagedeck tried it. The product backlog, the pile of what might get built, had 41 items on it, and Mia spent two days filling in the table. What the finished table revealed was that roughly half of those items were never going to fit into the quarter at all. The hours spent estimating reach and confidence for a six person-month item were simply gone. Half the table had measured things nobody was going to build.

The missing step was a coarse pass before the precise one. All 41 do not need measuring; what this stage needs is an approximate position, not an accurate score.

So the arithmetic came out and two axes stayed: how much it is worth and how much it takes. Stick notes on a wall and 41 items find their positions in half an hour.

Start by turning each candidate into a card on a wall or a shared screen. There are five steps.

1. Agree out loud on what the two axes mean. Whether value is revenue, user count, or churn prevented; whether effort covers development only or design and review as well. Skip this and the same card gets placed on the right by one person and on the left by another.
2. Place effort first. That is the horizontal axis and the people who build it do the placing, with less effort to the left. Effort goes first because it draws less disagreement than value, so the board takes shape quickly.
3. Place value. That is the vertical axis and product and sales do it together, with higher worth toward the top. Opinions diverge here, and the cards people disagree about are the cards this meeting is actually for.
4. Read the quadrants. The four squares have fixed meanings.
   • Top left — high value, low effort. Do these now.
   • Top right — high value, high effort. See whether they can be split; if not, they move into next quarter's plan.
   • Bottom left — low value, quick to do. Slot them in when there is room.
   • Bottom right — low value, high effort. These do not get deferred; they come off the list.
5. Write the result down. For every card in the bottom right, one line on why it isn't happening. Without that, the same card gets debated in the same spot three months later. The line costs ten seconds and saves the whole discussion.

While placing, don't try to fix absolute positions. Whether this card sits to the right of that one is the only judgment needed. Cards get nudged past each other until the relative order looks right. Start converting effort into person-months and a half-hour exercise becomes a two-day one again.

It works best with more than twenty candidates of uneven size. Mixed sizes are what spread the horizontal axis, and spread is what makes the items to cut visible. It also fits when several people are looking at once. A score table only shows its result once every cell is filled, while here positions are visible the whole time cards are moving, so comments land during the meeting rather than after a result has been printed.

Three situations it does not suit.

1. Settling a final order. When six cards land in the top left, this picture does not order those six. For ordering inside one square, move on to RICE or ICE, which multiplies three axes.
2. Candidates that are all a similar size. If everything takes a few days, nothing separates on the horizontal axis and the cards form a single line. Only the value axis is left, and a ranked list does that job faster.
3. Running it by voice only. The power here comes from everyone looking at the same picture. Without a shared screen it does worse than a score table.

The limitation is that both axes are lumps. Value quietly absorbs how many people are reached, how large the effect is for them, and how trustworthy that guess is. So when someone asks why this card sits above that one, the answer falls back on instinct. In a setting where a decision has to be explained, this picture alone does not hold up.

The other problem is the bottom left filling up. Quick work is easy to reach for, and some teams spend a whole quarter clearing that square. Twenty small items finished leaves the product unchanged, but the count of finished items goes up, so it feels like progress, and that feeling is why the square keeps getting picked.

"Let's get these on the matrix and cut the bottom right right here."

A proposal to remove what isn't happening before anything gets measured precisely.

"Is this really on the left of the effort axis? With review it's three weeks."

A request to align on what the effort axis includes.

"Six cards in the top left. We need a separate pass for the order inside it."

Priority within one square does not come out of this picture.

Pagedeck draws this before quarterly planning starts. Mia brings the cards, Theo places them along the horizontal axis, and Sofia and Ravi raise or lower them on the vertical one. Half an hour turns 41 items into ten, and only those ten go on to a table with scores in it.

A common expectation is that the cards spread evenly across the four squares. The drawing shows four equal boxes, so it reads that way. Place a real set of candidates on a board and they cluster in the top right corner. Things get onto a backlog because somebody judged them worth doing, and worthwhile things tend to be large. When the picture comes out clustered, what is wrong is not the picture but the step before it: items of wildly different sizes on one board, or a value axis nobody agreed on, placed generously by each person.

The other is reading the bottom left as easy wins to do first. Low worth but quick looks like a bargain. That square is third in order, though — it is where things get slotted after the top left, and reversing the two ends a quarter with many items touched and no number moved. That is how a product ends up with twenty nice-to-have features attached to it.