A Project Management Office That Does Not Influence Decisions Is Just an Expensive Email Management Service

An organization might spend millions of pounds on a Project Management Office, only to discover it has bought a sophisticated machine for generating reports without acquiring a better capacity for decision-making.

Imagine a monthly project portfolio review meeting. Dozens of colorful slides, key performance indicators, completion rates, and risk registers are presented to the board of directors. Some projects are green, some are yellow, and a few are red.

Everyone leaves with a comforting impression: everything is under control.

Yet behind these screens are projects competing for the very same resources, decisions delayed for weeks, conflicting priorities across departments, and project managers unable to resolve problems because their authority does not allow it.

Here the question arises: what has the PMO added other than documenting what everyone already knows?

I know this argument will unsettle many who work in PMOs, which is why we must distinguish between the reporting function and the institutional value of the office.

Reporting is important. A project portfolio cannot be managed without reliable information and a clear monitoring methodology. However, a report is a means, not the final product of the office.

Value begins when information helps leadership make a better decision at the right time.

If two projects are competing for the same resource, who has the authority to resolve the priority? If a project continues to consume budget without fulfilling its business case, who has the authority to recommend terminating it? And if dozens of projects are running in parallel, exceeding the organization's real capacity, who can say to management: we cannot execute everything right now?

The PMO does not necessarily need ultimate authority to halt projects. That authority might lie with an investment committee or executive leadership. However, an effective office must at least possess the organizational capability to expose conflicts, present recommendations, clarify the cost of indecision, and follow up on execution.

The deeper issue is that some organizations establish a PMO merely to appear more mature, while refusing to grant it the mandate required to influence decisions.

When the office fails to change outcomes, the organization accuses it of the very bureaucracy it helped create.

From a customer experience perspective, the price of this flaw can be far greater than the cost of the office itself. A project delayed due to an unresolved decision can mean a service unreleased, a product unlaunched, or an ongoing problem that continues to frustrate customers.

I believe that the success of a PMO should be measured by the decisions it helped improve, the conflicts it surfaced early, and the value it protected—not by the number of reports it issued.

If an organization could eliminate its PMO without any change in the quality of its decision-making, the real question is not about how to improve the office, but about the justification for its existence in its current form.