01 · Leading PMOs¶
Running a PMO (Level 3, module 05) is about the mechanics — templates, gates, dashboards. Leading one is a different job: you're accountable for whether the PMO itself delivers value the organisation would notice if it disappeared, and you have to earn authority you're rarely handed outright. Most PMO leaders fail not by picking the wrong framework but by building a PMO nobody outside it believes is worth funding past year one.
The PMO leader's actual scorecard¶
A PMO that measures its own success by "number of templates published" or "percent of projects compliant with the gate process" is measuring activity, not value. A defensible scorecard ties PMO activity to outcomes the organisation already cares about:
| PMO metric | What it should move | How you'd know it worked |
|---|---|---|
| Portfolio-level forecast accuracy | Fewer surprise overruns reaching the executive team | Variance between quarterly forecast and actual shrinks over 3–4 quarters |
| Time-to-decision on cross-project conflicts | Faster resource conflict resolution | Median days from conflict raised to resolved drops |
| Project recovery rate | Fewer projects reaching Level 3's recovery territory (module 08) unnoticed | Number of projects caught at Amber before they hit Red rises |
| Executive trust proxy | Whether leadership uses the PMO dashboard to make real decisions, or works around it | Direct observation — are decisions made in the room referencing your numbers? |
That last row is the honest one: if executives are still asking individual PMs for status in side channels instead of trusting the PMO rollup, the PMO has a credibility problem no template will fix.
Building authority without formal power¶
Most PMO leads have influence, not command authority, over the PMs whose projects they govern. The authority has to be built, in roughly this order:
| Phase | What you do | What you're earning |
|---|---|---|
| 1. Prove usefulness on low-stakes items | Consolidate reporting, remove duplicate meetings, save people time | Trust that the PMO reduces friction, doesn't add it |
| 2. Solve one real cross-project problem visibly | Resolve a resource conflict that was previously unresolved for weeks | Proof the PMO has teeth when it matters |
| 3. Get one gate genuinely enforced | A project doesn't get its next funding tranche without clearing criteria | Real governance authority, not just advisory |
| 4. Become the default source of truth | Executives ask the PMO before asking individual PMs | Institutional authority |
Skipping to phase 3 or 4 before earning phases 1–2 is the most common mistake new PMO leaders make — mandating a heavyweight gate process before anyone trusts the PMO's judgment produces workarounds and shadow reporting, not compliance.
Worked example: turning around a distrusted PMO¶
A PMO has existed for 18 months. Symptom check: PMs submit status reports late and inconsistently, three of the last five "Green" projects turned out to be in recovery territory when finally escalated, and the CFO has started asking for project updates directly from vendors rather than the PMO dashboard.
Diagnosis: the PMO has been operating as supportive (Level 3, module 05) — templates exist, but nothing is enforced, so RAG status reflects what PMs self-report with no verification, and self-reported status trends optimistic.
Recovery plan:
| Action | Why | Timeframe |
|---|---|---|
| Introduce one mandatory, verified metric per project (e.g., CPI/SPI or equivalent Agile proxy) instead of self-reported RAG | Removes the single point of self-report bias that caused 3 of 5 misses | Immediate |
| Spot-check two projects per month against the underlying data, not just the report | Rebuilds the PMO's own credibility with evidence, not assertion | Ongoing |
| Present the CFO with one clean rollup that would have caught the 3 missed projects, retroactively | Concrete proof the new approach works, not a promise | Within one reporting cycle |
| Move from supportive toward controlling for the two metrics that failed, not the whole framework | Precision — a full controlling overhaul without earned trust triggers resistance | Next quarter |
The retroactive proof step matters specifically because "we've changed the process" is a claim; "here's how this exact change would have caught the $400,000 problem you already know about" is evidence, and evidence is what rebuilds a CFO's trust in a PMO that has already disappointed them once.
PMO team structure at scale¶
| Role | Focus | Reports to |
|---|---|---|
| PMO Director | Strategy, executive relationships, governance authority | CIO/COO or equivalent |
| Portfolio Analyst | Rollup reporting, dashboard integrity, data quality | PMO Director |
| Governance Lead | Gate criteria, compliance, stage-gate reviews | PMO Director |
| Agile Coach (if applicable) | Cross-team agile practice, Scrum of Scrums facilitation | PMO Director |
| PM Community Lead | Templates, training, lessons-learned repository | PMO Director |
A PMO of one person doing all five roles is normal below a certain scale; the risk is scaling headcount before scaling trust — adding a Governance Lead to enforce gates nobody yet believes in just adds a second person the organisation routes around.
How It Actually Works¶
"Authority without formal power" has a specific organizational-behavior mechanism behind it: influence in a matrixed organization runs largely on accumulated credibility capital, which behaves like a resource that is earned in small increments (a forecast that turned out accurate, a risk flagged before it materialized) and spent in large ones (one high-visibility miss can erase months of accumulated trust). This asymmetry — slow to build, fast to lose — is the actual reason a PMO's first 90 days matter disproportionately: early wins compound into a credibility balance that later, larger asks can draw against, while an early visible miss forces the PMO to rebuild from zero under heightened scrutiny, which is measurably slower than building from zero under neutral scrutiny because every subsequent claim now gets extra verification before anyone acts on it.
Exercise¶
You inherit a PMO where the dashboard is technically accurate but nobody in leadership uses it — every steering committee still asks PMs to present their own slides from scratch.
- Using the four-phase authority-building table, diagnose which phase this PMO is stuck at and why (be specific about what evidence in the scenario points to that phase).
- Propose one low-stakes, high-visibility action (phase 1 or 2 style) you would take in your first month, and explain why it's sequenced before any gate-enforcement change.
- Design one PMO scorecard metric (using the outcome-tied format from the first table) that would let you prove, in two quarters, that the PMO is worth its budget.