Is your PMO helping delivery — or just reporting on it?
A PMO should give leadership better control of delivery — not simply better reports about it.
IN THIS INSIGHT…
A PMO can produce impressive dashboards, regular reports and well-organised project information. But does that necessarily mean it is improving delivery?
In this Insight, you'll discover:
Why reporting and delivery oversight are not the same thing
How a PMO can become busy without necessarily adding value
What useful PMO activity should help leadership understand and act on
Why good governance should make projects easier to manage, not harder
How to tell whether your PMO is supporting decisions or simply documenting them
Why the right level of PMO support depends on what your organisation actually needs
A PMO CAN LOOK BUSY WITHOUT MAKING PROJECTS BETTER
There is something reassuring about a well-organised PMO.
There are dashboards, project reports, traffic-light ratings, governance meetings, templates, trackers, action logs and reporting cycles.
Everything appears to be under control.
But there is an important question that can sometimes get lost underneath all that activity: Is the PMO helping projects move forward, or is it mainly reporting on what has already happened?
The distinction matters. Reporting has an important role. Leadership teams, trustees and funders often need reliable information about progress, risks, spending, milestones and outcomes.
But reporting is not the same as delivery oversight. A report can tell you that a project is behind schedule. A useful PMO should help the organisation understand why, what the consequences are, what decisions are needed and what can realistically be done about it. That is a very different contribution.
REPORTING TELLS YOU WHAT IS HAPPENING. OVERSIGHT HELPS YOU DECIDE WHAT TO DO.
A project dashboard might show that three projects are rated amber. That is useful information. But what happens next?
If the PMO simply updates the dashboard, circulates the report and waits for the next reporting cycle, the organisation has gained visibility without necessarily gaining control.
A stronger approach would ask:
Why are those projects amber?
Is the problem temporary or becoming structural?
Are the same risks appearing across several projects?
Are projects competing for the same people or resources?
Is leadership aware of a decision that is holding delivery back?
Has the original priority changed?
Does something need to be escalated?
Is the project still worth continuing in its current form?
This is where PMO capability can become genuinely valuable. The purpose of oversight is not to create another layer between leadership and project teams. It is to help leadership see what matters, understand what it means and make better decisions.
That might mean challenging a project plan. It might mean identifying a dependency between two projects. It might mean highlighting that a project has continued despite the conditions that originally justified it having changed. It might mean helping a Project Manager escalate an issue before it becomes a much larger problem.
None of those activities necessarily produces another report. But they may have considerably more impact on delivery.
WHEN REPORTING BECOMES THE WORK
One of the warning signs of an ineffective PMO is when the organisation becomes very good at describing projects but not necessarily at improving them.
The PMO spends significant time collecting updates.
Project Managers spend significant time preparing them.
Leadership receives increasingly detailed reports.
Meetings become focused on reviewing the information.
And then everyone moves on to the next reporting cycle.
This can create the appearance of control. But if the same risks appear month after month, the same decisions remain unresolved and projects continue to drift, the reporting process may be documenting the problem rather than helping solve it.
That does not mean the answer is to stop reporting. It means reporting needs to have a purpose.
A good question for any PMO is: What decision, action or improvement is this information intended to support?
If the answer is unclear, it may be worth reconsidering the process.
REFLECTION:
If your PMO stopped producing its regular reports for one month, what would leadership actually lose?
Would it lose critical insight — or mainly a familiar reporting routine?
GOOD GOVERNANCE SHOULD MAKE DELIVERY EASIER
Governance sometimes gets treated as something that sits above project delivery.
The project team delivers.
The PMO reports.
Leadership reviews.
But good governance should not be disconnected from what is actually happening on the ground.
If a governance process requires project teams to spend hours producing information that nobody uses, it is consuming delivery capacity rather than strengthening it.
If every project has to follow exactly the same process regardless of size, risk or complexity, the organisation may be applying more control than the situation requires.
And if project teams are unclear about what decisions need escalating, when they need to escalate them or who can make those decisions, a beautifully designed reporting framework will not solve the problem.
Effective governance should create clarity. It should help people understand:
Who needs to know?
What do they need to know?
When do they need to know it?
What decisions need to be made?
Who has the authority to make them?
What happens if a project cannot deliver what was originally agreed?
Those questions are much more important than whether the organisation has the perfect reporting template.
THE PMO SHOULD CONNECT INFORMATION TO ACTION
The most useful PMO information is rarely information for its own sake. It connects what is happening in projects to what leadership needs to understand and decide.
Imagine a charity delivering several significant initiatives at the same time.
One project is delayed because a supplier has not delivered.
Another is struggling because the same internal team is already at capacity.
A third is progressing, but its original benefits are becoming less relevant because organisational priorities have changed.
Individually, each project may appear manageable.
Viewed together, there may be a much bigger organisational issue.
That is where PMO oversight can add value. The PMO can identify patterns that individual Project Managers may not be able to see.
It can bring related risks together.
It can highlight competing demands for resources.
It can identify decisions that affect more than one project.
It can give leadership a clearer view of the overall delivery picture.
That is not simply reporting. It is helping the organisation manage its portfolio of change.
REFLECTION:
When your leadership team receives a project report, does the conversation usually move towards “What should we do?” or “What happened?”
What would change if every significant piece of reporting had to support a decision or action?
A PMO SHOULD NOT BECOME ANOTHER LAYER OF BUREAUCRACY
This is particularly important for charities and other purpose-driven organisations.
Resources are limited.
People often have multiple responsibilities.
Project teams may already be balancing delivery with operational work.
Adding processes simply because a PMO exists can quickly become counterproductive. A PMO does not demonstrate its value by the number of templates it creates, the number of meetings it attends or the amount of information it collects.
In fact, those measures can sometimes encourage the wrong behaviour.
A PMO that is measured primarily on whether reports are completed on time may become very good at reporting. A PMO that is expected to improve organisational visibility, strengthen decision-making and support delivery is likely to behave differently.
The question becomes less: “Have all the reports been completed?”, and more: “Do we understand what is happening across our projects, and are we acting on what we know?”
That does not mean reducing governance to the absolute minimum. Some projects genuinely require robust controls. Projects involving significant funding, regulatory requirements, organisational risk, major change or multiple stakeholders may need a stronger governance structure.
The point is proportionality. The level of governance should reflect the level of risk and complexity.
NOT EVERY PROJECT NEEDS THE SAME LEVEL OF OVERSIGHT
A small internal improvement project probably does not need the same governance structure as a major organisational transformation.
A short project with a familiar team may require very little central oversight.
A programme involving several departments, external partners, significant funding and major organisational change may need considerably more.
This is one reason why effective PMO capability should not be confused with a fixed set of processes. The right approach depends on the organisation and its projects.
Some organisations may need a permanent PMO because they have a sustained portfolio of complex change. Others may need additional PMO capability for a particular period of growth, transformation or organisational change.
Some may already have capable Project Managers but need stronger coordination and oversight across projects.
Others may need help establishing basic governance and reporting before deciding what ongoing capability is appropriate.
The question is not simply: “Do we have a PMO?”
It is: “What project oversight does our organisation actually need?”
REFLECTION:
If you designed your PMO today from scratch, knowing what you now know about your organisation's projects, would you create exactly the same processes?
Or have some of them simply become part of how things are done?
WHAT SHOULD A USEFUL PMO ACTUALLY CONTRIBUTE?
There is no single definition that works for every organisation, but a useful PMO should generally help leadership and project teams do things they would struggle to do as effectively without it.
That could include:
Better visibility
Giving leadership a reliable view of progress, risks, dependencies and priorities.
Better decisions
Bringing the right information together so decisions can be made at the right time.
Better coordination
Identifying connections and competing demands across projects.
Better governance
Creating proportionate structures that provide accountability without unnecessary administration.
Better risk management
Identifying emerging problems early enough for something to be done about them.
Better prioritisation
Helping leadership understand where limited organisational capacity is being used and whether priorities remain appropriate.
Better delivery confidence
Giving leadership confidence that important projects are being actively monitored and managed.
None of these outcomes depends on producing a particular number of reports. The reports are simply one means of achieving them.
THE REAL TEST IS WHAT HAPPENS BECAUSE THE PMO EXISTS
Perhaps the simplest way to assess a PMO is to look beyond its outputs.
Don't just ask what it produces. Instead, ask what is different because it exists.
are risks being identified earlier?
are decisions being made faster?
are competing priorities more visible?
are Project Managers receiving useful support?
are leadership teams better able to challenge projects when circumstances change?
are resources being allocated more deliberately?
are projects being stopped, reshaped or escalated when appropriate?
are important issues reaching the right people before they become crises?
are trustees and senior leaders receiving information that genuinely helps them exercise oversight?
If the answer to several of these questions is yes, the PMO is probably doing something valuable.
If the answer is mostly no, but the organisation is still producing more reports, holding more meetings and maintaining more trackers, it may be time to look at what the PMO is actually designed to achieve.
REFLECTION:
What is the strongest evidence that your PMO improves project delivery?
And if you had to demonstrate its value without showing a single dashboard or report, what would you point to?
THE PMO SHOULD SERVE DELIVERY — NOT THE OTHER WAY AROUND
There is nothing wrong with reporting. There is nothing wrong with governance. And there is certainly nothing wrong with having a PMO.
The problem comes when the structure becomes more important than the outcome it was created to support.
A PMO should exist to help an organisation deliver important work with greater visibility, control and confidence.
Sometimes that means better reporting.
Sometimes it means challenging a project.
Sometimes it means bringing a difficult issue to leadership.
Sometimes it means coordinating projects that are competing for the same resources.
Sometimes it means helping a Project Manager who is struggling with a particular delivery issue.
And sometimes it may mean telling leadership that a project should be paused, changed or stopped.
Those activities may not always make the PMO look busy. But they can make the organisation more effective.
START WITH THE CAPABILITY, NOT THE STRUCTURE
This is also why the question of whether a PMO should be permanent, internal or external should usually come later.
First ask what the organisation needs.
How many projects are being delivered?
How complex are they?
What risks are involved?
What internal capability already exists?
Where is leadership lacking visibility?
What governance is genuinely required?
What support do Project Managers need?
And how long is that level of oversight likely to be needed?
The answer might justify a permanent internal PMO. It might not.
An organisation may need additional PMO capability for a defined period rather than indefinitely. It may need specialist support during a transformation, additional capacity while several projects are running simultaneously, or independent oversight when leadership needs a clearer view of delivery.
The important thing is not the label. It is whether the organisation has the capability it needs, in a form proportionate to the work it is trying to deliver.
CONCLUSION - IS YOUR PMO HELPING DELIVERY, OR JUST REPORTING ON IT?
A PMO should do more than tell you what is happening. It should help you understand what it means, what needs attention and what should happen next.
Reporting is part of that. Governance is part of that. But neither should become the purpose of the PMO itself.
The real test is whether the PMO helps the organisation make better decisions, manage risks earlier, coordinate its projects more effectively and ultimately improve delivery.
If your PMO is generating plenty of information but leadership still struggles to understand where projects stand, what needs attention or where organisational capacity is being stretched, the issue may not be a lack of reporting.
It may be that the PMO needs to focus more clearly on delivery.
At RootRise, we provide practical External PMO Support that can be shaped around the level of oversight an organisation actually needs — from strengthening project governance and reporting to providing independent oversight and coordination across multiple projects.
You don't necessarily need more process. You need the right level of capability to help your projects move forward.
If you're wondering whether your current PMO is genuinely helping delivery, we'd be happy to have an initial conversation. There's no obligation — just an opportunity to understand what you're trying to deliver and whether your current approach is helping you get there.
