A project management office, or PMO, is the team or function that gives an organization a single, consistent way to select, run, and govern its projects. At its best, a PMO is the difference between a company that finishes the right work and one that stays permanently busy on the wrong work. At its worst, it is a reporting layer that produces status decks nobody reads.
The difference is not the org chart. It is whether the PMO owns decisions or just paperwork. This guide covers what a PMO genuinely does, the three common types, and a practical path to standing one up without the bureaucracy that gives the function a bad name. For the full operating structure these pieces sit inside, see the PMO framework.
Key takeaways
- A PMO standardizes how projects are chosen, run, and reported so leaders can compare them fairly.
- There are three common types: supportive, controlling, and directive. Pick the lightest one that solves your actual problem.
- Start with the one decision the organization keeps getting wrong, not with a 40-page methodology.
What a PMO actually does
Strip away the frameworks and a working PMO does a handful of concrete things. It defines how a project is proposed and approved, so the answer to "should we do this?" is not just whoever asked loudest. It sets a common way to estimate, plan, and track work, so two projects can be compared on the same terms. It runs the governance cadence where projects get reviewed, funded, paused, or killed. And it gives leadership a true picture of what is in flight, what it costs, and whether it is on track. Each of these is one of the office's core PMO functions, and they only create value when they run as one connected operating process rather than separate activities.
Notice what is not on that list: doing the project management for every team. A good PMO raises the floor on how projects are run across the organization. It does not try to personally run them all. Who actually carries out that work depends on how the office is staffed, which is the subject of PMO roles and responsibilities.
The three types of PMO
Most PMOs fall into one of three models, and the right one depends on how much authority the function needs to fix the problem you actually have.
Supportive PMO
A supportive PMO provides templates, training, lessons learned, and a shared toolset, often a common project portfolio management tool every team can adopt. It has a low degree of control: project teams can take or leave its help. This model fits organizations where projects are generally healthy and the gap is consistency, not discipline. It is the cheapest to stand up and the easiest to ignore.
Controlling PMO
A controlling PMO requires that projects follow defined standards: a particular planning approach, specific gates, mandated reporting. It has a moderate degree of control and works when leadership has decided that inconsistency is causing real harm and wants compliance, not just guidance. The risk is that it tips into box-ticking if the standards are not genuinely useful.
Directive PMO
A directive PMO supplies the project managers and runs the projects directly. It has the highest degree of control because the work happens inside it. This fits organizations with high project volume, regulatory exposure, or a track record of delivery failures that justifies centralizing the discipline.
The type sets how much authority the office holds, but a separate decision is how the office is arranged as a unit: one central team, embedded teams per division, or a central hub with local satellites. That organizational design, and where the office should report, is covered in PMO structure.
How to set up a PMO: a practical path
The fastest way to discredit a new PMO is to open with a thick methodology binder. Do the opposite. Start narrow and earn the right to expand. And once the scope is agreed, write it down in a short PMO charter, so the office's authority survives its first collision with a senior leader who wants an exception. For the full step-by-step version of this, including a phased 90-day plan and a setup checklist, see the dedicated guide on how to set up a PMO from scratch.
1. Name the one decision you keep getting wrong. Is it that everything is "priority one"? That projects start before they are funded? That nobody knows who is overcommitted? Your first job is to fix that single failure, not to standardize everything.
2. Build the intake and prioritization first. Most PMO value comes from choosing the right work. A simple, transparent way to score and rank incoming requests beats a perfect tracking system for projects that should never have started. We cover this in depth in how to prioritize a project portfolio.
3. Establish a light governance cadence. A recurring forum where projects are reviewed against criteria, with real decision rights, is what turns a PMO from a reporting function into a steering one. See project portfolio governance for the cadences and decision rights that work, and a project governance framework for the decision rights inside a single project.
4. Make capacity visible. You cannot say yes responsibly until you know who is already committed. A basic view of demand versus the people you actually have prevents the silent over-commitment that wrecks delivery. More in resource and capacity planning for project portfolios.
5. Report on outcomes, not activity. Executives do not need a list of tasks. They need to know whether the portfolio is delivering the results it was funded for. We cover what that looks like in PMO reporting that executives actually read.
Signs your PMO is working
You will know the function is earning its keep when leaders start asking the PMO before committing to new work, when at least some projects get paused or killed at reviews instead of limping on, and when teams stop being assigned to four "top priority" efforts at once. If none of that is happening after a couple of quarters, the PMO has become a reporting layer, and it is time to revisit which decisions it actually owns. A PMO maturity model gives you a structured way to assess where the office stands today and which capability to build next, and our PMO best practices checklist is the faster self-audit if you want to know today whether the office is improving any decision at all.
Frequently asked questions
What does a PMO do?
A PMO defines how projects are selected, governed, and reported across an organization. Day to day that means running intake and prioritization, setting delivery standards, keeping resource commitments visible, and giving executives one reliable picture of portfolio status and spend. The mix shifts with the PMO type: supportive offices advise, controlling offices enforce standards, and directive offices run the projects themselves.
What is a PMO in project management?
In project management, a PMO (project management office) is the central function that owns the standards, governance, and portfolio view that individual projects plug into. Project managers deliver one project at a time; the PMO makes the collection of projects behave like a managed portfolio, with shared criteria for what gets approved and a common way of reporting progress. The discipline it is running when it does that is project portfolio management, and a PMO can exist without practicing it.
What is the difference between a PMO and a project manager?
A project manager is accountable for delivering one project: its scope, schedule, budget, and team. A PMO is accountable for the system around all projects: which ones get approved, the standards they follow, and how the portfolio performs as a whole. Put simply, the project manager works in a project while the PMO works on the portfolio.
What are the three types of PMO?
The three standard types are supportive, controlling, and directive, ordered by how much control they exert. A supportive PMO provides templates, coaching, and lessons learned. A controlling PMO requires compliance with defined standards and gates. A directive PMO staffs and runs the projects itself. In practice most offices blend elements of two, and the right degree of control depends on how much inconsistency is actually costing the organization.
Is PMO higher than project manager?
Not inherently. A PMO analyst is usually junior to an experienced project manager, while a PMO director typically outranks one. The PMO is a function, not a rung on the career ladder, so seniority depends on the specific role. What the PMO does hold over project managers is decision authority on standards, gates, and portfolio priorities.
What is a PMO manager?
A PMO manager is the person who leads the project management office, owning the delivery standards, the intake and prioritization process, portfolio reporting, and the resource picture across every project. They do not usually deliver projects themselves. The role and a full job description are covered in our guide to the PMO manager.
What is the PMO process?
The PMO process is the repeatable cycle the office runs: intake of new requests, prioritization and approval, governance through stage gates, monitoring and reporting, and benefits realization after delivery. Each stage has an owner and an output, which is what stops the office becoming a reporting desk. The full cycle is set out in PMO functions and processes.