How Value Management Offices Handle Competing Priorities
"Everything is priority one."
It is the most common phrase in multi-project organisations, and it is usually said with frustration. Sometimes it is said as a joke. Either way, it describes a real condition: a portfolio in which every project has been declared important enough to win the next argument about resources.
Most attempts to fix this treat it as a discipline problem. The organisation needs better governance. Tighter approval gates. A more rigorous prioritisation matrix. A senior leader willing to make tough calls.
Those moves help at the margins, but they rarely fix it. Because "everything is priority one" is not primarily a discipline problem. It is an economic one. And the function built to handle it is a Value Management Office.
Managing competing project priorities is not about forcing every sponsor through a better scoring matrix. It is about making the economic consequences of priority decisions visible.
Why conventional prioritisation methods fail
Most organisations already have a prioritisation method. MoSCoW. Weighted scoring. RICE. Or, more often than anyone likes to admit, executive sponsor seniority. Some combination of all four.
These methods work reasonably well inside a single project. They struggle at portfolio level because they share three structural weaknesses:
- They prioritise projects in isolation. Each business case is scored on its own merits, without reference to what approving it will do to everything already in flight.
- They don’t see the constraint. A project ranked highly by every prioritisation criterion can still be the wrong project to start - if it depends on a resource that is already fully committed to higher-value work.
- They produce static rankings. The list reflects what mattered when the scoring was done. It does not update as conditions change, as new information arrives, or as projects already in flight reveal their true economics.
The result is a prioritisation list that looks defensible on paper and falls apart in practice. Within weeks, every project on the list is being treated as priority one by the people delivering it, because the list does not survive contact with the reality of shared constrained resources.
The real problem competing priorities are pointing at
When a portfolio descends into "everything is priority one", the actual signal is rarely about prioritisation discipline. It is about three connected economic facts that the organisation has not made visible:
- There is more demand on the portfolio than the constrained resources can carry. The list of approved work exceeds the capacity to deliver it.
- The economic difference between projects is not being calculated. Two projects might be ranked equally on a scoring matrix while being worth very different amounts to the business.
- The economic cost of delay is invisible. Slipping project A by three months looks identical on a status report to slipping project B by three months, even when one delay costs ten times more than the other.
Until those three facts are visible, no amount of discipline will hold the prioritisation in place. People will keep escalating, because escalation is the only mechanism that actually changes resource allocation when the underlying economics are invisible.
What a VMO does differently
A VMO does not start with a better ranking method. It starts by making the underlying economics visible. Once that is done, prioritisation stops being a political negotiation and becomes an economic decision the organisation can defend.
Concretely, a VMO changes four things about how competing priorities are handled:
First, it makes the constraint explicit. In most portfolios there is a specific group of people, skill set, or asset that limits how much work the organisation can actually deliver. A VMO names that constraint, protects it, and uses it as the anchor for sequencing. The question shifts from "what should we start next?" to "what should the constraint work on next to produce the most value?"
Second, it gives every project an economic profile. Not a scoring matrix - a view of what each project is worth, how much value is at risk if it slips, and how the economics change as conditions evolve. That profile is updated continuously, not annually.
Third, it treats sequencing as a portfolio decision, not a project decision. A new project entering the portfolio is evaluated for what it will do to everything already in flight. An acceleration is evaluated for what it will cost the projects it deprioritises. A cancellation is evaluated for what it frees up. The full economic consequence of every choice is visible before it is made.
Fourth, it identifies where targeted investment in acceleration would produce disproportionate economic return. Not every task is equally worth speeding up. A small investment in reducing the duration of one specific activity - extra capacity on the right task at the right moment - can pull a project’s delivery date forward by weeks. And because projects share constrained resources, that acceleration can create value beyond the project itself: capacity freed up sooner, downstream projects able to start earlier, deferred value brought back into the window. A VMO is the function that calculates whether the economic benefit of acceleration exceeds the cost of intervention - and gives leadership the numbers to defend the spend.
At its most sophisticated, this thinking goes further. The highest-return acceleration is sometimes counterintuitive. A task with little apparent economic value in isolation can become the most important investment in the portfolio if accelerating it gets the right work to a constrained resource sooner, or releases that constraint for higher-value work downstream. And because each intervention changes the system, the next move has to be calculated from the new state, not the old one. The function operates as a continuous decision system, not a one-shot optimisation.
When those four things are in place, "everything is priority one" stops being a viable position. The economics of the portfolio become the starting point for prioritisation, and the function’s job is to make those economics visible to the people making the decisions.
What changes in the conversation
The visible test of whether a VMO is actually handling competing priorities is what happens in the steering group.
In a function that has not made this shift, prioritisation conversations are dominated by who is asking, how loudly they are asking, and how recently the last crisis was. The decisions feel political. The same projects come up again and again. The resourcing changes constantly, often without anyone formally deciding to change it.
In a function operating as a VMO, those conversations look different. Each priority decision is presented with its economic consequence attached. Accelerating project A means deferring project B by a calculable amount, costing the portfolio a calculable amount, and creating a calculable benefit elsewhere. The conversation becomes an economic trade-off rather than a political one.
That shift is what most senior leaders are actually asking for when they say they want better prioritisation. They are not asking for a more rigorous matrix. They are asking to make decisions with the economic consequences visible. A VMO is the function that puts those consequences on the table.
The deeper move underneath the practical one
There is a more fundamental change underneath all of this, and it is worth naming directly.
Most organisations prioritise based on the value they believe a project will deliver in the future. A VMO also prioritises based on what each project is currently costing the portfolio in capacity, sequencing, and deferred value from everything else.
Those two perspectives produce very different decisions. The first asks "which projects look most attractive?" The second asks "given finite shared capacity, what is the economic return on how we are running the portfolio right now, and where should focus shift to maximise overall value?"
The second question is one most portfolios have never been able to answer. A VMO is the function built to answer it - and answering it is what stops competing priorities from being a permanent feature of how the business runs.
Take the next step
If "everything is priority one" sounds familiar in your organisation, the PMO to VMO guide explains how to make the underlying economics visible - so prioritisation stops being a political negotiation and becomes a decision the business can defend. It walks through what to start measuring, what to report on, and how to make the case at executive level.
