Downsizing or Restructuring a PMO Without Losing Institutional Knowledge
3 August 2026 2 min read
PMOs get restructured or downsized for reasons that usually have nothing to do with whether they’re working — a budget cycle, a reorg, a new executive with a different view of governance overhead. When it happens, the real risk isn’t the headcount reduction itself, it’s losing the accumulated knowledge of how things actually work that never made it into a document.
Identify what only exists in someone’s head, before they’re gone
Every PMO accumulates undocumented knowledge — which stakeholder actually needs to be looped in early on a certain type of decision, why a particular governance exception exists, which reports a specific director actually reads versus ignores. Before any restructure takes effect, run a deliberate knowledge-capture exercise: sit down with departing team members and document the “how things actually work” knowledge specifically, not just the formal process documentation that already exists elsewhere.
Protect the standards, even if you can’t protect the headcount
If the team shrinks, the templates, governance criteria, and reporting standards you’ve built — see our PMO Starter Kit and Governance Pack for the kind of structure worth preserving — are cheaper to keep running with fewer people than to rebuild from scratch later. A smaller team running the same lightweight standards is a very different outcome from a smaller team improvising from memory.
Be honest about what a smaller team can no longer do
A reduced PMO trying to maintain its full previous scope with fewer people doesn’t produce the same quality of output more slowly — it produces silently degraded output, because something has to give and it often isn’t visible until it fails. Decide explicitly, with your own leadership, what’s being deprioritised as a direct consequence of the change, and say so, rather than letting quality erode quietly and get blamed on the team.
Communicate the change to the organisation directly
A PMO that goes quiet during its own restructure creates a vacuum that gets filled with assumptions, usually worse than the reality. A short, honest note to the stakeholders who rely on you — what’s changing, what isn’t, who to go to for what — protects the relationships you’ll need once the team is stable again.
Treat it as a chance to cut what wasn’t earning its keep anyway
Every PMO accumulates some processes and reports that continued out of habit rather than genuine value — a forced reduction is a legitimate moment to cut those specifically, rather than spreading the same reduced capacity thinly across everything the PMO used to do. Ask what can stop entirely, not just what can be done by fewer people.