Setting Up a PMO From Scratch: The First 90 Days

Most new PMO leads try to build everything in the first month — full governance, a tool rollout, standardised templates across every team. It usually backfires. Here’s a sequence that builds credibility instead of resistance.

Days 1–30: visibility before control

Your first priority is not governance — it’s an accurate picture of what’s actually happening across current projects. Run a lightweight status collection (even a simple spreadsheet) across every active project before introducing a single new process. This does two things: it gives you real data for later decisions, and it costs project teams almost nothing, which buys you goodwill for what comes next.

Days 30–60: one standard, applied narrowly

Introduce a single standard — usually a consistent status report format — and apply it only to the highest-visibility projects first, not the whole portfolio at once. Prove the format works and actually gets read by leadership before asking every team to adopt it. Rolling out an untested standard everywhere at once is the single most common cause of PMO resistance.

Days 60–90: governance, sized to actual risk

Only now introduce formal governance — stage gates, sign-off requirements, escalation paths — and size it to the risk profile of the project, not uniformly. A low-risk internal tooling project doesn’t need the same sign-off depth as a customer-facing system migration. A PMO that applies heavyweight governance to everything gets seen as bureaucracy; one that scales governance to risk gets seen as useful.

The trap: mistaking activity for authority

New PMO leads often measure their own success by how many processes they’ve introduced. Measure it instead by whether senior stakeholders are making better decisions faster because of what your PMO provides. If nobody outside the PMO would notice if it disappeared tomorrow, it isn’t yet delivering value — regardless of how much process exists on paper.

Where to start if you want a structure, not a blank page

Our PMO Starter Kit is built around exactly this sequencing — visibility, then a single standard, then risk-scaled governance — rather than a generic full-framework template.