Is Your PMO Actually a Value Management Office in Disguise?
Most PMO leaders never sit down and decide to become a Value Management Office. They drift into it.
The questions being asked of the function gradually shift. The reports that used to land cleanly start getting awkward follow-up questions. The conversations at steering group move from "is this project on track?" to "should we even be doing it?" The work itself starts to feel different - more strategic, more political, more economic - without anyone formally changing the mandate.
That is how PMO value management work usually begins: not with a new department, but with a PMO being pulled into decisions about value, capacity and economic consequence that the original mandate was never designed to handle.
If that sounds like you, your PMO is already a VMO in disguise. The recognition usually arrives late, because the language of the function hasn’t caught up with the work.
Here’s how to tell.
Sign 1: You spend more time explaining trade-offs than running reviews
A traditional PMO runs project reviews. Status, milestones, risks, issues. The cadence is rhythmic - weekly, monthly, quarterly - and the conversation is largely about whether each project is meeting its own plan.
A PMO becoming a VMO finds that those reviews keep getting hijacked. Senior leaders aren’t asking whether the project is on track. They’re asking what it’s costing the rest of the portfolio. They’re asking whether the original business case still stands. They’re asking whether the resources tied up in this initiative would create more value somewhere else.
Those are not project review questions. They are portfolio economics questions. And the PMO leader who finds themselves spending more time on the second type than the first is no longer running a traditional PMO - regardless of what the org chart says.
Sign 2: Your dashboards keep getting greener while your sponsors keep getting more frustrated
This is the most common pattern, and the most disorientating. Projects are tracking well. The metrics are improving. Delivery maturity is going up. And yet the people sponsoring those projects are getting less satisfied, not more.
The gap is structural. A dashboard built on project-level metrics will show you how well projects are running. It will not show you whether they’re running on the right things, in the right order, against the right priorities. Green projects can produce a red portfolio - and a PMO whose dashboards say everything is fine while the business says otherwise has already outgrown what those dashboards were designed to measure.
Recognising the gap is the first step. Closing it requires a function that reports on portfolio economics, not just project status. That function is a VMO.
Sign 3: Resource conflicts are the dominant conversation in every steering group
In a healthy portfolio, resource decisions are made calmly and rarely. In most portfolios, they dominate every meeting.
If the conversation in your steering groups is mostly about who gets which people, why the specialist team is overloaded, and whether project A or project B should take priority this fortnight, the function is already operating in VMO territory. Those decisions aren’t governance questions. They’re economic ones, made under the pressure of shared constrained resources.
A traditional PMO mediates those conversations. A VMO answers them - using a coherent view of what each project is economically worth, what each constraint is costing, and what the consequence of each resourcing choice will be across the portfolio.
Sign 4: You’re being asked which projects to stop, not just how to run them better
A traditional PMO is rarely asked to defend the act of stopping a project. The portfolio is treated as a given. The question is how to execute it.
A PMO becoming a VMO finds itself being asked the opposite question, often by the CFO. Which of these projects, if we stopped them today, would we miss the least? Where are we throwing good money after bad? What’s the smallest portfolio we could run and still hit the strategic goals?
Those questions are economic, not operational. Answering them well requires the function to hold both the value side and the delivery side of every project in a single view. That is no longer only a PMO delivery question. It is what a VMO is built to handle.
Sign 5: You’re translating delivery into executive language - and increasingly impatient with the gap
Every experienced PMO leader has had this moment. A senior executive asks why a project is slipping. The accurate answer involves resource contention, dependency mapping, and risk realisation. The useful answer is in pounds, dollars, or strategic consequence.
The function that has started bridging that gap on its own initiative - translating delivery reality into the language executives actually need - has already started doing VMO work. The frustration with how poorly the function’s data feeds executive decisions is itself a sign that the mandate has outgrown the toolkit.
A VMO formalises what an experienced PMO leader is already doing informally. It gives the work the language, the framework, and the legitimacy it currently has to invent on the fly.
What this means in practice
If you recognised your function in two or more of those signs, you are further along the path than you think. The hard part - building the credibility, earning the trust of leadership, learning what questions actually matter - is largely done. What remains is making the shift explicit, deliberate, and properly supported.
That shift does not have to start with restructuring. It does not have to start with new headcount. It does not have to start with fighting for a budget line that doesn’t exist. What it requires is:
- Changing what the function measures - from project status to portfolio economics
- Changing what the function reports on - from delivery dashboards to value, capacity and constraint
- Changing what the function is permitted to decide - from execution discipline to investment-level influence
Each of those is a deliberate choice. None of them is a reorganisation. The function you have already become can be made official without disrupting the function you currently run.
Why the recognition matters
Most PMO leaders who are already doing VMO work get less credit for it than they should, because the language of the function still belongs to the old mandate. Reports describe project health rather than portfolio economics. Job descriptions emphasise governance rather than value. Career conversations talk about delivery maturity rather than strategic influence.
That mismatch matters. It limits the function’s authority. It caps the seniority of the people who lead it. It positions the team as overhead rather than as a source of economic leverage. And it leaves the PMO leader having to justify, over and over, work the business clearly already needs.
Recognising the function for what it has become is the first step toward giving it the authority, language and support it already needs.
Take the next step
If two or more of those signs felt familiar, the PMO to VMO guide is the deeper playbook. It explains how to complete the shift you’ve already started - what to change in what you measure, what to change in how you report, and how to make the case to your executive sponsor without restructuring or fighting for a new function.
