Not all PMOs work the same way. In fact, one of the most common reasons a PMO fails is that it operates at the wrong level of authority for its organisation — either too hands-off to make a difference, or too controlling to be trusted by the people it’s supposed to support.
The most widely used framework for thinking about this comes from the Project Management Institute, which describes three distinct PMO types. Understanding where your PMO sits — and where it should sit — is one of the first decisions you need to make.
The three PMO types
Supportive — low authority, high service
A Supportive PMO acts as a resource centre. It provides templates, tools, training, and guidance — but it has no authority to enforce standards or intervene in how projects are run. Project managers can take what they need and leave what they don’t.
This model works well in organisations with a strong project management culture already in place, where PMs are experienced and consistent standards exist naturally. It also suits decentralised organisations where business units have significant autonomy and would resist central control.
The risk is that without any enforcement mechanism, a Supportive PMO can become invisible. If nobody is required to use the templates or follow the standards, uptake is patchy and the PMO struggles to demonstrate value.
Controlling — medium authority, standards with teeth
A Controlling PMO still provides support and tools, but it also requires compliance. Projects must use approved methodologies, follow defined reporting formats, and pass through governance checkpoints. The PMO has the authority to flag non-compliance and escalate to leadership.
This is the most common model in mid-size to large organisations. It balances central oversight with operational flexibility — project managers still have autonomy over day-to-day delivery, but within a framework that gives leadership visibility and confidence.
Done well, a Controlling PMO is seen as a quality standard rather than a policing function. Done badly, it creates bureaucracy without value and breeds resentment from delivery teams who feel monitored rather than supported.
Directive — high authority, centralised delivery
A Directive PMO goes furthest. Project managers are employed by and report directly to the PMO, which takes full ownership of project delivery across the organisation. Standards aren’t just required — they’re non-negotiable, and the PMO has direct control over resource allocation and project execution.
This model suits organisations where project delivery is the core business activity — large infrastructure programmes, consulting firms, or organisations that have experienced repeated delivery failures and need to reset entirely. It gives maximum consistency and control, but requires significant investment and strong executive sponsorship to sustain.
The trade-off is flexibility. A Directive PMO can be slow to adapt to unusual project types and can create a single point of failure if the PMO leadership is weak.
Which type is right for your organisation?
There’s no universally correct answer — it depends on four things:
- Organisational maturity — how consistently are projects currently being run? Low maturity usually needs more control, not less
- Culture — will project managers and business units accept central oversight, or will they push back? Starting with a Supportive model and earning trust before moving to Controlling is often smarter than imposing authority from day one
- Executive sponsorship — a Directive PMO without strong backing from the top will collapse quickly. Be honest about how much political capital you have
- Scale — a small organisation running five projects probably doesn’t need a Directive PMO. A large programme of complex interdependent projects probably can’t survive without one
PMOs evolve — and that’s by design
Most successful PMOs don’t start at their final model. A common pattern is to begin as Supportive — build credibility by providing genuinely useful tools and support, earn trust from delivery teams, demonstrate value to leadership — and then gradually move towards Controlling as maturity increases and the case for standards becomes self-evident.
Trying to start as Directive in an organisation that isn’t ready for it is one of the fastest ways to kill a PMO. People will route around you, leadership will lose patience, and you’ll spend your time fighting for relevance rather than improving delivery.
Start where the organisation can accept, demonstrate value quickly, and expand your authority as trust grows.
Key takeaways
- Supportive PMOs provide tools and guidance but can’t enforce standards
- Controlling PMOs require compliance and have authority to escalate — the most common model
- Directive PMOs own delivery outright — highest control, highest investment required
- Match the model to your organisation’s maturity and culture, not your personal preference
- Most PMOs evolve from Supportive toward Controlling as trust and credibility are established