Is the PMO governing projects, or trying to control complexity with inadequate tools?

Few PMO heads openly admit this.

However, there is a significant difference between controlling projects and improving the organization's ability to deliver value.
Many PMOs confuse these things.

• The dashboards are up to date.
• The executive forums take place.
• The indicators are green.
• The reports are submitted on time.

Even so:

• The organization remains slow.
• Priorities change every week.
• Business areas are constantly overloaded.
• Stakeholders complain about bureaucracy.
• Projects compete with one another.
• The portfolio grows faster than the organization's delivery capacity.

At some point, it is worth asking an uncomfortable question:

Is the PMO solving the problem, or merely organizing the chaos in a visually elegant way?

The book Doing the Right Project: Using a Systems Thinking Approach to Select Successful Projects raises precisely this type of question.

Most PMOs still operate according to a linear logic:

• Identify the problem;
• Create controls;
• Measure compliance;
• Expand governance.

The difficulty is that complex organizations do not respond linearly.
Often, the attempt to increase control begins to reinforce the problem itself.

Tools such as Causal Loop Diagrams help to make this behavior visible.

• More approvals generate:
• More queues;
• More handoffs;
• More delays;
• More multitasking;
• Greater executive dependency.

The natural response is usually predictable: create even more governance.
The system then enters a loop.
The PMO begins to act as an administrative stabilizer while the organization loses its adaptive capacity.

This may be one of the most uncomfortable conclusions:

A PMO can increase operational maturity while simultaneously reducing organizational viability.

Stafford Beer’s Viable System Model addresses precisely this imbalance between:

• Operations;
• Coordination;
• Control;
• Intelligence;
• Adaptation.

Organizations survive through adaptation.

Yet many PMOs remain designed to preserve stability in environments that change too quickly.
There is another issue.

The organizational chart rarely explains how decisions are actually made.

Projects may follow the formal governance structure, but influence, priority, and decision-making speed usually circulate through informal networks.

Tools such as:

• Social Network Analysis;
• Actor Mapping;

show that some individuals accelerate decisions without holding executive positions, while others can obstruct entire programmes without ever appearing in the steering committee.

Almost no PMO measures this.

Perhaps because it is more comfortable to measure:

• Schedule;
• SPI;
• KPI;
• Status reports.

Then to discuss:

• Influence;
• Systemic behaviour;
• Organizational overload;
• Capacity degradation;
• Perceived value.

There is another important challenge to conventional thinking.

Many PMOs believe that the portfolio problem is prioritisation.

This is not always the case.
Sometimes, the real problem is the organization's inability to stop initiatives.
The system continues absorbing demand until it reaches saturation.

The Stock and Flow Model helps to reveal precisely this dynamic: the invisible accumulation of work that gradually degrades capacity, collaboration, and delivery speed.
This rarely appears in traditional reports.

Another relevant issue is that different business areas often interpret the same problem in entirely different ways.
While one area perceives “governance,” another perceives “bureaucracy”.
While leadership understands “control,” teams experience “delay”.
Tools such as:
Cognitive Mapping;
CATWOE;
help reveal these differences in perception before they develop into organizational conflict.
Perhaps the most difficult conclusion for many PMO heads is this:
A PMO can be highly competent at governing projects and still contribute to the exhaustion of the organizational system.
This type of discussion has appeared increasingly frequently in PMO assessments conducted by AIPMO recently.
Often, the problem was not:

• The absence of processes;
• The absence of processes;
• The lack of indicators;

Or the absence of governance.
The problem was the system’s inability to:

• Adapt;
• Prioritise;
• Integrate business areas;
• Sustain flow;

Reduce organizational friction.
Tier 1 assessment helps initiate this type of analysis.
It is not merely an operational questionnaire. It is a diagnostic mechanism designed to identify patterns that normally remain invisible in the PMO’s day-to-day activities.

Many organizations discover, for example:

• Excessive governance without a proportional increase in value;
• Limited strategic influence;
• Structural portfolio overload;
• Conflicts between control and speed;
• Misalignment between business areas;
• Operational maturity without adaptive capacity.

This type of reflection usually changes the PMO’s mindset.
The discussion becomes:

“How can we increase the organization's capacity to generate value without degrading the system itself?”

You can run a masterclass with your team that examines this change in perspective in greater depth.
It is not intended to introduce another methodology.
Instead, it discusses:

• Organizational behavior;
• System dynamics;
• Adaptation;
• Governance in complex environments;
• Influence;
• Overload;
• Portfolio flow;
• Operational sustainability.

The modern PMO challenge no longer appears to be limited to project execution.
The challenge lies in understanding how decisions, governance, and control structures influence organizational capacity, speed, collaboration, adaptation, and perceived value within the system itself.
In some cases, this discussion naturally evolves into more extensive PMO transformation initiatives.
Not necessarily because the organization wants more governance, but because it begins to recognize that some portfolio problems do not originate within projects.
They originate within the organizational system that produces those projects.

Nelson Rosamilha,PhD
[email protected]