The 90-day PMO: what to stand up first

Every new PMO leader gets the same two weeks of goodwill and the same impossible mandate: “bring order to the chaos.” Spend that goodwill on a 40-page methodology and you’ll be quietly ignored by week six. Spend it on three things people actually feel, and you’ll earn the runway to do the rest.

1. One status format — and only one

The fastest credibility win is a single, consistent status report that every project uses. Not because templates are exciting, but because comparability is. When every project reports health, the top risks, and variance the same way, leadership can finally scan the portfolio instead of decoding six different spreadsheets. Resist the urge to make it comprehensive. Make it readable in 90 seconds.

2. A front door for new work

Chaos usually enters through the side: a VP corners a developer, work starts, and nobody decided anything. Stand up a simple intake pipeline — request, rough value, rough cost, a priority score — and suddenly “who approved this?” has an answer. You don’t need a governance board in month one. You need a list everyone can see.

3. A risk register that’s actually alive

A risk log that’s updated once a quarter is theater. Pick your ten riskiest projects, get real owners and due dates on the top risks, and review them on a cadence. The goal isn’t a perfect register — it’s the habit of naming problems out loud before they become issues.

The trap: confusing control with value

The failure mode of a young PMO is mistaking process for progress. New gates, new templates, new approvals — each one feels like control and lands like friction. The teams you’re trying to help start routing around you. Every artifact you introduce should pass one test: does this make a decision faster or a risk visible sooner? If not, it’s overhead.

Maturity comes next — but it compounds on trust, and trust is built by making people’s week easier, not their paperwork heavier.