I've seen a PMO dissolved six weeks after publishing the best quarterly results in its history.
Project success rates up. Overruns down. Cycle times shorter. Every metric they'd committed to, met or exceeded, documented properly, reported on schedule.
And when the restructuring came, nobody in the room fought for them.
That's not a measurement failure. That's a recognition failure — and it's the problem PMI's PMO practice guide addresses in Step 10 of the PMO Value Ring: value recognition.
In my last article I wrote about Step 9, value delivery — the discipline of proving impact with evidence rather than assertion. Step 10 is the uncomfortable sequel. You can deliver value, measure it rigorously, report it faithfully, and still lose, if the people who matter don't feel it.
Two different questions
Step 9 answers: has the PMO achieved what it said it would? That's an evidence question. Objective, quantitative, settled by data.
Step 10 answers: do our customers see us as a valuable partner? That's a perception question. Subjective, relational, settled by how people feel when your name comes up in a meeting you're not in.
Most PMO leaders treat the second as a consequence of the first. Deliver well enough, the reasoning goes, and recognition follows automatically.
Delivered value and perceived value are separate quantities, and the gap between them is where PMOs get quietly written off.
What perception looks like when you measure it
The indicators in Step 10 feel unfamiliar to leaders trained on delivery metrics, because they're not about outputs at all. They're about standing.
- Trust and credibility
- Do stakeholders act on your data without independently verifying it first? A PMO whose numbers get double-checked by three departments has a credibility problem regardless of how correct those numbers are.
- Strategic partnership
- Are you invited into decisions early, or informed of them late? Free to measure: look at the last five significant initiatives. How many involved the PMO before the business case was approved?
- Relationship and collaboration
- Governance generates friction by design. Some PMOs generate friction people accept as worthwhile; others generate friction people route around. Same process, entirely different outcome.
- Innovation and adaptability
- Are you seen as evolving with the organisation, or as the office enforcing last decade's templates? A reputation for rigidity is durable and damaging.
- Willingness to recommend
- Would your customers advocate for your services to a peer? Would they advocate for your budget?
The gap is the finding
The valuable output of Step 10 isn't the perception score. It's the distance between what you measured in Step 9 and what people believe in Step 10.
| Delivery | Perception | What you actually have |
|---|---|---|
| Strong | Weak | A communication problem. You're doing good work invisibly. The fix is narrative and visibility, not more delivery effort. |
| Weak | Strong | A credibility risk. Goodwill is buying you time you haven't earned, and it will run out abruptly. |
| Weak | Weak | A service design problem. You're probably delivering things nobody particularly wanted. |
Same organisation, three completely different remedies. You cannot tell which you're facing without measuring both sides. Running Step 9 without Step 10 leaves you half-blind: you know what you achieved, but not what it bought you.
Recognition is built, not earned
The instinct when you discover a perception gap is to work harder. It's almost always the wrong response. Three practices matter more, and none involves delivering more.
Ask directly, on a repeating cycle
Perception surveys are ordinary practice everywhere except, oddly, in PMOs — where leaders often assume they already know what stakeholders think. Segment responses by group, because executive sponsors and project managers frequently hold opposite views of the same PMO. Repeat at intervals so you're tracking a trajectory, not a snapshot. The asking itself does work: seeking feedback signals that you take the relationship seriously.
Tell stories, not just statistics
A dashboard proves your case. A story makes someone care about it. People remember the initiative you rescued. They do not remember the 14% figure, even when the 14% is what actually mattered.
Bring stakeholders into the interpretation
Workshops where customers map for themselves how PMO services connect to outcomes they care about produce a different quality of recognition than any presentation can. When people work out your value on their own, they own the conclusion. When you present it to them, they evaluate it — and evaluation invites scepticism in a way discovery doesn't.
Why this step closes the loop
The flywheel metaphor earns itself here. A PMO that's recognised gets invited into initiatives earlier. Earlier involvement means better positioning to deliver real value. Better delivery generates stronger evidence. Stronger evidence, communicated well, deepens recognition further.
A PMO that isn't recognised gets involved late, inherits problems it had no hand in creating, delivers compromised results, and finds its evidence unpersuasive — which erodes recognition further. The same wheel, turning the other way.
Neither direction is an accident. Both are the accumulated result of whether anyone was deliberately managing perception alongside performance.
One thing to do this quarter
Ask five stakeholders a single question, and don't defend the answer:
If they struggle to answer, you have a recognition problem — regardless of what your metrics say. If they answer immediately and specifically, you have something more valuable than a good quarter. You have a constituency.
That's the difference between a PMO that survives the next restructuring and one that doesn't. It was never really about the numbers.
Measure both sides
The delivery assessment covers eight dimensions of capability. Run it separately with a sponsor, a project manager and an operations lead — where they disagree is usually more diagnostic than where they agree.
Open the assessment