A PMO is not a shared drive with a logo. It is an office with a defined amount of authority over how projects are run — and the fastest way to make it hated is to claim more authority than the organisation will actually grant.
Supportive, controlling, and directive
A supportive PMO is a service. It offers templates, training, coaching, and a place to ask 'has anyone done this before?' Project managers keep the decision rights. Use it when the organisation is new to structured delivery, or when skilled PMs already exist and mainly need a common language. The failure mode is becoming a stationery cupboard: lots of artefacts, no behaviour change.
A controlling PMO sets standards and checks that they are used. It may require a charter, a risk register, a stage gate, or a reporting format — and it has enough teeth to send work back. Use it when leadership wants comparable data across projects and is willing to enforce the minimum. The failure mode is audit theatre: forms completed so the PMO goes away, while the real decisions happen in a side chat.
A directive PMO assigns the project managers and owns delivery method. The projects report into the office, not merely through it. Use it when the work is high-stakes, tightly coupled, or the organisation has learned the hard way that optional process is optional. The failure mode is a bottleneck dressed as governance: every decision queues behind one overworked head of PMO.
These are positions on a spectrum, not job titles. A PMO can be supportive for small internal change and controlling for regulated programmes. Write down where you sit for each class of work. If you cannot say who decides and who merely advises, you do not have a model. You have a meeting series.
Make the offer explicit
Write a one-page service catalogue: what the PMO does, what it does not do, who it serves, and what it needs in return. 'We will run the portfolio review and coach new PMs. We will not write your status report for you after week four.' Ambiguity is how every fire becomes the PMO's problem.
Name the customers. A PMO that tries to delight project managers, sponsors, finance, and audit equally will please none of them. Decide whose problem you are primarily hired to solve this year — usually leadership's visibility, or delivery quality — and design the model around that.
Revisit the model when the work changes. A supportive office that worked at twenty people will not hold a fifty-project portfolio. A directive office built for a transformation can become a drag once the transformation is business-as-usual. Models are decisions with a date, not identities.
Summary & next steps
Supportive advises, controlling standardises and checks, directive owns delivery. Pick the lightest model the pain requires, and only claim the authority leadership will actually back.
Next: governance frameworks — decision rights and gates that mean something, rather than a slide titled 'governance' with a circle in the middle.