When does PMO capability need to be permanent?
A PMO doesn't become valuable simply because an organisation has projects. The question is whether the need for oversight, coordination and governance has become permanent too.
IN THIS INSIGHT…
As organisations take on more projects, it can become tempting to assume that the answer is to create a permanent PMO. But permanence is a significant organisational commitment. It should be based on a sustained need for capability — not simply because projects have become more numerous.
In this Insight, you'll discover:
Why having more projects doesn't automatically mean you need a permanent PMO
The difference between a temporary need for PMO support and an ongoing organisational capability
When a permanent internal PMO can genuinely add value
Why the right PMO model can change as an organisation develops
What leadership teams should consider before making PMO capability permanent
DOES A PMO NEED TO BE PERMANENT?
It's a reasonable question. If an organisation is managing several important projects, improving governance, coordinating delivery and providing regular reports to trustees or funders, creating a permanent PMO can appear to be the natural next step.
Sometimes it is. But there is an important distinction between needing PMO capability and needing a permanent PMO function.
An organisation may need stronger project oversight for a major transformation, a period of rapid growth, a significant funding programme or a portfolio of time-limited initiatives. That need can be substantial. It can require experienced people, better reporting, clearer governance and more consistent coordination.
But if the underlying reason for that additional capability is temporary, creating a permanent structure may not necessarily be the most proportionate response.
The better question is not: "Do we have enough projects to justify a PMO?"
It is: "Has our need for PMO capability become an ongoing part of how this organisation needs to operate?"
That is a different question.
PROJECTS CAN BE TEMPORARY. ORGANISATIONAL COMPLEXITY MAY NOT BE
One of the reasons this decision can be difficult is that organisations often experience a period of increasing project activity without knowing whether it represents a permanent change.
A charity may receive significant new funding and suddenly have several projects running at once.
A growing organisation may introduce new systems, services or operating models.
A merger may create a substantial programme of change.
A leadership team may launch several strategic initiatives at the same time.
During these periods, the need for coordination and oversight can increase quickly. The organisation may need someone to bring consistency to reporting, monitor risks, coordinate dependencies, support governance meetings and give leadership a clearer picture of delivery.
That is a genuine PMO need. But it does not necessarily tell you whether the need will still exist in three years.
Some organisations go through a concentrated period of change and then return to a relatively stable operating environment. Others discover that the change was not a temporary phase at all.
The organisation has become more complex.
Projects have become a normal part of how strategy is delivered.
Different teams depend on one another more often.
Leadership needs regular portfolio-level information.
Trustees, funders or other stakeholders expect stronger evidence of delivery.
In that situation, PMO capability may have moved from being a temporary requirement to an ongoing organisational capability.
REFLECTION:
If your current need for PMO support disappeared tomorrow, would the organisation genuinely return to the way it operated before?
Or has the way you deliver strategy changed permanently?
MORE PROJECTS DOESN'T AUTOMATICALLY MEAN MORE PMO
It is tempting to use the number of projects as the trigger.
Five projects might seem manageable.
Ten projects might feel like the point where a PMO becomes necessary.
Twenty might appear to make a permanent PMO inevitable.
But project numbers alone tell you very little. Five highly interconnected projects can create more governance complexity than twenty relatively independent ones.
Similarly, an organisation might manage a significant portfolio effectively because it has experienced project managers, established governance and strong leadership involvement.
Another organisation might struggle with a much smaller number of projects because responsibilities are unclear and information is fragmented.
The issue is therefore not simply volume. It is the ongoing organisational requirement for coordination, visibility, governance and decision-making across projects.
This distinction matters because a permanent PMO should solve a permanent organisational problem.
If the organisation's challenge is a temporary increase in delivery activity, temporary or flexible PMO support may be more proportionate.
If the organisation has reached a point where project delivery has become a permanent feature of its operating model, the case for permanent capability becomes stronger.
WHEN PERMANENT PMO CAPABILITY STARTS TO MAKE SENSE
There is no universal threshold. However, a permanent PMO becomes increasingly reasonable when project oversight is no longer something the organisation only needs during occasional periods of change.
For example, an organisation may have reached this point when:
strategic priorities are consistently delivered through multiple projects or programmes
projects regularly compete for the same people, funding or organisational capacity
leadership needs an ongoing view across the portfolio rather than individual project updates
project governance has become a normal part of organisational decision-making
risks and dependencies regularly cross project or departmental boundaries
trustees, funders or senior leaders require consistent portfolio-level reporting
the organisation needs to maintain project standards, controls and processes continuously
lessons from one project need to inform how other projects are delivered
there is a continuing requirement to prioritise projects and allocate delivery capacity
project delivery has become part of the organisation's normal operating model rather than an occasional activity
Notice that these aren't arguments for creating bureaucracy. They are indicators that the organisation may have developed a lasting need for project delivery infrastructure.
A permanent PMO can provide continuity in that environment.
It can maintain standards.
It can provide consistent reporting.
It can help leadership understand the relationship between projects.
It can retain organisational knowledge between initiatives.
And it can provide a stable point of coordination as different projects begin, change and finish.
That can be valuable. But it still doesn't mean the PMO needs to be large.
PERMANENT DOESN'T HAVE TO MEAN LARGE
Another assumption worth challenging is that a permanent PMO needs to become a substantial department. It doesn't.
An organisation may have a continuing need for PMO capability without needing a large team. A small internal PMO might provide the core governance, reporting and coordination required, while specialist expertise is brought in when needed.
Another organisation might have a dedicated PMO leader supported by project managers who remain embedded within individual teams.
The structure should reflect the capability required. Permanent capability and permanent headcount are not necessarily the same thing. This is particularly relevant for charities and purpose-driven organisations, where resources need to remain closely connected to organisational purpose.
A permanent function should earn its place by adding continuing value. If the function exists primarily because "we've always had a PMO", that is worth questioning. If it exists because leadership genuinely relies on the capability it provides, the case is much stronger.
REFLECTION:
If you made your PMO permanent tomorrow, what ongoing organisational problem would it be responsible for solving?
And would that problem still exist if your current portfolio of projects changed completely?
THE RISK OF MAKING A TEMPORARY NEED PERMANENT
There is another side to this decision. Creating permanent PMO capability can provide stability, but it also creates an ongoing organisational commitment.
There is recruitment.
There is management capacity.
There are salaries and employment costs.
There is responsibility for maintaining the function when project activity changes.
And there is the possibility that a function created to solve a particular problem gradually becomes an organisation in its own right.
That doesn't make permanent PMOs a bad idea. It simply means the decision deserves the same level of thought as any other significant organisational investment.
A PMO should not exist simply because the organisation has reached an arbitrary number of projects. Nor should it exist because leadership feels uncomfortable with the level of uncertainty created by change.
The question should always return to capability.
What does the organisation need to be able to do consistently?
What level of oversight is required?
What decisions need better information?
What coordination needs to happen across projects?
And how long is that capability likely to be required?
THE NEED CAN BE PERMANENT WITHOUT THE MODEL BEING FIXED
There is an important distinction here. An organisation can have a permanent need for PMO capability without needing exactly the same PMO structure forever.
The organisation may grow.
Its portfolio may change.
Its funding model may change.
Its strategic priorities may change.
The number and type of projects may change.
The PMO may therefore need to change too.
A small organisation might initially need occasional external support to establish governance and reporting. As the portfolio grows, it might develop an internal PMO lead. Later, it might need a broader team. At another point, a major transformation may require additional external specialists alongside the internal function.
The capability remains important. The model evolves.
This is why the choice should not be framed simply as internal versus external. Both can have a place. A permanent internal PMO may provide continuity, organisational knowledge and embedded capability. External PMO support can provide additional capacity, independent oversight, specialist experience or temporary support during periods of change.
The right arrangement depends on what the organisation needs at that point in its development.
REFLECTION:
Is your organisation deciding what PMO structure it needs based on today's projects?
Or are you considering what project delivery capability the organisation will need to sustain its strategy over the longer term?
WHEN PMO BECOMES PART OF HOW THE ORGANISATION OPERATES
Perhaps the clearest indicator of a permanent need is when project management stops being something that happens alongside the organisation's normal work and becomes part of how the organisation delivers its strategy.
Projects are no longer occasional.
Change is continuous.
New initiatives are regularly introduced.
Existing projects create dependencies for future projects.
Resources need to be prioritised across competing demands.
Leadership needs to understand not only whether individual projects are progressing, but whether the overall portfolio is supporting organisational priorities.
At that point, PMO capability can become part of the organisation's infrastructure. It provides a consistent way of seeing, coordinating and governing change.
That doesn't mean every decision needs to pass through a PMO. In fact, a good PMO should make decision-making easier, not create another layer between leaders and delivery teams. Its role is to provide the information, coordination and governance that allow the organisation to make better decisions.
That is a meaningful organisational capability, and when the need for that capability is enduring, permanence may make sense.
DON'T CONFUSE PERMANENCE WITH AUTOMATICALLY BEING INTERNAL
There is one final point worth making. When leaders decide that PMO capability is likely to be needed for the long term, the next question is often: "Who should we hire?"
That may be the right question. But it doesn't have to be the first one.
Permanent organisational capability can be provided in different ways.
It could be an internal PMO team.
It could be a smaller internal function supported by external specialists.
It could be an ongoing External PMO arrangement.
It could be a combination of internal project leadership and external governance support.
The important thing is to distinguish between the capability the organisation needs to retain and the employment structure used to provide it.
That distinction creates more options. It also helps leadership avoid making a permanent employment commitment before it has fully understood the capability required.
For some organisations, an internal PMO will clearly be the right answer. For others, maintaining access to experienced external PMO support may provide greater flexibility while still delivering continuity and oversight.
Neither is automatically better. The right answer is the one that gives the organisation the capability it genuinely needs.
THE QUESTION ISN'T "DO WE HAVE ENOUGH PROJECTS?"
The decision to make PMO capability permanent is ultimately less about project numbers and more about organisational maturity.
Has project delivery become a sustained part of how you achieve your strategy?
Has coordination across projects become a continuing leadership requirement?
Does the organisation need consistent governance and portfolio visibility regardless of which projects happen to be underway?
Do you need to retain project knowledge and delivery standards over time?
If the answer is yes, then a permanent PMO may be worth serious consideration. If the answer is no, it doesn't mean the organisation doesn't need PMO support.
It may simply mean that the support should remain proportionate to the period of need. That could mean temporary, fractional, contract or External PMO support during a period of change.
The objective isn't to avoid permanence. It is to make sure permanence is justified.
CONCLUSION
A permanent PMO can be a valuable organisational capability. But it shouldn't become permanent simply because an organisation has more projects than it used to.
The better question is whether the organisation has developed a lasting need for project oversight, coordination, governance and portfolio-level decision support.
If it has, a permanent PMO may provide the continuity and organisational knowledge needed to support that environment. If the need is significant but temporary, a different model may be more proportionate. And if the need sits somewhere between the two, there is no reason to force the decision into a simple permanent-or-nothing choice.
At RootRise, we believe the starting point should always be the capability the organisation actually needs.
Sometimes that means building internal PMO capability.
Sometimes it means strengthening an existing team with additional expertise or capacity. Sometimes it means External PMO Support for a defined period or ongoing support without creating a permanent internal function.
The important thing is to make the decision deliberately. Not because "organisations like ours need a PMO". Not because the number of projects has reached an arbitrary threshold. But because you understand what your organisation needs to deliver its strategy with confidence.
If you're considering whether your organisation has reached that point, we'd be pleased to have an initial conversation. There's no obligation to create a PMO — permanent or otherwise. Just an opportunity to look at what your organisation actually needs and whether the capability you have today is enough for what you're asking it to deliver.
