Almost every PMO I've been asked to fix has the same origin story: a program failed visibly enough that leadership decided "we need a PMO," someone stood one up quickly, and within a year it had settled into a role nobody actually respects: the group that collects status updates and turns them into slides for someone else's steering committee.
That's not a staffing problem. It's a design problem, and it's baked in from day one if nobody answers a simple question before the PMO exists: what can this group actually decide, versus what can it only report on?
The PMO That Everyone Sends Slides To
A PMO with no decision rights becomes, by default, an information-processing function. Delivery teams learn quickly that the PMO can't actually change a resourcing decision, override a vendor escalation, or force a scope trade-off, so they treat it as an audience, not an authority. Status gets sanitized before it reaches the PMO, because there's no cost to doing so and no benefit to being fully honest with a group that can't act on what you tell them.
This is corrosive in a specific way: it looks like the PMO is working - reports go out, dashboards get updated, meetings happen on schedule - while the actual signal quality keeps degrading. Leadership eventually notices that the PMO's dashboards said green right up until a program blew up, and the conclusion drawn is usually "the PMO isn't very good," when the real issue is that it was never given the authority to be good at anything beyond compiling what it's told.
Three Signs Your PMO Has No Real Authority
First: nobody consults the PMO before committing to a delivery date externally. They inform it afterward. Second: the PMO's escalation path exists on a slide but has never actually been used to stop or redirect a program in trouble. Third: when a program does fail, the retrospective doesn't mention the PMO at all, because it was never positioned to have prevented anything.
If any of these describe your PMO, the fix isn't better reporting templates or a new dashboard tool. It's a written charter, signed off by the executive sponsor, that says explicitly what the PMO can mandate, what it can only recommend, and where it escalates when its recommendation is ignored.
What Changes When a PMO Earns Its Seat
The PMOs that actually earn influence do it through a small number of visible, real decisions in their first two quarters, not through a large process rollout nobody asked for. They pick the two or three highest-friction points in the organization's delivery model, fix those specifically, and let the credibility from those wins do the work that a governance framework document never will.
None of this requires a large team or an elaborate operating model. It requires the organization to decide, honestly, whether it wants a PMO that reports or a PMO that decides, and then to actually build the second one, on purpose, instead of drifting into the first by default.