Why do priority lists fail?
Because they are almost always wish lists ordered by age or by the seniority of whoever asked. A list where everything is marked high priority informs nothing: it just moves the decision to execution time, where it gets made by whoever has the emptiest calendar.
The recognizable symptom is that the list never changes. If in six months nothing was dropped, there was no prioritization: there was accumulation.
How do you score impact without inventing numbers?
By anchoring it to something you already measure. An impact that cannot be expressed through an existing metric is usually a hunch dressed up as a project.
Three valid ways to express it: money per year, hours freed per year, or risk avoided with an estimated probability. If an initiative fits none of them, the useful question is not how it scores but why it is on the list.
Be explicit about uncertainty: an estimate with a range — “between X and Y” — is more honest and more arguable than a single number nobody can defend.
What makes up effort, besides time?
Four components, and time is the least decisive:
- Weeks of work. The obvious estimate.
- Dependencies. How many areas or vendors have to coordinate. Each one multiplies the real timeline.
- Quality of the data required. An initiative that needs clean data you do not have hides a whole project inside it.
- Risk if it goes wrong. Touching billing is not the same as touching the blog.
What do you do with each quadrant?
| Impact | Effort | Decision |
|---|---|---|
| High | Low | Do it now. These are the quick wins that buy credibility for everything else. |
| High | High | Plan it in phases, with a first delivery that proves something. |
| Low | Low | Only if there is room. Never before a high-impact one. |
| Low | High | Drop it. These are the projects done “because we can.” |
The quadrant that generates the most value is the last one, even though it produces nothing: dropping things explicitly frees capacity and, above all, ends the argument.
Why start with the quick wins?
Not for ease, but for internal politics. An organization that has spent months hearing about digital transformation without seeing anything develops scepticism, and that scepticism makes everything that comes after more expensive.
A first visible delivery in weeks buys the patience needed for the three-month projects. Starting with the big, correct project is technically defensible and organizationally fragile.
How do you keep the prioritization alive?
By reviewing it on a fixed rhythm with the same criteria. A matrix scored once and filed turns back into a wish list within months, because new requests come in without passing the filter.
Two rules that help: nothing goes on the list without a score, and every review has to be able to drop something. It is exactly what a Digital Roadmap delivers — not the list, but the criteria that keep it alive.