When some solutions worsen the problem they were meant to solve
Faced with this chaos, people tend to add more committees, templates and progress reports. That’s how PMOs become “overcomplicated bureaucracies.”
Let’s illustrate with an “imaginary” case: an IT department overseeing 80 active projects implemented a highly prescriptive PMO, with detailed reporting required at every stage. Findings over twelve months: the time devoted to reporting increased significantly, without any measurable improvement in delivery timelines¹. This PMO was designed as a control function before the organization’s project management maturity justified it. Starting instead with a support model covering a limited scope, measuring the actual impact on strategic alignment before adding control mechanisms, and so on, would probably have provided the same level of visibility without doubling project managers’ administrative workload.
► The risk is putting the wrong structure in place, in the wrong order, before securing the support needed to make it work.
Internal resistance: a blind spot?
Setting up a PMO is a shift in power. The most experienced project managers may see it as a loss of autonomy, while senior management may see it as another cost centre that needs to be justified.
Most of the time, a PMO fails because it lacks an executive sponsor who is sufficiently committed to resolving priority conflicts and protecting the PMO’s mandate when the first signs of resistance emerge. PMI research points in the same direction: sustained senior-management involvement is one of the most reliable predictors of success for an initiative of this kind².
► If you’re considering taking on this project, the first question to ask yourself is: “Who above me is prepared to defend this mandate when a director comes to ask why their project has been delayed because of portfolio-prioritization decisions?”
What if all you needed was a PMO sized to your reality?
A coherent, manageable PMO is built on a few foundational decisions that must be made in the right order and adapted to your context, not copied from a white paper.
1.Choose the right positioning.
A support PMO equips and coaches your project managers. It’s ideal when your organization is changing rapidly and needs flexibility. A controlling PMO imposes strict standards and close monitoring. It can work in an already standardized environment (but be careful: it requires significant resources and political buy-in). A directive PMO goes further: it directly provides and manages project managers. It offers strong consistency, but requires a high level of authority and is rarely appropriate at the beginning of the journey. These three types are distinguished primarily by the degree of delegated authority, not by maturity.
2.Clarify where the PMO reports.
Your position in the organizational chart determines your real influence over decisions. If you report to a technical function, you remain close to the teams but risk being perceived as one stakeholder among many. If you report to the executive team or a transformation function, you gain the legitimacy to exercise decision-making authority within defined boundaries when competing projects need to be prioritized—provided that authority is explicitly delegated to you.
3.Define a pilot scope, not a big bang.
Some organizations aim for approximately one PMO position for every 15 to 20 active project managers³, but this figure is only a starting point, not a requirement: the maturity of your teams, the complexity of your projects and your management culture can shift this ratio in either direction. What matters is the discipline of starting small: one business area, one category of strategic projects, before expanding further.
4.Choose a limited number of mechanisms, and execute them well.
• A charter documenting your actual mandate and the limits of your authority.
• A decision-making forum to resolve priorities.
• A responsibility matrix clarifying who decides, who executes and who is consulted.
• And a limited number of indicators measuring the strategic alignment of your projects and the benefits achieved against their baseline—not just the schedule.
► This last distinction is what separates a useful PMO from an overcomplicated bureaucracy.
What still needs to be decided, and cannot be improvised alone
You now know which foundational decisions make PMOs viable. What this article cannot do for you is help you make those decisions for your organization: what level of authority to request from senior management given your internal culture, how to build a rollout plan that anticipates resistance from your most influential project managers, and which indicators to choose so that your executive committee quickly sees the value of the PMO rather than its administrative burden.
That’s what our training course Project management: setting up a project office to ensure consistency and performance, explores. It is designed for supervisors, project coordinators and team leaders who must champion this initiative with senior management. You leave with an implementation plan tailored to your organization, along with the arguments needed to secure the executive support on which your PMO’s survival depends.
¹ PMI, Pulse of the Profession 2023 – Power Skills, Redefining Project Success.
² Standish Group, Chaos Report 2018.
³ PMI, Pulse of the Profession 2018 – Success in Disruptive Times.
