Guide: Prioritisation
The value vs complexity matrix: how leadership teams should score it
Published by Scott Seaborn, Founder
A simple grid can settle your investment priorities, or quietly undermine them. The difference is how you define the scores and who gives them.
The value vs complexity matrix is one of the most widely used prioritisation tools in business. It is simple: score each opportunity on the value it would create and the effort it would take to deliver, then plot the results on a two-by-two grid.
Product teams use it to rank features. Leadership teams increasingly use it to decide where to invest in digital and AI. That second use is where it most often goes wrong, because the matrix is only as good as the scores behind it and the people who gave them.
What the matrix shows
Each opportunity is placed by two scores: business value on one axis and delivery complexity on the other. That creates four groups.
- Do first: high value, lower complexity. These earn their place at the top of the plan.
- Plan and fund: high value, higher complexity. Worth doing, but they need proper scoping, budget and ownership.
- Quick fixes: lower value, lower complexity. Useful when capacity allows, but they should not crowd out the work that matters.
- Deprioritise: lower value, higher complexity. Stop, rescope or park them until something changes.
The grid is the easy part. The decisions that make it trustworthy happen before anyone plots a single point.
Why it breaks down at leadership level
When a leadership team uses the matrix, the same failures appear again and again.
- One function does the scoring. IT scores complexity and the business scores value, so each side questions the other’s numbers.
- The scales are never defined. A “4 out of 5” for value means something different to finance, operations and sales.
- Scores are agreed in the room. The most senior or most confident voice sets the number, and real disagreement disappears.
- Averages hide the argument. Two people scoring 1 and 5 produce the same average as two people scoring 3, but they are telling you very different things.
- Value is estimated without evidence. The opportunity list came from a workshop or a vendor, not from the people who live with the problem.
The result is a neat chart that nobody fully believes. It gets presented once and the priorities drift back to whoever argues hardest. Alignment has to be built into the scoring, not added afterwards.
How to define business value
Agree what value means for this decision before anyone scores. Choose a small number of value criteria that matter to the business, then write down what a low, middle and high score looks like for each.
Typical criteria include revenue protected or created, cost or time removed, risk reduced, customer experience and the effect on the people doing the work. Where you can, tie each score to something measurable: hours per week, error rates, orders delayed, cash tied up.
Written anchors matter more than the number of points on the scale. They are what make a score from operations comparable with a score from finance.
How to define delivery complexity
Complexity is not just technical difficulty. An opportunity can be easy to build and still hard to deliver. Consider:
- Technical work, including integration with existing systems.
- Data: whether the information exists, is reliable and can be accessed.
- Process change: how much the way people work has to change.
- People and skills: training, roles and the capacity to absorb change.
- Dependencies on other projects, suppliers or decisions.
Score complexity with the people who would have to deliver the change, not only those who would design it.
Who should score
Score across functions, and score independently. Each person scores the same list against the same written scales, without seeing anyone else’s answers. Then bring the results together.
Independent scoring does two things. It stops the loudest voice from setting the result, and it shows you where people genuinely disagree. The gap between how IT and the business score the same item is often the most useful information in the whole exercise.
Reading the result
Look beyond the quadrant each opportunity lands in.
- Look at the spread, not just the average. Items with a wide range of scores need discussion before they are funded.
- Look for shared foundations. Several opportunities may depend on the same data, system or process fix. Fixing that once may be the best first investment.
- Check the evidence behind high-value scores. A high score with nothing behind it is an assumption, not a priority.
From matrix to decision
A ranked list is not a decision. Leadership still needs to agree the sequence, name an owner for each priority and set the measures that will show whether it worked. Record what was agreed and why, so the ranking can be revisited when circumstances change rather than rebuilt from scratch.
A short checklist
- Value and complexity criteria agreed and written down.
- Opportunities drawn from evidence, not just ideas.
- Scoring done independently, across functions.
- Disagreements discussed, not averaged away.
- Shared dependencies identified.
- Owners, sequence and measures agreed.
Slid3rs™ is how we run this: your people score every opportunity against the same written scales for business value and delivery complexity, and the full scoring record stays attached to the result. It follows AI Compass™, which gathers the evidence, and leads into FlowRoom™, where leadership agrees what happens first.
Common questions
What is a value vs complexity matrix?
A prioritisation tool that scores each opportunity on the business value it would create and the complexity of delivering it, then plots the results on a two-by-two grid to show what to do first, what to plan and fund, what to treat as a quick fix and what to deprioritise.
Who should score value and complexity?
People from every function affected by the decision, scoring independently against the same written scales. Complexity in particular should be scored with the people who would have to deliver the change.
How is it different from an impact vs effort matrix?
They are close relatives. Value vs complexity usually defines both axes more broadly: value covers revenue, cost, risk, customer and people effects, and complexity covers data, process change, skills and dependencies as well as technical effort.
Related reading
Next