Prioritisation Matrix: Effort vs Value Without Pretending It Is Exact Science
Somebody in the room will eventually say that the scores do not mean anything. They are right, and it is the least useful moment in the session, because the numbers were never the product. The product is what happens when a group has to place the same item on two axes at once and discovers that they disagree about which axis it sits high on.
An effort and value grid is a structured conversation with a picture attached. Section 5 of the PMBOK® Guide Eighth Edition describes it among the tools available to a project. It earns its place by being quick, visible and hard to argue with in the abstract. What it does not do is calculate a decision, and treating a set of scores as though it has is the failure mode worth guarding against.
What the grid is doing
It forces two judgements to be made separately. People conflate them constantly: a thing that is hard is described as unimportant, and a thing somebody wants badly is described as easy. Splitting the two apart produces four positions, and each carries a different kind of decision.
High value and low effort is the obvious corner, and the genuinely useful question there is why these items have not already been done. Usually the answer is that nobody owned them, which is a management problem the grid has just exposed.
High value and high effort is where the real planning sits. These items need sequencing, funding and a decision about what they displace. Placing one here is the beginning of a conversation, and a grid that leaves this quadrant crowded has not finished its work.
Low value and low effort is where most disagreement happens, oddly enough. Small items accumulate, and doing them all consumes a surprising proportion of a team's capacity. They are worth batching, and they are worth saying no to as a group at a defined point.
Low value and high effort is the corner people avoid discussing, because something is usually in it that a senior person asked for. Naming that plainly, in a room, with the alternatives visible, is the most valuable thing the grid does all afternoon.
Where the numbers mislead
False precision arrives first. A scale of one to ten invites arguments about whether something is a seven or an eight, and the difference carries no information at all. Three bands, or even two, produce the same placement with less ceremony and fewer arguments nobody learns anything from.
Value gets defined by whoever is most present. The sponsor's priorities score highly because the sponsor is in the room describing them, and the operational pain felt by twenty people in a depot is represented by nobody. This is the single largest distortion in most prioritisation sessions, and it is fixable by inviting different people.
Effort gets estimated by the wrong hands. A figure produced by someone who will not be doing the work tends to be optimistic in a particular direction, and the items that suffer are the ones whose difficulty lives in data quality, integration or an unglamorous migration. Where an effort score matters, it should come from the team that will carry it.
Forty minutes a shift
A haulage company was building a driver application and ran a prioritisation session on its remaining backlog. Near the bottom of the grid, scored low value and low effort, sat a request to stop the app asking drivers to enter a load reference they had already scanned at the gate.
It stayed at the bottom for two rounds. The sponsor's attention was on a delivery tracking feature the sales team wanted for customer conversations, which sat high on value because the person who wanted it was explaining why it mattered.
A depot manager attended the third session, mainly by accident. The duplicate entry, she explained, was not a small irritation. It happened at every drop, drivers worked around it by writing references on their hands, the resulting mismatches generated queries that her team spent most of a morning clearing each week, and the time cost across sixty drivers came to something close to forty minutes a shift. The item moved to the top corner and was delivered in a fortnight. Nothing about the scoring method had changed; the room had. Building the habit of asking whose value is being scored, and whose effort, is practical tool use that Omega's PMP® Exam Preparation works at directly.
Running one honestly
Get the people who feel the consequence into the room, alongside the people who will do the work. A grid scored by a leadership group is a record of what leadership believes, which is useful information and not the same thing as a priority order. Fifteen minutes from somebody who does the job daily will move more items than an hour of debate among people who do not.
Treat the output as a position to be revisited. Capacity changes, facts arrive, and a grid that was right in March will be misleading by July. Re-running it takes forty minutes and is far cheaper than delivering a sequence that stopped making sense months earlier.
For a PMP® candidate, whenever a scenario describes a prioritisation exercise, the thing to notice is who supplied the inputs. Where a description mentions a stakeholder group whose work is affected and who was not consulted, the technique is not the problem, and the response that helps is widening the input rather than refining the method.
The grid is worth an afternoon whenever a backlog has grown past the point where anyone can hold it in their head. Use coarse bands, invite one person who will be affected and is not normally invited, and pay particular attention to anything that lands in the expensive corner with a senior name attached to it.
Interested in going further?
Knowing which decision a tool is fit to support, and where its output stops being evidence, is a large part of using any technique well. Omega's PMP® Exam Preparation works through the practical tools alongside the judgement each one needs.
The PMBOK® Guide Eighth Edition sets the prioritisation matrix among the other tools a project draws on, which is a useful way to see where it fits.
Ad · Amazon affiliate link.
References
A167: Project Charter Explained: Purpose, Content and Common Misunderstandings
A168: Business Case vs Project Charter: What’s the Difference?
A169: Assumption Log vs Risk Register
A170: Decision Log: The Forgotten Project Control
A171: Change Log vs Issue Log
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
