PMO Leadership
What the domain tests
The PMO leadership domain tests whether you can position a PMO as a value-creating organisational function rather than an administrative service. Questions probe mandate, operating model, service design, influence without authority, governance interfaces and evidence of outcomes.
Core rules
- A PMO mandate must be written, sponsored and revalidated; without it the PMO drifts into policing.
- Design the operating model deliberately: central, hub-and-spoke or embedded. Choose based on decision speed, scale and project criticality, not fashion.
- Publish a service catalogue with customers, inputs, outputs and service levels. Services typically include portfolio prioritisation, assurance, reporting, method tailoring, tooling and competence development.
- Lead through influence: map stakeholders by interest and impact, agree decision rights, and broker conflicts between delivery and governance.
- Measure outcomes the organisation values - decision cycle time, benefits realisation, assurance closure - not report volume.
- Evolve maturity in steps; a PMO that adds controls faster than it adds capability loses credibility.
Worked example
A PMO is asked to 'improve reporting'. The weak answer builds a new template. The stronger answer interviews portfolio leaders, finds that decisions wait for monthly packs, and proposes a decision dashboard with named decision owners and a weekly cadence. It pilots with one programme, measures decision latency before and after, then scales. Reasoning: the request was an output; the PMO addressed the decision system, used stakeholder evidence and measured an outcome.
Traps
- Defining PMO success as project success; the PMO enables but does not own delivery.
- Centralising everything; some services belong embedded.
- Confusing assurance with audit.
- Launching a service catalogue without service owners or SLAs.
- Reporting activity counts instead of decision or benefit outcomes.