A short note on the VMO, and why it may be the most useful evolution in project management right now.
Alex Rodov · PMO Leadership, PMP, Microsoft MVP Alumni
I've sat through this meeting more times than I can count.
The PMO presents its quarterly review. The numbers look good:
- Projects are on schedule.
- Budgets are under control.
- Governance is being followed.
- Delivery targets are being met.
Then someone asks the question that changes the room:
"So what did this actually do for the business?"
Suddenly, the dashboard has less to say.
Because delivering a project successfully and delivering business value are two different things.
And most PMOs were built to measure the first.
A Simple Idea Called the VMO
There's a name gaining attention for the next step: the Value Management Office, or VMO.
Don't let the acronym put you off. The idea is simple.
A traditional PMO asks:
- Is the project on time?
- Is it on budget?
- Is it on scope?
- Are governance requirements being met?
A VMO asks one more question:
Is this project still worth doing?
More specifically:
Is it still creating the value we promised when we started?
That question is harder to ask.
It means being willing to stop a healthy project because the business case has changed. It means looking at a portfolio like an investment portfolio and asking what each initiative is actually returning.
A project can be perfectly managed and still be the wrong project.
A PMO earns trust by finishing projects. A VMO earns a seat at the table by knowing which projects deserved to be finished.
From Project Delivery to Business Outcomes
This is the shift at the heart of value based project management.
Traditional project reporting focuses heavily on delivery performance:
- Schedule
- Cost
- Scope
- Risks
- Milestones
- Resources
Those metrics matter.
But they don't always answer the executive question:
What changed because we invested in this project?
A value focused approach adds another layer.
For example:
- Did the project increase revenue?
- Did it reduce operational risk?
- Did it improve customer experience?
- Did it reduce costs?
- Did it create a measurable strategic advantage?
- Did the expected benefits actually materialize?
This changes the conversation from "Did we deliver?" to "Did delivery matter?"
That is where VMO thinking becomes powerful.
This Shift Is Already Happening
The move toward more strategic PMO leadership is already underway.
A decade ago, only about a third of PMOs could say they had a clear mandate. Today, that figure is over half.
Nobody necessarily announced the transition.
It happened gradually as stronger PMO leaders started asking better questions.
Instead of opening a leadership meeting with delivery statistics alone, they increasingly talk about what the work actually changed:
Revenue protected. Risk avoided. Benefits realized. Strategic objectives advanced.
That's VMO thinking.
Many organizations simply haven't put the name on the door yet.
Why the VMO Matters Now
Here's the uncomfortable part.
Measuring value has always been difficult.
It requires teams to:
- Track expected benefits.
- Keep business cases current.
- Connect projects to strategic objectives.
- Measure outcomes after delivery.
- Revisit assumptions when business conditions change.
Most PMOs already wanted to do more of this.
The problem was time.
Project professionals have historically spent enormous amounts of effort collecting updates, preparing reports, reconciling information, and building executive presentations.
That is changing.
As AI takes over more of the reporting and data collection workload, it gives PMOs something they desperately need:
time to think about value.
AI doesn't create a VMO.
It simply removes one of the biggest practical excuses for not becoming one.
The AI Advantage: Less Reporting, More Judgment
This is where AI can change the role of the PMO.
Imagine a system that can continuously process project data and surface:
- Schedule variance
- Cost variance
- Resource constraints
- Emerging risks
- Portfolio trends
- Performance changes
The PMO doesn't have to spend Friday afternoon assembling the report.
Instead, the conversation can move toward the questions that actually matter:
Why is this happening?
What does it mean for the business?
Should we continue investing?
What value are we protecting or creating?
That is a much more strategic use of project management expertise.
The technology handles more of the information layer.
The human provides the judgment.
Where I'd Start
You don't need a new department.
You don't need a new executive title.
And you probably don't need another transformation program.
Start with your three biggest projects.
For each one, ask:
If we were deciding today, knowing what we know now, would we still say yes?
Then add one value metric next to your existing delivery metrics.
Just one.
It could be:
- Revenue impact
- Cost savings
- Risk reduction
- Customer impact
- Benefit realization
- Strategic contribution
Let leadership get used to hearing the PMO talk about outcomes, not just dates.
Then expand from there.
The name can come later.
The habit is the real shift.
The Future of the PMO Is About Value
The PMO doesn't need to disappear.
It needs to evolve.
The future belongs to organizations that can connect project execution, portfolio decisions, and business value in one continuous conversation.
That's what makes the VMO idea so compelling.
It isn't about creating another layer of bureaucracy.
It's about asking whether the work deserves the resources being spent on it.
And in an environment where AI can increasingly automate reporting, analysis, and administrative project work, that question becomes even more important.
Because when machines handle more of the reporting, people have more time to decide what is worth doing.
The PMOs people remember won't be the ones that delivered the most. They'll be the ones that knew what was worth delivering.
Alex Rodov
Top comments (0)