The PMO Graveyard Is Full of Good Intentions
Across the UK's SME landscape, the same story plays out with depressing regularity. A growth-stage business reaches the point where ad-hoc project delivery is no longer sustainable. Someone — usually a CEO, COO, or a newly hired Operations Director — decides it's time to set up a proper PMO. A framework is chosen, templates are built, and a kickoff announcement goes out. Twelve months later, the whole thing has quietly died.
The tragedy isn't that the idea was wrong. PMOs genuinely transform delivery performance when they're built well. The tragedy is that the failure modes are almost always the same, and almost always avoidable.
This article covers the six most common reasons SME PMOs collapse in their first year — and what to do instead.
Mistake One: Building for the Enterprise, Not the Business
The single most common PMO failure mode is importing an enterprise-grade framework wholesale into an SME context. Prince2 governance boards, full MSP programme structures, four-level reporting hierarchies — these are tools designed for organisations with hundreds of staff, dedicated programme offices, and months of setup time. Dropped into a 60-person business, they create friction without value.
SME leaders don't need the full PMBOK. They need just enough structure to get visibility, manage risk, and make decisions faster. The right PMO for your business is the one your people will actually use — not the one that looks impressive in a governance framework document.
Start with three things: a consistent project intake process, a weekly status dashboard, and a clear escalation path. Build from there. Everything else is optional until the business asks for it.
Mistake Two: No Executive Sponsor With Real Authority
A PMO without a genuine executive sponsor is a car without fuel. It looks like it should work, but it goes nowhere. Sponsorship doesn't mean someone agreed to have their name on the launch email. It means an individual at C-suite or board level who will actively defend the PMO's recommendations, enforce governance decisions, and be visibly seen using the outputs.
When resource conflicts arise — and they will — only executive authority can resolve them. When a department head decides the PMO's reporting requirements are too burdensome — and they will — only executive authority can hold the line. Without this, the PMO gradually gets ignored and eventually dismantled.
Mistake Three: Prioritising Process Over Outcomes
New PMOs often spend their first months building process. Templates, methodologies, governance frameworks, tooling — all before they've delivered a single visible win for the business. This is a fatal error.
The business case for a PMO is built on outcomes, not on the elegance of your RAID log template. Your first ninety days should be focused on finding one or two projects in difficulty and making them demonstrably better. Show the business what good looks like before you ask them to change their working habits.
"A PMO that can point to three rescued projects in its first quarter will survive. A PMO that spent that same quarter writing methodology documents will not." — Common wisdom among seasoned PMO leads
Mistake Four: Trying to Own Everything
PMOs that position themselves as the owners of all project activity quickly become bottlenecks. Every decision gets routed through them. Teams slow down. Resentment builds. The PMO becomes associated with delay rather than delivery.
The best SME PMOs are enabling functions, not controlling ones. They set standards, provide visibility, and intervene when things go wrong — but they empower project teams to operate with autonomy within that framework. The goal is better delivery across the organisation, not a bigger empire for the PMO.
Mistake Five: Ignoring the Cultural Dimension
Project management is a discipline that requires behavioural change. People have to update status reports they didn't have to write before. They have to attend governance meetings that didn't used to exist. They have to raise issues in a structured way rather than just dealing with things informally.
If this change isn't managed with care, resistance builds quickly. The PMO becomes seen as an overhead rather than a help. Smart PMO leaders invest as much energy in the people side — communication, relationship-building, early wins, recognising adoption — as they do in the technical side.
Mistake Six: No Clear Definition of Success
Remarkably few PMOs are set up with a clear, measurable definition of what success looks like at the six and twelve month mark. Without this, there's no way to demonstrate value — and when budgets get reviewed, the PMO becomes an easy target.
Before you launch, agree on three to five metrics you'll track. These might include on-time delivery rates, reduction in project escalations, stakeholder satisfaction scores, or reduction in budget variance. Measure them from day one, and report them visibly.
Building a PMO That Survives
The PMOs that make it through year one share a common set of characteristics. They started small and simple. They secured genuine executive commitment. They focused on outcomes before process. They built trust with delivery teams rather than imposing on them. And they measured and communicated their value consistently.
None of this is complicated. But all of it requires discipline — particularly in the face of pressure to do more, faster, with more structure, from day one.
If you're planning a PMO setup or reviewing why a previous attempt didn't stick, we'd welcome the conversation. Our PMO Setup & Design service is specifically built for SMEs who want to get this right without the enterprise overhead. Book a free discovery call and let's talk through your situation.