A while back, I attended a PMO roundtable hosted by the PMI Puget Sound Chapter. The topic was starting a PMO.
The room included a small group of experienced project managers and PMO leaders from several large local organizations.
I asked two questions:
What does your PMO cost the company each year?
How much work can your PMO reliably commit to managing at one time?
The answers were harder to pin down than I expected.
The Full Cost Was Difficult to See
People could name the parts of the PMO cost.
Project management salaries. Contractors. Software. Training. Administrative support. PMO leadership.
But no one could pull those pieces into a reasonably complete annual number.
That was not a reflection of their experience. It said more about how PMOs are often structured.
Project managers may sit in one budget. Software sits somewhere else. Contractors are charged to individual initiatives. Training and administrative costs may be controlled by another department.
The PMO leader can be responsible for results without owning, or even seeing, the full cost of the operation.
That makes some basic management questions difficult to answer:
Are we getting enough value from the PMO investment?
What does additional capacity really cost?
Would another project manager solve the problem?
Could a different operating model provide better coverage or flexibility?
When the total cost is unclear, those decisions are often made one expense at a time rather than from a clear view of the whole function.
Capacity Was Even Harder to Define
My second question was about capacity.
How many initiatives can your PMO manage at one time without putting existing commitments at risk?
Most described intake as a judgment call.
They looked at what was already underway, talked with the team, and decided whether another initiative felt manageable.
Several said that an initiative could usually move forward if it came with enough budget for a contract project manager.
That may solve the immediate staffing need. It does not necessarily solve the capacity problem.
The new project manager still enters an existing environment. The initiative may need the same executives, subject matter experts, technology teams, vendors, and business resources already committed elsewhere.
Available funding can also allow one initiative to move ahead of work that may matter more to the business.
One person shared the only concrete capacity example. A PMO he knew planned around each project manager handling three projects a year.
That number needs more context. Three small projects and three complex, cross-functional initiatives are not the same. Still, the organization had made an effort to define what its PMO could reliably carry.
PMO Capacity Should Be More Than a Feeling
There is no perfect formula for PMO capacity.
Initiative size, complexity, risk, timing, dependencies, and leadership demands all matter. Capacity cannot be reduced to project count alone.
But a PMO should still be able to describe the level and type of work it is prepared to support.
Without that, demand keeps entering the portfolio until people become overloaded, delivery slows, or leadership has to step in.
By then, a capacity issue has become an execution issue.
This Is an Operating Model Question
The roundtable left me wondering how many PMOs operate without a clear view of their total cost or committed capacity.
They may have capable project managers, useful tools, regular reporting, and some responsibility for intake and prioritization.
But the PMO has not been defined as a complete business capability with a known cost, a clear service expectation, and an agreed level of capacity.
That is a different standard.
A well-defined PMO should be able to explain:
- What it costs to operate
- What services it provides
- What type and volume of work it can support
- How demand is managed against available capacity
- What leadership should expect from the investment
These are not just administrative details. They shape how confidently the business can approve, prioritize, and deliver strategic work.
Why a Fully Managed PMO Belongs in the Conversation
This is one reason a fully managed PMO service should be among the options executives consider.
In a fully managed model, cost, capacity, and service expectations can be defined up front. The framework, dashboards, software, portfolio controls, governance, operating cadence, and trained delivery team are already in place.
Leadership has a clearer view of what it is buying, how much work the PMO can support, and how capacity can adjust as business demand changes.
That does not make a fully managed PMO the right answer for every organization.
Some companies should build and operate the capability internally. Others may need fractional PMO leadership or targeted project support.
A fully managed PMO becomes relevant when the organization needs an established execution capability with committed capacity, predictable cost, and clear accountability.
Two Questions Worth Asking
The discussion left me with two questions every PMO should be able to answer:
What does your PMO cost the company each year?
How much work can it reliably commit to managing?
If those answers are unclear, it does not mean the PMO is failing.
It does mean leadership may not have a complete view of the capability it is funding or the amount of work it can safely ask that capability to carry.
Before adding another project manager, contractor, or software platform, get clear on cost and capacity.
The answers will tell you a lot about the PMO you have and the operating model you may need next.
Take a deep dive into calculating PMO costs.
