The PMO Nobody Mandated
You head a five-person PMO at Nordwind Systems, a 900-employee industrial automation manufacturer. The PMO was created fourteen months ago after an ERP rollout ran 40% over budget, but its mandate was never written down. The CFO sponsors it and wants one page of numbers per month; the CEO is neutral. There are 38 active projects, eleven of them more than 15% over budget. About 60% of project managers submit status late, and the risk register is maintained by nobody outside your team. Two senior project managers with twenty years' tenure publicly call the PMO 'administrative overhead' and refuse to use the status template because 'our projects are different'. The next steering committee is in three weeks and the CFO has asked what the PMO has actually delivered. Your team is competent but demoralised; one analyst has already resigned.
1. How should you establish the PMO's legitimacy in the next 90 days? State what you would do first, what you would deliberately not do, and why.
Read the worked answer
A PMO's legitimacy rests on three sources: a formal mandate, demonstrated value, and relationships. Here only the second and third are available in the short term, so a template-and-compliance campaign in week one would fail - the resistors would simply escalate to a neutral CEO who has no reason to back you.
Weeks 1–4 - diagnosis and mandate. Interview the CFO, the CEO's chief of staff, and 8–10 project managers including both critics; the purpose is to find what decisions are currently being made wrong, not to explain the methodology. Simultaneously draft a one-page mandate with the CFO covering scope, decision rights, and the three things you will not do. A written mandate converts sponsorship into something the CEO can be asked to endorse.
Weeks 4–8 - one visible win. Take the three worst-performing of the 38 projects, run a recovery review with their own project managers, and produce a decision paper each. Value is proven by recovering money, not by counting submissions.
Weeks 8–12 - minimum viable reporting. Agree with the CFO one page: exceptions and decisions required, not a RAG wall. Baseline the 60% late-submission figure so you can show movement later.
Deliberately not doing: mandatory tooling rollout, competency certification, or a methodology handbook before the first win. These consume credibility you have not yet earned.
2. The two senior project managers continue to refuse the template. What are your options, and which do you recommend?
Read the worked answer
Four realistic options:
- Enforce. Escalate to the CFO and make compliance mandatory. Fast, but with a neutral CEO and twenty years of tenure on their side, this converts a two-person dispute into a governance referendum you may lose.
- Exempt. Let them opt out. Cheap, but the 60% late-submission problem is watching, and the exemption legitimises every future refusal.
- Co-opt. Give them a formal role - peer reviewers on the three recovery reviews, or a joint working group on what 'different' actually means in data terms.
- Differentiate. Accept a different content in exchange for a fixed minimum data set and a fixed date.
Recommendation: co-opt plus differentiate. Their objection is not really about templates; it is about status and the implication that their judgement needs supervision. Co-opting them into a defined, visible role addresses that, and their 38-project overview makes them genuinely useful reviewers.
In parallel, agree one page of irreducible data - schedule position, top risk, next decision - and a monthly date. Where they can demonstrate that a field is meaningless for their project type, drop it: this signals you are listening rather than capitulating.
Set a boundary. If the minimum is still missing after two cycles, escalate on that single specific failure, not on attitude. Choose that fight only when the first win has been banked, so the CFO is defending a PMO that has already delivered something.
3. What should you present to the CFO at the steering committee so the PMO is not reduced to a reporting factory?
Read the worked answer
The CFO's request for 'one page of numbers' is a symptom, not the requirement: what a CFO needs is early warning and confidence that decisions are being taken. Presenting a dashboard of RAG statuses confirms the 'administrative overhead' accusation, because a bad dashboard only tells executives what they could have learned from the project managers anyway.
Structure the pack around decisions, not projects. For each item: the issue, the money at stake, the decision required, the owner, the date. With 11 of 38 projects over budget by more than 15%, pick the six where a decision in the next 30 days actually changes the outcome, and say so explicitly.
Triangulate before presenting. Sample six projects and cross-check schedule and cost claims against source records. Expect two to be materially wrong; finding that yourself builds far more credibility than a clean-looking report would.
Quantify the PMO's contribution in a form the CFO uses. Avoid 'number of reports produced'. Use recovered spend, benefits at risk, and decisions enabled - and be honest about what you cannot attribute.
Ask for something. Request the written mandate at this meeting, plus one decision right: the PMO defines portfolio reporting standards. A PMO that only presents is a service; a PMO that owns a standard is an institution.
Finally, acknowledge the resignation and the team's morale by proposing a leaner, decision-focused remit - funding what works is more persuasive than defending headcount.