PMOs have a survival problem. They get founded with energy and a clear mandate, then settle into a routine of producing status reports, maintaining templates, and chasing project managers for updates. Two budget cycles in, leadership starts asking what the PMO is actually for. The conversation that follows determines whether the PMO becomes a permanent capability or a casualty of the next reorganisation.
Three PMO Archetypes
PMOs broadly fall into three archetypes. The Supportive PMO provides templates, training, lessons learned, and coaching — a service organisation for project managers. The Controlling PMO enforces methodology, governance, and reporting standards — a compliance function. The Directive PMO directly manages projects through PMs who report into the PMO — a delivery organisation. Each model is appropriate in different contexts. The mismatch between the chosen model and the organisational need is the leading cause of PMO failure.
Choose the Model the Organisation Actually Needs
A high-maturity organisation with experienced PMs and a culture of delivery discipline often needs a Supportive PMO — heavyweight controls would slow them down. A low-maturity organisation with inconsistent practices typically benefits from Controlling and gradually moves toward Supportive as maturity grows. A directive PMO is right when project delivery is genuinely centralised and the PMO owns the resourcing pool. Picking the wrong model means either underweight intervention (in a high-need environment) or overhead without value (in a high-maturity environment).
What a PMO Should Actually Be Measured On
- Project success rate — on-time, on-budget, scope-delivered, by definition agreed before the project
- Cycle time from approval to value delivered — across the portfolio, trended
- Resource utilisation and predictability — not just utilisation rate, but variance between forecast and actual
- Quality of project intake — projects approved should match strategic priorities, with clear value cases
- Decision quality — decisions made with the right information at the right time, evidenced
- Capability development — measurable improvement in project management skill across the organisation
A useful sanity check: if your PMO disappeared tomorrow, what specifically would degrade? If the answer is "the weekly status report would not be produced," the PMO is producing artefacts rather than outcomes. If the answer is "intake decisions would degrade, resource conflicts would not be detected, quality would suffer," the PMO is doing structural work. Build the PMO so the answer is the second one.
Common Failure Modes
Status reporting that nobody reads. Methodology that nobody follows. Tools that nobody updates. Stage gates that get waived under pressure. Lessons learned that get filed but never inform the next project. These are the symptoms. The underlying cause is almost always a PMO operating without clear authority — producing artefacts because that is what it can do, rather than influencing decisions because the organisation listens.
How to Earn Authority
PMOs earn authority by demonstrably improving outcomes that leadership cares about. Pick three measurable outcomes — project success rate, decision speed, resource conflict resolution — and show steady improvement. Stop producing artefacts that nobody references. Spend the time saved on coaching, intake quality, and stage gate substance. Within two cycles of credible improvement, the PMO has the authority to shape methodology, governance, and resourcing decisions that matter.
Tooling Comes Last
Most failing PMOs invest in tooling early — a portfolio management platform, a status dashboard, a lessons-learned repository. The tools are easy to buy and feel like progress. They are not. A good PMO with bad tools delivers value. A bad PMO with good tools produces dashboards. Solve the operating model first; the tooling is then a multiplier on a system that already works rather than a substitute for one that does not.