More than half of PMOs set up in organisations are quietly disbanded, restructured, or absorbed into another function within two years. Academic research published through the
Association for Project Management has tracked this pattern for over a decade: PMOs are often short-lived, and their value is difficult to evidence.
Not because the discipline of project management is broken. Because the PMO was set up to fix the wrong problem, with the wrong remit, reporting to the wrong person.
After 21 years of being called in to either rescue a PMO or replace one, we see the same five reasons it goes wrong. None of them are technical. All of them are solvable.
Reason 1: It Was Set Up to Solve the Wrong Problem
The most common origin story for a failing PMO is this. A high-profile project failed, a board asked why, and someone said “We need a PMO”.
That is the wrong answer to the wrong question. A PMO is not a fix for one bad project. It is a permanent capability for governing many projects. If you build one in reaction to a single failure, you build it to perform the autopsy, not to prevent the next one.
The PMOs that survive year two are the ones that were set up with a clear charter: which projects they govern, what decisions they own, and what outcomes they are accountable for. The APM Body of Knowledge sets out three core benefits a PMO must deliver: deployment support, process improvement, and resource flexibility. If your PMO charter doesn’t name those outcomes, it doesn’t have one.
Reason 2: It Was Staffed Too Junior
If the executive view of a PMO is that it produces reports, then it will be staffed by people whose job is to produce reports. Those people cannot challenge experienced project managers. They cannot validate the inputs they receive. They cannot tell the board what the real risk picture looks like.
The PMO becomes a copy-and-paste function. Its outputs are no better than its inputs. And when the outputs are poor, the executive concludes the PMO is not adding value. That conclusion compounds the problem, because nobody is going to invest in a function that has already been written off.
A PMO needs at least one senior practitioner who has actually delivered programmes. Without that, the function cannot do the one thing it exists to do: ask harder questions than the project managers it governs.
Reason 3: It Has No Real Authority
PMOs are often launched with a polite mandate. They can request information. They can recommend standards. They can produce reports. What they cannot do is stop a project, escalate over a sponsor’s head, or force a change in resourcing.
Without authority, the PMO has no leverage. Project managers learn quickly which reports they need to fill in and which they can ignore. The PMO becomes administrative theatre. Visible, expensive, and unable to change anything.
The fix is not bureaucratic. It is governance design. The PMO needs a sponsor at executive level, a defined remit, and a small number of decisions it owns outright. Once those decisions are real, the rest of the function gains traction.
Reason 4: It Measured the Wrong Things
Many PMOs report on activity. Number of projects in the portfolio. Percentage of templates completed. Hours logged against governance forums. None of these tell you whether the portfolio is healthy.
A useful PMO reports on outcomes. Are the projects delivering the benefits they were funded to deliver? Are the dates being held? Are resources being used where they create the most value? Those are the metrics a board cares about. Anything else is noise dressed up as rigour.
If your PMO dashboard can’t answer a single board-level question without footnotes, it is measuring the wrong things.
Reason 5: It Couldn’t Adapt
Organisations grow, restructure, and pivot. The
APM Golden Thread research (commissioned by APM and conducted by PwC Research) shows the project profession now contributes £186.8 billion annually to the UK economy, a 19% increase in five years. The pace of change is real. A PMO built rigidly around one methodology, typically the one its first head championed, will struggle to keep up.
New projects arrive that don’t fit the template. Teams find workarounds. The PMO becomes a gatekeeper to a process that no longer reflects how the business actually works.
The PMOs that survive are the ones that flex. They have a core of non-negotiables: governance, reporting, risk. Around that core, they keep a wider layer of practice that adapts to the type of project being delivered. Waterfall where it fits. Agile where it fits. Hybrid where it has to.
What a PMO That Works Actually Looks Like
It has a clear charter, written and signed off by an executive sponsor.
It is staffed with at least one senior practitioner with real delivery scars.
It owns specific decisions, not just the production of decks.
It reports on outcomes the board cares about, not on activity it can measure.
It flexes with the business, instead of fighting it.
Building that takes three to six months of focused work, not a software rollout.
If your
PMO is approaching its second birthday and the board has started asking what it’s for, that conversation is the warning sign. There is still time to reset it before the function is dismantled.
Book a Free PMO Assessment. No fee. No obligation.
