PMO (Project Management Office)
A PMO — project management office — is the function that holds delivery standards for an organisation. It owns the portfolio register, the reporting cadence, the templates and the stage gates. Mandates differ: some PMOs support delivery teams with tooling and assurance, some control them through gates and approvals, and some run the projects directly.
What it contains
A PMO is a function rather than an artefact, but it is recognisable by what it maintains. In most organisations that is a portfolio register of every project with an owner, a stage and a budget; a reporting cycle with fixed dates; a set of templates everybody is expected to use; a stage-gate or approval process; and some form of resource view showing who is committed where.
Beyond that the scope varies. A PMO may hold the benefits register, the change control process, the lessons learned library, the standard rate card for contractors, or the assurance reviews that run before a gate. Small PMOs typically hold the register and the reporting cycle and little else. Larger ones accumulate responsibilities until somebody trims them back.
How it is used
The PMO is the reason a director can ask "how many projects are amber and why" and get an answer in one place. It collects status from delivery teams on a fixed rhythm, normalises it into a single format, and presents it to whichever board owns the portfolio. That aggregation is the core service. A portfolio dashboard is the usual mechanism: one register per project, one roll-up view across all of them.
The second use is standardisation. When every project reports RAG differently, comparison is impossible, so the PMO fixes the definitions and the format. The third is gate assurance: before a project moves from design to build, or from build to go-live, the PMO checks that the required evidence exists. It does not usually make the decision. It records what was decided and by whom.
Which templates a PMO needs first depends on its mandate. The starting set for a small PMO is smaller than most people expect — a register, a status format, a RAID log and a decision log will cover the first six months.
Where it goes wrong
The most common failure is a PMO that collects data nobody uses. Weekly reports are gathered, formatted, filed, and never referenced in a decision. Delivery teams notice this quickly and the quality of what they submit drops accordingly.
The second failure is a mandate mismatch. A PMO set up to support is asked to enforce, or a PMO with enforcement authority behaves like a helpdesk. Neither works. If the PMO can stop a project at a gate, that needs saying out loud; if it cannot, it should not pretend otherwise.
The third is template proliferation. Every incident produces a new mandatory field, every audit produces a new form, and within two years the reporting burden exceeds the value of the reporting. A PMO that never removes anything ends up as an overhead the organisation routes around.
A fourth, quieter failure: the PMO owns the portfolio register but not the decision about which projects run. It then spends its time reporting on a portfolio that nobody has prioritised. Prioritisation belongs with whoever funds the work, but the PMO usually has to supply the scoring. An intake and prioritisation view is the artefact that makes that conversation possible.
Related terms
Portfolio management is the discipline the PMO usually administers — deciding which projects run and in what order. Programme management co-ordinates related projects towards a shared outcome; a PMO may sit inside a programme or across the whole organisation. Governance is the wider structure of boards and decision rights that the PMO services with reporting; how those boards are arranged is covered in the guide to programme governance. Stage gate is the checkpoint at which a project needs approval to continue.
Questions
Is a PMO the same as a programme office?
Not necessarily. A programme office serves one programme and closes when it ends. A PMO is usually a standing function across the organisation, though the terms are used interchangeably in many places.
How many people does a PMO need?
There is no fixed answer. A single portfolio analyst can maintain a register and a reporting cycle for a modest portfolio; assurance, benefits tracking and resource management each add work.
What is the difference between a supporting and a controlling PMO?
A supporting PMO provides templates, tooling and reporting help without authority over delivery decisions. A controlling PMO can require compliance and hold a gate closed until conditions are met.
Does a PMO run projects itself?
Only in a delivery PMO model, where project managers report into the PMO. In supporting and controlling models the project managers report elsewhere and the PMO provides the framework.