The Real Cost of Not Having a Value Management Office
Most executives can tell you what their PMO costs to run. Headcount, tooling, overhead - it’s a defensible number on a budget line.
Almost none of them can tell you what running their portfolio without a Value Management Office is costing them. Not because the cost isn’t there. Because nothing in the standard reporting stack is designed to find it.
That invisibility is the problem. A cost you cannot see is a cost you cannot defend against. And in many multi-project organisations, the cost of not having a VMO is likely to be far larger than the cost of building the capability.
This is the real cost of poor project portfolio management: value erosion that standard delivery reporting was never designed to expose. Here is where to look for it.
The cost of running the wrong portfolio
Every active project in your portfolio is consuming capacity that could have been spent on something else. That is true even when the project is delivered on time, on budget, and to specification.
The question that almost never gets asked is: of all the things this organisation could have done with this capacity, was this the highest-value choice?
A traditional PMO does not ask this question. It assumes the portfolio is correct and focuses on whether the chosen projects are being delivered well. That is a reasonable assumption only if the projects entered the portfolio through a process that compared them economically against everything else competing for the same resources.
In most organisations, they didn’t. Projects get approved because the business case looks compelling in isolation, the sponsor is senior enough, or the budget is available. What rarely gets calculated is what approving that project does to everything already in flight - which projects it will quietly delay by competing for the same constrained resources, and what those delays will cost the business.
The cost of running the wrong portfolio is not the cost of the projects you chose. It is the value you didn’t realise from the projects you should have chosen instead, plus the damage approving the wrong ones did to the projects already underway.
The cost of delay nobody calculates
In most portfolios, project delay is treated as a scheduling event. The slip gets reported. The mitigation plan gets discussed. The new date gets entered in the system.
What almost never gets calculated is what that delay is economically worth.
In project economics, this is closely related to drag cost: the financial consequence of time being added to the path that determines when value can be realised.
If a project will return five million pounds in annual revenue once delivered, every month of delay is worth around four hundred thousand pounds in deferred value - and that is before you account for the strategic cost of arriving in the market later than a competitor, or the reputational cost of slipping commitments to customers.
Multiply that across a portfolio of twenty or thirty projects. Add the projects that finish so late their original business case no longer holds. Add the projects that get cancelled after consuming most of their budget. The numbers become significant very quickly.
A traditional PMO reports delays as red status indicators. A VMO reports them in financial and strategic terms - deferred revenue, delayed savings, missed market windows, or avoidable penalty exposure. The difference is not cosmetic. It is the difference between a problem the business shrugs at and a problem the business acts on.
The cost of pointing your best people at the wrong work
In most multi-project organisations, there is a small group of people - sometimes a single team, sometimes a single specialist - whose hours are the limiting factor on overall delivery. Everything important eventually depends on them. They are the constraint.
What those people work on, in what order, is the single most consequential resource allocation decision the business makes every week. It determines how much value the portfolio actually produces.
Without a VMO, that decision is usually made through a combination of seniority, escalation, and whoever shouted loudest in the last steering group. The constrained resource gets pointed at the work that is most politically visible, not the work that would create the most economic value.
The gap between where those people’s time currently goes and where it would create the most value across the portfolio is one of the largest invisible costs in any complex business. It does not show up on a P&L. It does not show up in a project status report. But it is real, it is significant, and it is calculable - if anyone has the language to calculate it.
The cost of not knowing when to stop
Every portfolio contains at least one project where the economics have quietly turned. The cost remaining to complete is now higher than the value remaining to be realised. The business case has eroded - through delay, scope change, market shift, or competitor action - to the point where continuing no longer makes financial sense.
Most organisations don’t see that moment coming. The project continues because cancelling it would be politically expensive, because nobody is formally asked to test whether the original case still holds, and because the function that should be asking that question is busy reporting on whether the project is hitting its milestones.
The cost of carrying on with projects that should be stopped is one of the most expensive forms of portfolio waste. Capital is consumed for diminishing returns. Constrained resources are tied up on work that would create more value elsewhere. And the political cost of eventually cancelling rises with every month the decision is deferred.
A VMO is the function that asks the stop question explicitly, in economic terms, on a regular basis. In many organisations, the savings from cancelling one badly deteriorated project could exceed the cost of building the VMO capability that found it.
Why these costs compound
Each of the costs above looks survivable in isolation. A slipped project. A misallocated specialist. A project that should have been stopped six months earlier.
The problem is that they don’t occur in isolation. They compound. The wrong projects in flight delay the right ones. Misallocated specialists slow the constraint. Projects that should be stopped consume the capacity that could be rescuing the projects that should be accelerated. Each problem makes the next one worse.
And because none of these costs sit on a single line in the management accounts, they are easy to discount as soft, theoretical, or unmeasurable. They are none of those things. They are real costs being paid in real money, every quarter, by businesses running portfolios without an economic management function.
What makes them feel theoretical is simply that nobody is currently looking for them.
What a VMO costs by comparison
A VMO is rarely a new headcount line. In most organisations, it is an evolution of the function the business already has - the same team, with a wider mandate and a sharper analytical toolkit.
The investment required is usually in three things: changing what the function measures, changing what it reports on, and giving it the data and tools needed to put economic numbers on portfolio decisions that are currently being made on instinct.
Against the recurring cost of running the portfolio blind, that investment is small. The first major portfolio decision the function improves - one project re-sequenced, one acceleration justified, one cancellation made earlier than it would otherwise have happened - can easily justify the entire initiative.
The harder question is not whether a VMO is worth funding. It is how long the business can afford to keep operating without one.
Take the next step
If you suspect the costs above are real in your organisation, the PMO to VMO guide explains how to make them visible. It walks through what to start measuring, what to report on, and how to make the economic case at executive level - without restructuring or fighting for a new function.
