Ray Moller
Technical Director – Portfolio and Program Management
Right-sizing your PMO: why fit matters more than headcount
When organisations look to improve project, program or portfolio delivery, the first question is often: “What kind of Project Management Office (PMO) do we need?”
It is a useful question, but not the best place to start. A PMO only creates value when it fits the way an organisation actually makes decisions, manages commercial performance and escalates risk. Without that fit, even a well-resourced PMO can become a reporting layer that improves visibility but does not improve control.
Ray Moller
Right-sizing a PMO is not about adding more people, templates or dashboards. It is about aligning the PMO’s mandate, authority and operating rhythm to the governance model of the organisation. In practice, that means understanding who makes decisions, what information leaders need, how quickly issues need to be escalated, and what commercial outcomes the PMO is expected to protect.
For organisations operating under profit and loss (P&L) pressure, this becomes even more important. Monthly margins, work in progress (WIP), billing cadence, debtor position, cashflow and delivery performance are not separate from project governance. They are part of it. A PMO that is properly designed can help connect delivery activity to commercial performance, giving leaders the information and escalation pathways they need to act before small issues become material problems.
Start with decision rights, not headcount
A common mistake is to start PMO design by asking how many people are needed. A better starting point is to ask how the organisation is governed.
Who has the authority to approve changes to scope, cost and schedule? Which decisions sit with executives, and which sit with functional leads or project teams? What does leadership need to see each month to understand performance? What happens when a project moves outside agreed tolerance levels?
These questions matter because PMO models succeed or fail based on decision rights. A highly directive PMO can work well in an organisation where authority is clear and delegated. In a matrixed business where delivery levers sit across multiple functions, that same model may struggle. The PMO may see the risk, but not have the authority to act on it.
When decision rights are unclear, a PMO can easily become a passive reporting function. It collects information, produces dashboards and highlights issues, but is unable to drive resolution. When decision rights are clear, reporting becomes a mechanism for action.
Why commercial rhythm matters
Project governance is often discussed through the lens of schedule, scope and risk. Those remain critical, but in commercial environments the PMO must also understand the rhythm of business performance.
End-of-month reporting, WIP calculations, billing cycles, debtor management and margin performance can all affect the health of a portfolio. If these inputs are disconnected from project reporting, leaders may only see issues after commercial performance has already been affected.
A right-sized PMO helps create a single view of delivery and commercial performance. It does not replace finance, commercial or delivery teams, but it helps connect the information they rely on. That allows leaders to see where project performance is creating margin pressure, where decisions are delayed, and where intervention is needed.
The goal is not more reporting. It is better control.
Three PMO models, and when they fit
Most PMOs can be understood through three broad models: directive, controlling and supportive. None is inherently better than the others. The right choice depends on how the organisation is structured, how decisions are made, and what outcomes the PMO is expected to influence.
Directive PMO
A directive PMO is appropriate where executive decision rights are clear and can be delegated. It has authority to enforce standards, approve changes, gate payments and drive delivery outcomes.
This model can work well in environments where strong central control is needed and the PMO has a clear mandate to intervene. It is suited to organisations that need consistent delivery discipline across a portfolio and are prepared to give the PMO the authority required to act.
A directive PMO can be powerful, but only when the governance model supports it. If authority remains dispersed across functions, the PMO may be expected to control outcomes without having the decision rights to do so. That creates frustration and weakens accountability.
Controlling PMO
A controlling PMO is best suited to organisations where authority is shared, but consistent standards and reporting are still required. It does not necessarily approve every decision, but it enforces process, maintains data discipline and triggers escalation when agreed thresholds are breached.
This model is useful when leaders need transparency across a portfolio and confidence that issues are being identified early. It works well where escalation pathways are clear and decision-makers are willing to act when the PMO raises a breach or exception.
The controlling PMO often provides the balance many organisations need: enough structure to maintain discipline, without assuming authority that sits elsewhere in the operating model.
Supportive PMO
A supportive PMO provides templates, tools, coaching and reporting support. It is most effective in matrixed organisations where delivery outcomes are owned by functions, project teams or discipline leads.
In this model, the PMO enables better delivery rather than directing it. It helps teams adopt consistent methods, improve reporting quality and access the right information. It can also support capability uplift by building project management maturity across the organisation.
A supportive PMO is not a weaker model. It is simply designed for a different environment. Where authority is intentionally decentralised, a supportive PMO can create value by improving consistency and capability without forcing a centralised control model onto a business that is not designed to use it.
Fit matters more than size
A PMO that is too small may not have the capacity to provide meaningful assurance, reporting or escalation. A PMO that is too large can drift into operational activity and lose sight of its governance role.
Right-sizing is about matching the PMO’s footprint to the organisation’s governance model, commercial rhythm and portfolio complexity. More people do not automatically create better control. In some cases, a lean PMO with clear decision rights, reliable data and strong escalation pathways will outperform a larger PMO with an unclear mandate.
The first step is to understand where governance is working and where it is not. This can often be done through a short governance scan, looking at decision rights, reporting cycles, data quality, escalation triggers and the way leaders use information.
From there, the organisation can decide what kind of PMO is required and what capability is needed to support it.
Stabilise the data backbone
A PMO cannot create control if the data it relies on is inconsistent, late or contested.
For many organisations, the fastest improvement comes from stabilising the data backbone. This means agreeing which systems are authoritative, what data definitions are used, who owns each dataset, and how information flows into executive reporting.
A single source of truth does not mean every team uses the same tool for every task. It means leaders can rely on one validated view of portfolio performance when making decisions.
For commercial organisations, this should include the connection between project delivery information and financial performance indicators such as WIP, revenue, margin and cashflow. Without that connection, the PMO may identify delivery issues but miss the commercial consequences until later.
Define the mandate before adding resources
Adding people to a PMO before defining its mandate can create confusion. Teams may assume the PMO is responsible for outcomes it does not have authority to control. Executives may expect intervention, while delivery teams view the PMO as an administrative burden.
A clear mandate should answer:
· What decisions can the PMO make?
· What decisions can it recommend?
· What does it monitor and report?
· What triggers escalation?
· Who acts when a tolerance is breached?
A tolerance breach occurs when a project moves outside agreed limits for cost, time, scope, quality or risk. These limits only matter if they are linked to a clear escalation pathway. Otherwise, they become another reporting item rather than a trigger for action.
Once the mandate is clear, resourcing decisions become more meaningful. The organisation can determine whether it needs a directive, controlling or supportive PMO, and what team size, skills and systems are required to make that model work.
Metrics that protect outcomes
A right-sized PMO focuses on the metrics that support action. For many organisations, three areas are particularly important.
The first is timely financial visibility. Leaders need validated performance information quickly enough to intervene. That may include cost, revenue, WIP, margin and cashflow indicators soon after month-end close.
The second is decision speed. Measuring the time between a tolerance breach and a leadership decision can reveal whether escalation pathways are working. If issues are identified but decisions lag, the problem is not reporting. It is governance.
The third is margin protection. Where delivery issues create commercial pressure, the PMO should help leaders understand the relationship between project performance and financial outcomes. That does not make the PMO a finance function, but it does make it part of the control environment.
Good metrics should make action easier. If a measure does not help leaders decide, escalate or intervene, it may not belong in the executive reporting pack.
What good looks like
A well-fitted PMO gives leaders confidence. It provides a clear view of portfolio performance, highlights issues early and links reporting to action.
In practice, that means:
· decision rights are documented and followed
· reporting is based on validated data
· escalation triggers are clear and used
· the PMO model matches the organisation’s operating model
· commercial and delivery performance are viewed together
· the PMO supports action, not just visibility
When those elements are in place, a PMO becomes more than a reporting function. It becomes a mechanism for predictable delivery outcomes.
The question is not simply whether an organisation needs a directive, controlling or supportive PMO. The better question is which model fits the way the organisation actually governs, measures performance and makes decisions.
Right-sizing a PMO starts with governance. It requires clarity on decision rights, reliable data, meaningful escalation pathways and a mandate that matches the organisation’s operating reality.
A PMO does not need to be large to be effective. It needs to fit.
Need to right-size your PMO?
RPS helps organisations assess PMO effectiveness, clarify decision rights and align governance, reporting and escalation pathways to the way work is actually delivered.
If your organisation has visibility of project issues but struggles to turn that visibility into action, a short governance scan can help identify where the PMO model is supporting outcomes, and where it may need to change.
To discuss how RPS can support your PMO design, governance or portfolio delivery, connect with Ray Moller and the RPS team.
Get in touch with Ray
