How to Build a PMO Business Case Your Board Will Approve

If you’re pitching for a PMO — or a formal role running one — the business case is usually where good candidates lose the room. Here’s the structure that actually lands.

Lead with the cost of the current state, not the proposed solution

Boards don’t approve process for its own sake. Open with concrete evidence of what the absence of a PMO is costing: projects with no consistent status visibility, rework from unclear sign-off, or a specific failed or delayed project traceable to a governance gap. Quantify it if you possibly can — even a rough estimate beats “improved oversight.”

Keep the proposed model small and specific

Don’t propose a full enterprise PMO with a 12-person team on day one. Propose the smallest version that solves the specific cost you just described — often a “supporting PMO” doing standardised reporting and governance across existing projects, expandable later. A modest, credible first step gets approved far more often than an ambitious one.

Show the reporting the board will actually receive

Bring a mock-up of the monthly or quarterly report the PMO would produce — a single page a busy exec could scan in ninety seconds. This does more to build confidence than a page of methodology description, because it makes the benefit tangible rather than theoretical.

Address the resistance you’ll get before someone else raises it

Someone in the room will think “this is bureaucracy.” Pre-empt it directly: state what the PMO will not do (it won’t add sign-off layers to every decision, it won’t replace team-level planning) as clearly as what it will do.

The ask

End with a specific, time-boxed ask: budget and headcount for a defined period, with a named review point and named success measures. “Approve indefinitely” is a much harder yes than “approve for two quarters, review against these three measures.”