Why your PMO dashboard is a work of fiction, and the laws that explain it.
Your portfolio is “Amber, trending Green.” It has been for eleven months. Then, with six months to handover, three projects turn red in the same quarter, and the leadership team asks how this could have happened. Nobody was lying. That’s the problem.
You built a system in which the truth was optional. The scorecard belongs to the player.
On most construction projects, the project manager plans the programme, declares the progress, forecasts the cost, rates their own risks, picks their own RAG status, and reports upward. Then we call it governance.
Economists call this the principal-agent problem. The agent (the PM) has better information than the principal (the organization) and different incentives. Add a bonus, a reputation and a next project that all depend on the numbers, those numbers will bend, even without anyone consciously lying and you have designed a machine for flattering data.
This isn’t about dishonesty neither it is conflict of interest we’ve normalized. Most project managers are capable, committed people. The problem is structural.
No finance department lets a manager audit their own expenses. No hospital lets surgeons self-report their complication rates without verification. Yet in project delivery, we hand the scorecard to the player and wonder everyone scores well.
How the bending actually happens :
It rarely looks like fraud. It looks like reasonable judgment:
Watermelon reporting: green on the outside, red on the inside. The status is green because the PM “has a recovery plan.
Contingency hiding : delays absorbed into float, costs absorbed into contingency, until nothing is left to absorb.
Metric selection : reporting what looks good (milestones achieved) and quietly dropping what doesn’t (open RFIs, rework rates, unresolved design changes).
Optimism as a leadership style : bad news is “premature to escalate.
Upton Sinclair said it best: It is difficult to get a man to understand something when his salary depends on his not understanding it.
The laws that should worry you
1] Goodhart’s Law: When a measure becomes a target, it ceases to be a good measure. Reward green status and you will get green status.
2] Campbell’s Law: The more an indicator is used for decision-making, the more it is corrupted. The pressure distorts not just the number but the work behind it.
3] The 90-90 Rule: The first 90% of the project takes 90% of the time; the last 10% takes the other 90%. Every “we’re 90% complete” is a polite fiction experience has already disproved.
4] Hofstadter’s Law: It always takes longer than you expect, even when you take Hofstadter’s Law into account. Yet forecasts are written as though this project is the exception.
5] Parkinson’s Law and Student Syndrome: Work expands to fill the time available, and people start at the last moment. Any float a PM controls will be consumed and reported as “managed.”
6] Brooks: How does a project get to be a year late? One day at a time.* Slippage is a thousand self-reported “minor delays,” each too trivial to escalate.
7] Flyvbjerg’s Iron Law of Megaprojects : Over budget, over time, under benefits, over and over again. His research points to strategic misrepresentation underestimating cost and overestimating benefit because that’s how projects get approved and careers get made. Add optimism bias (Kahneman and Tversky’s planning fallacy) and you have an industry that believes its own press releases.
None of these are exotic. They are the best-documented findings in our field. And our reporting model ignores every one of them by asking the person with the strongest incentive to be optimistic to be the sole source of truth. Watermelons, by design : Green on the outside, red on the inside. It isn’t a character flaw. It’s the rational output of a system that punishes early bad news and rewards calm dashboards. A PM who escalates in month three is “not in control.” A PM who escalates in month fourteen, when it’s undeniable, is “managing a difficult situation.” We teach people to wait, then wonder why we find out late.
The PMO’s uncomfortable questions & PMO’s role
Here’s the critical question many PMOs avoid: Are we an independent assurance function, or a reporting secretary? If it collects PM-submitted data, formats it with templates and slicers, and forwards it to the same director who owns delivery results, it adds no assurance. It adds credibility theatre. Polish makes unverified numbers look audited. That is arguably worse than no report, because it earns trust the data hasn’t earned and if the PMO depends on PMs’ goodwill for its data and on the delivery director for its budget, it can’t be independent. It’s a mirror, and mirrors don’t warn you.
The question nobody wants to answer: who does the PMO report to?
Independence is not a feature of the dashboard. It is a feature of the org chart. Show me who the PMO reports to, and it will tell you what it can afford to say. Here are the realistic options, with their flaws.
1] Head of Delivery / COO. The most common arrangement, and the most compromised. The PMO polices the very person who controls its budget, headcount and career paths. Bad news travels upward through the person it embarrasses. This PMO is a reporting secretary, not an assurance function.
2] CEO / Managing Director. Better, because it has authority and the PMO isn’t subordinate to delivery. But CEOs are also measured on results and share the optimism bias. A CEO who has just promised the board a record year is not a neutral audience for a red portfolio.
3] CFO. Stronger independence, a natural link to cost, valuation and audit discipline. But the risks are real: the PMO may collapse into a cost-and-cash function, miss the programme, design and site-readiness signals that predict trouble, and be seen on site as “finance coming to count the beans.” CFOs also have their own incentives, particularly around margin and earnings guidance.
Board or Audit & Risk Committee (with a dotted line to the CEO). The strongest independence. It mirrors the Three Lines Model : delivery teams own risk (first line), oversight functions advise and monitor (second), and independent assurance reports to the board (third). The risk is distance: an assurance team with no operational credibility is ignored, or arrives at the board with technically correct but irrelevant findings.
The split model. My view, and the one should defend : stop asking one function to be both coach and referee.
PMO (enablement): methods, tools, training, templates, resourcing. It supports delivery and reports into the COO or Head of Delivery. Its job is to help projects succeed.
Project Controls & Assurance (independent): verifies progress, cost and risk, runs health checks and reference class forecasts. It reports to the CFO or, better, the Audit & Risk Committee, with a direct, unfiltered line to the board and protection from being overruled by delivery leadership.
Many organizations merge these two roles under a single “PMO” and then wonder why it is too timid to challenge and too distant to help. A function cannot be the PM’s friend and the PM’s auditor at the same time. Even this model needs guardrails: assurance leaders with security of tenure, budgets not set by those they assess, and the right to publish findings without delivery’s sign-off. Otherwise independence is a job title, not a fact.Once the reporting line is right, change what gets measured and how:
What independent measurement looks like
Separate the doing from the measuring. You don’t have to distrust your people. You have to stop designing a system that depends on their self-sacrifice. You don’t need to dismantle project teams. You need to separate doing from measuring.
Measure reality, not reports. Use site-verified quantities, BIM-linked tracking and independent QS valuations instead of self-declared percent complete.
Break the reporting line. Assurance reports to the CFO, the board or the audit committee, not to the head of delivery. Finance learned this a century ago.
Use the outside view. Apply reference class forecasting: compare each project’s forecast against the actual outcomes of comparable past projects, not against the PM’s belief in their own plan.
Standardize metric definitions centrally. If every PM defines “complete” differently, you’re comparing opinions.
Favour leading indicators. Percent Plan Complete from lookahead planning, open design queries, permit and access readiness, subcontractor resource turnout and rework trends reveal trouble earlier than cost and schedule variance.
Run independent peer reviews. Rotate experienced PMs from other projects into short, structured health checks, as audit does for finance.
Reward early bad news. If escalating a risk early damages a career, you will get silence. Measure PMs on how quickly and honestly they surface problems, not on how green they stay.
The fair objection
Critics will say this signals distrust, adds overhead, and creates a policing culture. They are partly right. Badly done, independent assurance becomes surveillance, breeds defensiveness and slows delivery. And not everything can be objectively measured; judgment will always remain. But consider the alternative: a culture where trust substitutes for verification, and where the first reliable data point arrives when the overrun is already unrecoverable. Independence isn’t an insult to project managers. It protects them from the pressure to be optimistic, and protects the organisation from learning the truth too late. But notice what the objection really defends: a system where verification is considered an insult. No surgeon feels insulted by an infection-rate audit. No CFO feels distrusted by external auditors. In every high-stakes profession, independent measurement is a sign of maturity, not suspicion.
The question for your next leadership meeting is If every PM status report vanished tomorrow, how would we know how our projects are really performing? If the answer is “we wouldn’t,” then you don’t have a performance system. You have a collection of self-assessments with a logo on them. This industry has been over budget and over time for decades, and we keep blaming weather, subcontractors and scope changes. Maybe the uncomfortable truth is simpler: We’ve been asking the people holding the pen to grade the exam.
Over to Readers :
I’ve given my position. I’d like to know where you disagree.
1] Who should the PMO report to in your organization, and who does it report to today? Is there a gap?
2] Can one function genuinely be both a delivery enabler and an independent assurer? Or is that a conflict we’ve simply learned to tolerate?
3] Have you ever seen a project turn red “suddenly”? Looking back, who knew first, and why didn’t it surface?
4] If your project managers’ status reports disappeared tomorrow, what would you use to know the truth?
5] Is independent assurance a sign of maturity or a symptom of low trust? Does it change delivery culture for better or worse?
6] How do you reward the PM who delivers bad news early in a system that rewards green dashboards?
Tell me where I’m wrong. Better still, tell me where you’ve seen it done right.