Why Teams Route Around Your PMO Instead of Through It
Sep 09, 2026
Organizations usually come to us with some version of the same pattern: teams keep their own trackers off to the side. Status updates go into the PMO's system, then get rebuilt somewhere else so the work actually stays visible. Decisions happen in hallway conversations and side threads, and the PMO finds out after the fact.
None of that means the PMO isn't trying. It usually means it's solving a problem the organization doesn't actually have anymore — or never fully defined in the first place.
The diagnostic teams skip
Most PMOs respond to this by tightening what they already do: more templates, more required fields, more mandatory check-ins. That almost always makes it worse, because it treats a structural mismatch as a compliance problem.
Before changing anything, it's worth answering four questions honestly:
-
What does the PMO produce, and what do teams actually use? If the honest answer is "reports" and "nothing," the PMO is likely optimized for process and compliance instead of outcomes.
-
Can it change outcomes, or only report on them? If it can only surface a problem, not act on it, it may be missing the authority or executive backing to matter.
-
Why do people route around it, specifically? If the answer is about how the PMO operates — cadence, tooling, who it reports through — that's a fit problem between the PMO and how teams actually work.
-
What did you expect it to change when it was stood up? If no one can answer that clearly, the PMO may simply have the wrong mandate or operating model for what the organization needs today.
Each answer points somewhere different. A PMO with the wrong mandate needs re-scoping, not more rigor. One that's process-heavy needs to be re-measured, not re-templated. Fixing the wrong one just adds friction to a function people are already avoiding.
What it's quietly costing
A PMO that gets routed around isn't neutral — someone is still doing the coordination work, just informally, without visibility, and without anyone accountable for it. That shows up as duplicate tracking effort, decisions made without the full picture, and a PMO that can't produce a credible answer when leadership asks what it's actually for.
What "good" looks like
A PMO worth keeping is measured on delivery outcomes, not on how much process it enforces. Teams work through it because it's the fastest path to a decision, not because policy requires it. It has a mandate specific enough that everyone — the PMO, the teams, and leadership — can describe what it owns in the same terms.
Getting there is a scoping exercise, not a rollout of more governance. Building and re-mandating PMOs is the entirety of what The PMO Squad does — not a module inside a broader consulting practice — which is why our Purpose-Driven PMO work starts with the same four-question diagnostic above before touching process, tooling, or templates. We're not there to help you enforce the current model better; we're there to determine whether it's the right model at all, then build the mandate and operating model around what the organization actually needs the PMO to do.
Where this isn't a fit
This isn't the right conversation if the goal is to keep the PMO's current process intact and just get better compliance with it. It's also not a fit if there's no real appetite to change the PMO's mandate — re-scoping only works with genuine authority to do it.
If this sounds like your PMO
Run the four questions above honestly first. If the answers point to a structural mismatch rather than an effort problem, it's worth a conversation about what's actually happening before deciding what to change.
Follow Us on LinkedIn
