Setting up a PMO that earns its place

A PMO is one of the most useful functions a delivery organisation can have — and one of the easiest to get wrong. When it focuses on templates and reporting for their own sake, teams see it as overhead. When it helps leaders make better decisions and helps projects deliver, it becomes indispensable.

Start with the decisions it must support

Before choosing tools or templates, ask: which decisions do our leaders need to make, and what do they need to know to make them well? Typical answers include which projects to start or stop, where to move people and money, and which risks need senior attention. Everything the PMO produces should trace back to one of those needs.

Choose the right type of PMO

• Supportive: provides templates, guidance and coaching. Suits organisations with experienced project managers.
• Controlling: sets standards and checks compliance. Suits regulated or high-risk environments.
• Directive: manages projects directly. Suits organisations with limited internal delivery capability.

Most organisations start supportive and add control only where risk justifies it.

A practical 90-day plan

• Days 1–30: build a single list of projects with owner, stage, budget and status. Solve one visible problem for a senior leader.
• Days 31–60: introduce a light delivery framework — stage gates, a standard status report and a shared risk and decision log.
• Days 61–90: set a regular portfolio review, agree a few trusted measures, and gather feedback from project teams.

Mistakes to avoid

• Launching with heavy process before showing any value.
• Asking projects for information that no one uses.
• Measuring compliance rather than delivery.
• Treating the PMO as a reporting function separate from delivery.

A typical scenario

In an illustrative example, an organisation running fifteen projects has no shared view of them. In the first month, the new PMO pulls together a one-page portfolio summary and identifies two projects competing for the same specialist team. Leaders re-sequence the work and avoid a clash. That early result builds goodwill, so the light reporting framework that follows is adopted willingly.

Set up proportionately, a PMO gives leaders visibility, teams consistency and projects a better chance of success.