Contents
The Project Management Office: Misunderstood and Often Underestimated
The Project Management Office — commonly known as the PMO — is one of those business functions that organisations either rely on heavily or regard with mild suspicion. For some leadership teams, a PMO is an indispensable part of how complex work gets done. For others, it is an overhead: a team of people who produce status reports and create governance processes that slow everything down.
Both views have a basis in reality. A poorly designed PMO does exactly that — it generates process without generating value. A well-designed PMO, on the other hand, is a significant business asset. It increases the probability that projects deliver what they promised, on time and within budget.
According to the Project Management Institute’s Pulse of the Profession report, organisations with mature project management practices — including effective PMO structures — waste significantly less on poorly performing projects than those without them. The gap is not marginal.
This article explains what a PMO actually does, the different models available, and how to assess whether your organisation would benefit from one.
What a PMO Actually Does
At its core, a PMO provides structure, standards, and oversight for the management of projects and programmes across an organisation. But that description covers a wide range of actual activities, depending on the type of PMO and the maturity of the organisation.
In practice, a PMO typically performs some combination of the following functions:
- Standards and methodology — defining how projects should be planned, reported, and managed across the organisation, so there is consistency rather than twelve different approaches in twelve different teams.
- Portfolio oversight — maintaining a clear view of all active projects, their status, risks, and interdependencies, and providing senior leadership with the information they need to make resource and prioritisation decisions.
- Resource management — tracking how project resources (people, budget, capacity) are allocated across the portfolio and identifying conflicts or constraints before they become crises.
- Risk and issue management — maintaining a structured approach to identifying, tracking, and escalating risks and issues that could affect project outcomes.
- Benefits tracking — ensuring that projects are set up to measure and realise the business benefits they were approved to deliver, not just to complete their technical scope.
- Reporting — producing regular, accurate, and useful status information for different audiences: detailed operational reports for project teams, concise executive summaries for leadership.
- Lessons learned — capturing what went well and what did not across completed projects, and making that knowledge available to future initiatives.
The Three Main PMO Models
Not all PMOs are the same. The right model depends on the size of the organisation, the maturity of its project management capability, and how much standardisation and control is appropriate.
The Supportive PMO
A supportive PMO provides guidance, templates, tools, and expertise to project teams, but does not mandate how projects are run. Teams can use the PMO’s resources or not, largely at their own discretion.
This model works well in organisations where project management capability is already reasonably strong and where a high degree of autonomy is part of the culture. It generates less resistance than more prescriptive models, but also delivers less consistency.
The Controlling PMO
A controlling PMO sets standards and requires compliance. Projects must follow defined methodologies, use approved tools, and report through a consistent framework. The PMO has the authority to review projects and flag those that are not meeting required standards.
This is the most common PMO model in medium to large organisations running multiple complex projects simultaneously. It delivers greater consistency and oversight, but requires genuine leadership support to be effective — without it, a controlling PMO can quickly become seen as a bureaucratic obstacle.
The Directive PMO
A directive PMO directly manages projects, assigning project managers from the PMO team rather than from business units. The PMO owns delivery.
This model is typical in organisations with a dedicated delivery function — for example, a consultancy or a company with a structured programme delivery division. It provides the highest degree of consistency and control, but also requires the most resource investment.
When a PMO Makes Sense — and When It Does Not
A PMO is not the right answer for every organisation. Before establishing one, it is worth asking a few honest questions.
Signs That a PMO Would Add Value
You are running multiple projects simultaneously and struggling with prioritisation. If your leadership team regularly debates which projects should take priority but lacks a structured way to make that decision, a PMO function can bring portfolio visibility that makes prioritisation more objective.
Projects frequently overrun or underdeliver. If this is a recurring pattern, it often signals inconsistent project management practice — different project managers doing things differently, with no shared standards or review mechanisms to catch problems early.
You are about to undertake a major transformation programme. Large-scale change — a system implementation, a merger integration, a significant organisational restructuring — significantly benefits from dedicated programme governance. This is one of the clearest cases for establishing at least a temporary PMO structure.
Your organisation has grown to the point where informal coordination no longer works. In smaller organisations, the founder or a small senior team can manage project portfolios informally. As organisations grow, this approach breaks down. A PMO introduces the structure needed to maintain visibility and control at scale.
When a PMO Is Probably Not the Answer
You are a small organisation running a small number of straightforward projects. The overhead of a formal PMO is unlikely to be justified. Strong project management discipline from individual project managers, supported by clear reporting to leadership, is usually sufficient.
You want a PMO to solve a cultural problem. If the real issue is that project teams do not communicate, leadership does not support projects properly, or accountability is generally poor, a PMO will not fix these things on its own. Structural solutions do not solve cultural problems.
You need a quick fix for a specific project that has gone wrong. A failing project needs targeted intervention, not a new organisational function. Address the specific project first, and then assess whether a PMO is the right long-term answer.
How to Set Up a PMO That Works
Many PMOs are established with good intentions and then quietly lose relevance within 12 to 18 months. The most common reasons: they focus too much on process and not enough on value, they generate reporting that no one reads, or they fail to secure genuine support from senior leadership.
A few principles that tend to make the difference:
Start With a Clear Mandate
Define specifically what the PMO is accountable for and what authority it has. Without a clear mandate, a PMO will either overreach — trying to control everything — or underperform, unwilling to challenge projects that are clearly in trouble.
Focus on the Highest-Value Activities First
A new PMO should resist the temptation to implement every process at once. Start with the activities that will deliver the most visible value: typically portfolio visibility (a clear view of all active projects and their status) and a consistent approach to risk and issue management.
Once those are working, add additional capabilities progressively.
Make Reporting Useful, Not Just Regular
One of the most common criticisms of PMOs is that they produce a lot of reports that take significant effort to compile but are rarely acted on. Reports should be designed around the decisions they need to support. If a report is not helping anyone make a better decision, it should be redesigned or discontinued.
Secure and Maintain Leadership Support
A PMO needs active support from senior leadership — not just initial approval. This means the PMO’s recommendations are taken seriously, escalations are genuinely addressed, and the function is given the authority it needs to do its job. Without this, the PMO becomes a reporting function with no influence.
The Difference Between a PMO and a Programme Manager
A question that arises frequently: do you need a PMO, or do you just need a good programme manager?
The answer depends on scope. A programme manager leads a specific initiative — they are responsible for delivering a defined set of outcomes within a defined timeframe. A PMO operates at a higher level, providing the infrastructure and oversight across multiple projects or programmes simultaneously.
For organisations running a single major transformation, a strong programme manager with clear governance support from leadership may be sufficient. For organisations managing a portfolio of ongoing initiatives, a PMO function — even a lean one — tends to be more appropriate.
Conclusion
A PMO is not a silver bullet. It will not automatically make projects succeed or eliminate the challenges that come with complex change. But when it is designed thoughtfully, given a clear mandate, and supported by leadership, it significantly improves an organisation’s ability to deliver on its commitments — consistently and with better use of resources.
The question is not whether a PMO is a good idea in theory. The question is whether it is the right fit for your organisation right now, and whether you are prepared to invest in making it work properly.
If you are considering establishing a PMO or reviewing how your current project governance structure is working, feel free to get in touch via the Contact page. I would be happy to discuss your situation.
Frequently Asked Questions
What does PMO stand for?
PMO stands for Project Management Office. It is an organisational function responsible for defining and maintaining standards for project management within an organisation, and in many cases for overseeing a portfolio of active projects.
How large does a PMO need to be?
There is no fixed answer. Some PMOs consist of a single person who maintains portfolio oversight and standards. Others are large teams managing dozens of programmes simultaneously. The right size depends on the volume and complexity of the organisation’s project portfolio.
What is the difference between a PMO and a project manager?
A project manager is responsible for delivering a specific project. A PMO operates at the portfolio level — providing governance, standards, and oversight across multiple projects. A project manager works within the structure the PMO defines; the PMO ensures that structure exists and is being followed.
Can a small business benefit from a PMO?
Small businesses rarely need a formal PMO function. However, the principles behind good project management — clear accountability, consistent reporting, structured risk management — are valuable regardless of organisation size. A small business can apply these principles without a dedicated PMO team.
What is a virtual PMO?
A virtual PMO is a PMO function that does not have a permanent full-time team but instead draws on resources from across the business or from external providers as needed. This is an increasingly common model for organisations that need PMO capability but cannot justify the cost of a permanent team.
