Your PMO is probably delivering value. Can you prove it?

Every PMO leader I've worked with believes their office delivers value. Most of them are right. Almost none of them can prove it in a way that survives a budget review.

That gap — between value delivered and value demonstrated — is where PMOs quietly die. Not in a dramatic restructuring announcement, but in a spreadsheet, during a cost-cutting exercise, when someone senior asks a question nobody has a defensible answer to: what exactly are we getting for this?

PMI's PMO practice guide addresses this head-on in Step 9 of the PMO Value Ring: value delivery. It's the step where a PMO stops describing what it does and starts measuring what it changes.

The uncomfortable difference between activity and outcome

Ask most PMOs what they delivered last quarter and you'll get a list of activities. Templates published. Governance forums held. Dashboards maintained. Project managers trained. Status reports issued.

All real work. None of it an outcome.

An activity is something the PMO did. An outcome is something that changed in the organisation because the PMO did it. "We ran fourteen governance forums" is an activity. "Budget overruns dropped from 31% of projects to 12% over three quarters" is an outcome.

The reason PMOs so often struggle to defend their budgets is that they've spent years reporting the first category while assuming leadership would infer the second. Leadership never infers it. You have to show them.

What Step 9 actually asks you to do

The value delivery step is built on a simple premise: for every service the PMO provides, there should be a promised outcome, and for every promised outcome, a measurable indicator tied to it.

That means starting from commitments you already made — in service agreements, in stakeholder conversations, in whatever you told the business you'd improve — and asking honestly whether you can evidence it. It's worth working through where your own PMO has evidence and where it has assertions:

Performance impact

Are projects actually more likely to succeed since you got involved? On-time completion, budget adherence, scope stability.

Operational efficiency

Has delivery got faster or leaner? Cycle times, rework volumes, resource utilisation.

Cost management

Has money been saved or protected? Reduced overruns, cost avoidance through earlier risk identification.

Risk mitigation

Are fewer things blowing up? High-impact risks retired before they hit, frequency of unplanned disruption.

Resource optimisation

Are the right people on the right work? Allocation efficiency, projects staffed with qualified managers.

Strategic alignment

Is the portfolio pointed at the strategy? Proportion of projects traceable to a stated objective.

You don't need all six. You need two or three that matter to the people who decide your budget, measured consistently, over a long enough period that the trend means something.

The baseline problem nobody wants to talk about

Here's where most value measurement efforts fall apart. You can't demonstrate improvement without a starting point, and most PMOs realise they need a baseline about eighteen months after the moment they could have captured one.

If you're standing up a PMO now, or launching a new service, capture the "before" state before you touch anything. Project success rates. Average schedule variance. How long a change request takes to get approved. It will feel like unnecessary administration in month one. It will be the most valuable dataset you own in month twelve.

If you missed the window — and most of us have — you can still reconstruct partial baselines from historical project records. Messier and more caveated, but a well-documented estimate beats no comparison at all.

Measurement is only half the job

Measuring value and communicating value are two different disciplines, and being good at the first doesn't make you good at the second. A PMO can build an immaculate metrics framework and still lose its funding because the results sat in a dashboard nobody senior ever opened.

Numbers establish credibility, but they don't create conviction on their own. What moves an executive is the story those numbers support: this is what was happening before, this is what we changed, this is what happened next, and here's what it means for the things you care about.

That story needs telling in different registers for different audiences. Your CFO wants financial impact in one page. Your project managers want operational detail. Your steering committee wants trajectory. Same underlying data, packaged three ways, on a cadence matching how the organisation already makes decisions — not one that suits the PMO's convenience.

When the numbers are bad

If you measure value delivery honestly, at some point results will come back worse than you promised. This is not a reason to stop measuring. It's the entire point of measuring.

A gap between expected and actual outcomes is diagnostic information. Maybe the original value proposition was unrealistic. Maybe the service was designed for a problem the organisation doesn't have. Maybe delivery is bottlenecked somewhere fixable. Each points to a different remedy.

That's a fundamentally stronger position than one built on unfalsifiable claims of value — because a PMO that measures itself rigorously has already answered the harder question about whether it deserves trust.

Where to start this week

You don't need a measurement framework to begin. You need one number.

Pick the single outcome your most important stakeholder cares about most. Find out what it looks like today. Write it down with the date. Then decide how you'll check it again in ninety days.

That's Step 9 in its smallest usable form. Everything else — indicator categories, reporting cadence, value narrative, gap analysis — is scaffolding around that one honest habit: deciding what you're going to change, then actually checking whether you changed it.

Most PMOs never do this. The ones that do stop having to justify their existence, because the answer is already on the page.

Next in this series

The PMO that got cut had excellent numbers →