Status reports can tell whatever you want them to, but facts always hold their own.

— #ProjectManagementTweet, Himanshu Jhamb & Guy Ralfe (2010)

So how does a multi-million-dollar project go from “on track” to “behind” overnight, when the status report has said Green for the past six months?

It isn’t overnight. It’s never overnight. What actually happened is that the gap between the report and the reality had been quietly widening for months, and nobody wanted to be the one who said so out loud.

I’ve written about a cousin of this problem before: the trap of calling something “90% done” when the word “done” means something different to whoever’s saying it. This is the same instinct wearing a different mask, just not a disagreement about definitions this time. It’s a reluctance to report the truth at all.

Some of it is simple human nature: what psychologists sometimes call impression management, the pull to control how you’re seen rather than say plainly what’s happening. Some of it is entirely rational fear. Flag something amber, and you don’t get help; you get more meetings, more reports, more scrutiny. The very thing you were trying to avoid by staying quiet in the first place.

So what do you actually do about it?

The Meeting

Not long ago, I sat as one of eighteen people on a weekly status call for a multi-million-dollar, high-visibility client programme I was ultimately accountable for delivering. It was the kind of programme where the client’s own leadership was watching closely, and where the pressure to look composed in front of them never really let up. For the better part of six months, the PMO team’s weekly deck told a good story: mostly green, the occasional amber, a confident narrative about progress made. That was the entire first half of (more or less) every call.

Then we’d get to risks and issues (the part of the meeting that actually mattered), and week after week, we’d start running out of time before we finished. We weren’t ending calls because the discussion was complete. We were ending them because the clock had run out. Busy executives dropped off the line without knowing what, if anything, was expected of them before the next one.

The Question

I pulled the PMO team into a private room and asked them one question: what is a status meeting with executives actually for? The first answers were the ones you’d expect: “so they know where things stand,” “so they have something to report to their own stakeholders.” Then one person said something that quieted the room: “So they know what they need to do to unblock us and keep things moving.”

That was it. Underneath every polite nod on that call, that’s what every executive was actually asking: Are we on track? What’s in the way? And what do you need from me?

The Turn

We rebuilt the meeting around that answer. Five minutes at the top for a genuine executive summary of where things stood, no embellishment and no spin, and then straight into whatever actually needed an executive’s hand to move: a decision, an escalation, a resourcing call, an introduction to someone outside the room. The status meeting became an action meeting. Executives stopped leaving early, because for the first time the second half of the call was about them, not about us.

We hit the delivery date. The programme was held up afterward, internally, as one of the better outcomes the organization delivered that year.

What I Took Away

The tweet holds because it’s not really about dishonesty. A status report can tell whatever story the room is willing to hear — but the facts underneath it don’t change to match, and eventually they surface, usually at the worst possible time. Our dashboard didn’t lie because the numbers were wrong. It lied because the meeting around it had no room for the truth to surface.

In today’s fast-moving digitalization environment, where vendor-heavy delivery models and highly visible flagship programmes are the norm, this pattern shows up constantly. Teams protect the narrative because raising a flag early feels more expensive, in the moment, than raising it late, even though it never actually is.

So the next time something like this happens on your own programme, the question worth asking isn’t whether you need a better dashboard. It’s whether your meeting is structured to reward the truth or just to manage how things look. Underneath that sits a harder question: does your organization’s culture reward the people who speak up early, or is there a quiet fear that keeps everyone managing appearances instead?

This is exactly the trap teams are walking into with AI right now. Plenty of programmes are automating status reporting (pulling straight from Jira, git commits, and ticket ages instead of asking a PM to narrate it) and treating that as the fix. It can genuinely help; a model has no stake in how it looks in front of the client’s leadership. But it only removes the impression-management problem if the meeting built around it still makes room for the uncomfortable data. An AI-generated dashboard nobody has time to actually discuss is just a faster way to stay Green.

The organizations that catch this early don’t have better dashboards. They’ve built a culture where flagging a problem gets you help, not more scrutiny — and the meeting is just where that culture shows up, week after week. We didn’t fix ours by changing what we measured. We fixed it by changing what the meeting was for. If your status calls keep running out of time before you finish covering the risks, and executives are leaving without knowing what you need from them, what would it take to flip the agenda?