Why PMOs Fail: The Five Reasons Mid-Market PMOs Get Shut Down in Year Two

Paul Thomas • May 4, 2026

Share this article

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.

Free Project Assessment & Audit, Tailored to You

Not sure where your project really stands? We assess what's happening, and give you a clear and honest picture at no cost. Every engagement starts with understanding your specific situation, because no two organisations are the same.

Totally free. No commitment needed.

Recent Posts

Hand circling a date on a desk calendar with a pen beside a laptop
By Paul Thomas July 16, 2026
Planning a PMO setup? This guide walks through the realistic 3-6 month timeline phase by phase, plus a free assessment to find your own number.
By Paul Thomas July 15, 2026
Most consultancies won't answer the cost question directly. Ask, and you'll typically get "it depends" and a form to fill in. It does depend, but that's not an excuse to be vague about what it depends on. If you're a COO trying to build a business case for the board, three variables actually set the price, and none of them are secret. What actually drives the number Programme size is the first. A single at-risk workstream costs less to stabilise than a portfolio of twelve, scope drives everything downstream. A workstream with one team, one sponsor, and one clear deliverable is a contained diagnostic exercise. A twelve-workstream portfolio with overlapping dependencies and multiple sponsors is a different order of problem entirely, because stabilising one workstream in isolation without understanding its dependencies on the other eleven risks solving the visible symptom while the underlying cause resurfaces somewhere else three months later. Embed duration is the second: recovery engagements typically run three to six weeks, and a straightforward stabilisation, credible plan, honest reporting, a functioning team, costs less than a six-week turnaround with practitioners embedded across multiple workstreams. The difference between the two isn't really about calendar time so much as coverage, how many people need to be physically present, in the room, for how many of those weeks, before the organisation can run the plan on its own. Seniority is the third, and the one most likely to be quietly reduced to save money. We only deploy practitioners with 15+ years of experience, never graduates running a template, and that's a deliberate cost floor, it's also why the fix tends to hold. It's worth being honest about why seniority costs more and is still worth it: a junior consultant working from a template can produce a plan that looks credible on paper. A senior practitioner who has seen a dozen versions of this specific failure pattern before knows which parts of that plan won't survive contact with the actual organisation, and can say so in week one rather than week five. What that seniority actually costs, in public numbers You don't have to take a consultancy's word for what senior delivery talent costs in the UK market. The Association for Project Management's 2025 Salary and Market Trends Survey, the UK's largest annual study of the profession, puts the average project management salary at £52,500, up 10% on 2023, with practitioners in consultancy and energy/utilities sectors averaging £62,500, per the APM Salary Survey 2025 . Embedded recovery work commands more than that average because it's compressed: fifteen-plus years of pattern recognition delivered on a timeline measured in weeks, not spread across a year. There's a useful way to think about what's actually being purchased here. A permanent hire's salary buys a year of their time, spread across whatever the organisation needs that year. A recovery engagement's cost buys weeks of concentrated attention on one specific problem, from someone whose entire value is having seen that problem before. The hourly economics look expensive next to a permanent salary until the comparison is corrected for what's actually being delivered in that window. The cost that never makes it onto an invoice Every cost conversation focuses on what recovery costs. The number that's harder to see, and usually larger, is the cost of inaction. A project drifting for another quarter doesn't just slip its date, it compounds in several distinct ways. The team burns out chasing an unrealistic plan, because nobody has told them the plan is unrealistic, so they keep trying to hit dates that were never achievable in the first place. The best people quietly start looking elsewhere, because skilled practitioners can generally tell when a programme has lost its way faster than the sponsors funding it can, and they don't wait around to find out how it ends. Stakeholder trust erodes in a way that outlasts the project itself, a sponsor burned once by an over-promised, under-delivered programme brings that scepticism into the next funding conversation, and the next, long after the specific project is closed. And the eventual fix costs more because the drift has to be unwound before recovery can even begin, every extra week of a bad plan being followed is a week of decisions made on false assumptions that now need to be found and corrected. By the time a board asks how much it will cost to fix, the more useful question is how much it has already cost to wait. Why nobody publishes a rate card A three-week reporting fix and a six-week multi-team turnaround are different projects with different costs, and any headline number would be wrong for most people who read it. That's not evasion. It's the same reason a surgeon doesn't quote a price before the scan — not because the price is a secret, but because quoting it before the diagnosis would mean quoting the wrong number to almost everyone who asked. Where to start Cost climbs with the number of embedded practitioners, the complexity of stakeholder alignment, and how far a programme has already drifted before anyone calls for help. It does not climb because of methodology, tooling, or brand name. Agile Minds gives every prospective client a free, two-week assessment before any number gets discussed. If you need a figure you can actually take to the board, we should talk .
Blue infographic chart with numbered hexagons and a pencil on a desk
By Paul Thomas July 14, 2026
Not every project needs the same delivery model. This step-by-step guide shows you how to build the right one for yours, then offers a free assessment.
Jaguar and Land Rover logos on a gray building facade
By Paul Thomas June 1, 2026
How AgileMinds built JLR a working agile framework through a real product, not a workshop. A 16-week app and guilds that kept it alive after we left.
Halfords storefront with glass entrance, orange logo, and parked bicycles outside
By Paul Thomas June 1, 2026
How AgileMinds delivered Halfords' unified ecommerce platform on Salesforce Commerce Cloud. Two brands, one basket, over 100 integrations, nine months.
Three people in red helmets and jackets stand outdoors at dusk, looking serious.
By Bernadine Dela Cruz May 29, 2026
How AgileMinds helped E.ON take a virtual power station from proof of concept to commercialised, award-winning solution in six months.
Stressed person at desk with laptop, head in hand, reviewing charts in a bright office
May 24, 2026
Uncover the hidden costs of project team burnout, like knowledge loss & attrition. Contact us for strategies to mitigate these issues.
Team collaborating around a laptop with papers, notebooks, coffee, and a smartphone on a desk.
By Paul Thomas May 4, 2026
Most failing projects send warning signs months before the board notices. Here’s how to spot them, and how to recover before it’s too late. Free assessment.
Colleagues in a meeting, leaning over documents and pointing at a chart on a conference table.
By Paul Thomas May 4, 2026
Explore why 70% of digital transformations fail due to middle management issues. Contact us for tailored solutions today!