Your PMO Is Keeping Score, Not Changing It
A company tires of projects running late and over budget, so it stands up a project management office to get a handle on them. Templates go out. Every project reports status on the same cadence, in the same format, with the same red, yellow, and green indicators. Within a few months the dashboards are immaculate. Leadership can see, at a glance, the health of every initiative in the portfolio. The PMO is working exactly as designed. And projects are still running late and over budget at nearly the same rate as before.
This is the quiet disappointment at the center of a lot of PMOs. The office was built to improve how projects turn out, and instead it became very good at describing how they turn out. A dashboard that reports a project is in trouble is not the same thing as a PMO that does something about it. Somewhere between the ambition and the rollout, helping projects succeed got swapped for tracking whether they do, and the two are easy to confuse because they generate the same meetings and the same reports.
A Dashboard Is Not an Intervention
Knowing a project is red does not make it green. Visibility is only useful if someone acts on what it reveals, and the implicit theory behind a reporting-first PMO is that visibility alone will drive better outcomes. The belief is that once leadership can see a struggling project, the problem will somehow get addressed. But seeing was rarely the bottleneck. The project team usually knew it was in trouble long before the status turned red. What the team lacked was not awareness. It was the decision, the resource, or the help that would have changed the trajectory, and a status report delivers none of those.
So the PMO accumulates ever more precise information about problems it is not positioned to solve. The reporting gets sharper, the cadence gets tighter, the formats get cleaner. The projects themselves move exactly as they would have without any of it. An office that measures outcomes it cannot influence is not managing projects. It is narrating them.
Why Scorekeeping Wins
The drift toward reporting is not laziness. It is incentives. Tracking is safe and intervening is not. Measuring compliance, whether the team updated the tracker and followed the template, is easy and uncontroversial. Stepping into a struggling project to make a call about scope, resourcing, or whether it should continue at all is political, risky, and demands authority the PMO usually does not have.
Most PMOs are handed a mandate to observe but not to act. They can require a status update. They cannot reallocate budget, overrule a sponsor, or stop a project. Given responsibility for outcomes and no power to affect them, the office does the only thing available to it, which is measure and report. The familiar pattern of a status that stays green until the week it suddenly goes red follows directly from this. A team that is tracked but not helped has every reason to manage its reporting rather than expose its problems to an office that will log the trouble without relieving it.
A PMO That Changes the Score
The useful question, when standing up a PMO or fixing one, is plain. When a project is in trouble, what is this office able to do about it. If the honest answer is produce a report that says so, the PMO is overhead, however polished the output. If the answer involves clearing a blocker the team cannot clear on its own, moving people to where they are needed, forcing a scope decision that has been avoided for weeks, or recommending with real weight that a doomed project be stopped, then the office is earning its cost.
That requires two things a reporting-first PMO tends to lack. The first is authority, or at least a direct line to someone who holds it, so that a red status triggers a decision rather than another slide. The second is capability, people in the office who have run hard projects themselves and can help a struggling team rather than only audit it. An office staffed to check compliance will check compliance. An office staffed to rescue projects can rescue them. The two look similar on an org chart and produce entirely different results.
The measure of a PMO was never the quality of its dashboards or the discipline of its reporting cadence. It is whether projects are more likely to succeed because the office exists. A PMO that only keeps score has mistaken the scoreboard for the game. The ones worth having are built to change the score, and that starts with giving the office something real to do on the weeks the number is bad.