What is a PMO? A Guide to the Project Management Office

A PMO, or Project Management Office, is the team or department that sets and maintains an organisation's project management standards. It defines how projects are run, keeps them consistent, and gives leadership a clear view of what is happening across the work. Where a project manager runs one project, the PMO looks across many, making sure they follow common processes and stay aligned with what the business is trying to achieve.

Below, we cover what the acronym stands for, what a PMO actually does, the different types, how it differs from a project manager, whether your organisation needs one, and how the role is changing as PMOs move from administrative support toward strategy.

What does PMO stand for?

PMO stands for Project Management Office, a team or department that supports and governs project delivery across an organisation.

Two variations are worth knowing, because you will see them used:

• The P can also stand for Programme or Portfolio. A programme management office supports a related group of projects working toward a shared outcome; a portfolio management office looks across all of an organisation's projects and programmes with a focus on strategic and financial priorities. Which one you have depends on what is being supported. In UK practice, the Association for Project Management treats project, programme, and portfolio offices as variants of the same idea.
• PMO is occasionally used to mean Project Management Officer, a single person rather than a department. This is the sense people mean when they talk about a PMO analyst or PMO manager as a job title.

There is also the EPMO, or Enterprise Project Management Office, which is the organisation-wide version. More on that below, because it matters for how modern PMOs connect to strategy.

What does a PMO do?

A PMO's remit varies by organisation, but most cover some combination of the following.

Governance and oversight.

The PMO sets the rules for how projects are approved, run, and reported on, and checks that projects follow them. This is the backbone of what a PMO does: consistent governance so that leadership can trust the picture it is being shown.

Process and methodology standardisation.

Rather than each team inventing its own way of working, the PMO defines shared methods, templates, and stage gates. This is what lets an organisation compare projects on a like-for-like basis and reuse what works.

Resource management.

The PMO helps allocate people across projects, spot where the same specialists are overcommitted, and balance demand against capacity. In organisations running many projects at once, this is often where the PMO earns its keep. For a closer look at how this works in practice, see our guide to critical resource and timesheet management for the PMO.

Reporting and portfolio visibility.

The PMO consolidates the status of projects into a view leadership can act on: what is on track, what is at risk, where the money and effort are going. This rolls individual project detail up into a portfolio-level picture.

Methodology support and delivery help.

Many PMOs actively support project managers with tools, training, and administrative help, rather than only setting rules. How hands-on this is depends on the type of PMO, which is the next section.

Benefits tracking. Increasingly, PMOs track whether projects actually delivered the value they promised, not just whether they finished on time. This closes the loop between delivery and the business case. Getting this right depends on tracking the right indicators — see our breakdown of KPIs every strategic PMO should track.

The types of PMO

There are two useful ways to categorise PMOs, and a thorough understanding uses both.

The first is by how much control the PMO exerts, a model widely used across the profession:

• A supportive (or enabling) PMO acts as a resource. It provides templates, training, and guidance, but leaves control with the project managers. Best where projects are already reasonably well run and the goal is to share good practice.
• A controlling PMO sets standards and requires projects to comply with them. It offers support but also checks conformance. Best where an organisation needs more consistency than it currently has.
• A directive PMO goes furthest: it provides the project managers and runs the projects directly. Best where central control and consistency matter more than local autonomy.

The second way is by what the office supports, which is the framing UK practitioners will recognise from the Association for Project Management:

• A project management office supports individual projects.
• A programme management office supports a group of related projects delivering a shared outcome.
• A portfolio management office looks across the whole set of projects and programmes, with an eye on strategic priorities and where the organisation should invest.

Most real PMOs sit somewhere on both of these axes rather than fitting one label cleanly. The point is not to pick the right box but to be clear about how much authority the office has and what level of work it is there to support.

PMO vs project manager: what's the difference?

This is a common point of confusion, and the distinction is straightforward once stated.

A project manager is responsible for delivering a single project: its plan, its budget, its team, its day-to-day decisions. They go deep on one thing.

A PMO operates above the individual project. It sets the standards project managers work to, looks across multiple projects at once, allocates resources between them, and reports on the whole to leadership. It works for breadth: consistency and visibility across many projects at once.

The two are complementary, not competing. Project managers run the projects; the PMO makes sure those projects are run consistently, resourced sensibly, and visible to the people who need to steer the portfolio. In a directive PMO the line blurs, because the PMO supplies the project managers, but even then the two roles are doing different jobs. The distinction gets more nuanced again once programmes enter the picture — see our guide on programme vs project management.

Does your organisation need a PMO?

A PMO is not free, and a badly scoped one can add bureaucracy without adding value. It is worth being honest about when the function actually helps. The usual signals:

• Projects regularly drift from the organisation's strategic priorities, or no one can say with confidence how the current set of projects maps to what the business is trying to achieve.
• Teams work in silos, each with its own way of running projects, making it hard to compare them or move people between them.
• Resources are stretched and there is no clear view of who is committed to what, so the same people are overbooked while work stalls elsewhere.
• Delivery is inconsistent: some projects succeed, others fail, and the organisation cannot explain the difference or learn from it.
• Leadership lacks a reliable, current view of project and portfolio health and is making decisions on stale or partial information.

If several of these are true, a PMO is worth considering. If projects are few and running well, the overhead may not be justified yet.

The wider context supports the case. PMI's Pulse of the Profession 2026 reports that 97% of professionals managed at least one complex project in the past year, and that roughly a third of complex projects fail, nearly twice the 13% failure rate for projects overall. In that environment, the consistency and visibility a PMO provides is a way of managing risk that would otherwise sit unmanaged. (These figures are from PMI's published Pulse of the Profession 2026 summary; worth citing directly from the source if you use them.)

How the PMO role is changing: from process to strategy

For a long time the PMO was understood mainly as an administrative function: the office that kept the templates, chased the status reports, and enforced the process. That version still exists, but it is not where the value is any more, and it is not where the profession is heading.

The shift is toward the PMO as a strategy-execution function. A modern PMO asks a bigger question than whether projects are following the process. It asks whether the organisation is investing in the right projects at all, and whether they are moving it toward its strategic goals. That means prioritising the portfolio against strategy, reallocating resources as priorities change, and giving leadership a live view of whether the organisation's initiatives are actually delivering the intended outcomes. PMI has framed this directly in its work on positioning PMOs as partners in strategy execution, and the Enterprise PMO, with its organisation-wide remit, sits closest to this strategic role. We cover this connection in more detail in connecting strategic goals and OKRs to execution.

This shift changes what a PMO needs from its tools. An administrative PMO can run on spreadsheets and status decks. A strategic PMO cannot, because the job depends on seeing across the whole portfolio in something close to real time: which projects are consuming which resources, how delivery maps to strategic priorities, where the risks are concentrating across programmes, and whether the portfolio still reflects where the business wants to go. That picture cannot be assembled by hand from scattered project files fast enough to be useful for a decision.

A project portfolio management platform becomes the enabler here rather than a nice-to-have. Altus gives a PMO a single, current view across every project and programme, so the office can manage resources across the whole estate, connect delivery to strategic priorities, and give leadership a portfolio-level read on where things stand. For PMOs running on the Microsoft stack, it does this inside the organisation's own Microsoft 365 environment, which matters when the portfolio data in question is sensitive. The point is not the tool for its own sake; the strategic PMO the profession is moving toward needs portfolio visibility that manual methods cannot provide. This is also the point at which many PMOs are reassessing their tooling anyway, as Microsoft retires Project Online — see our guide to migrating off Project Online.

[Optional: one real line here from an Altus customer or PMO lead about making the process-to-strategy shift in practice would lift this above PMI's own framing. Leave out if you don't have a genuine one.]

How to set up a PMO

Standing up a PMO is a project in itself, and the detail is beyond the scope of this guide, but the shape of it is:

1. Assess the need. Be specific about the problems the PMO is meant to solve, so its remit is grounded in real gaps rather than a general sense that there should be an office. Assessing your organisation's current project management maturity is a useful starting point — see our notes on project management maturity levels.
2. Choose the type and structure. Decide how much authority it will have (supportive, controlling, directive) and what it supports (project, programme, portfolio), based on the assessment.
3. Define processes and governance. Set the standards, templates, stage gates, and reporting the PMO will own, keeping them proportionate to the organisation's maturity.
4. Choose the tooling. Pick the platform that will give the PMO its portfolio visibility, matched to how the organisation actually works. Our guide to building a modern project management tech stack covers what to look for.
5. Pilot, then scale. Prove the model on a subset of projects, learn from it, and expand rather than imposing a finished machine on day one.

Frequently asked questions

What does PMO stand for?Project Management Office: the team or department that sets and maintains project management standards across an organisation. The P can also stand for Programme or Portfolio depending on what is supported, and PMO is sometimes used for Project Management Officer, an individual role.

What is the difference between a PMO and a project manager?A project manager delivers a single project day to day. A PMO works above the individual project, setting the standards project managers follow, looking across many projects at once, and giving leadership visibility of the whole. They complement each other.

What are the three types of PMO?By level of control: supportive (provides guidance, leaves control with project managers), controlling (sets standards and checks compliance), and directive (runs the projects directly). PMOs are also categorised by what they support: project, programme, or portfolio.

What is an EPMO?An Enterprise Project Management Office is the organisation-wide version of a PMO, with responsibility for aligning projects, programmes, and portfolios to corporate strategy. It sits closest to the strategic, portfolio-level role that modern PMOs are moving toward.

Does a small organisation need a PMO?Not necessarily. If projects are few and running well, the overhead may not be justified. A PMO earns its place when projects are numerous, inconsistent, drifting from strategy, or competing for the same stretched resources.

‍