The green rating isn't the problem. The silence around it is.

A CEO said something to me recently that has stayed with me. He was describing his programme governance table, sponsors, business owners, the people whose job it is to hold delivery to account, and he said none of them seemed able to ask why everything in the report was green. He put it down to culture and a lack of knowledge, and he wasn't wrong. But that framing covers over how many distinct, very human reasons actually sit underneath it, reasons most people in that seat would probably recognise in themselves if they stopped to look.

They took the seat for reasons that had little to do with delivery

Governance and sponsor roles are still, in a lot of organisations, a marker of arrival. A seat at the table signals that you have been trusted with something bigger than your own patch, and it looks good on a CV. Corporate governance research on "overboarding," where directors take on more board seats than they can properly attend to, shows how easily this plays out even at the most senior level. Institutional investors have grown concerned enough about it that firms like BlackRock and Glass Lewis now vote against directors who sit on too many boards at once, and surveys of non-executive directors consistently find the role has become more demanding without a corresponding increase in the time anyone has set aside for it. The same dynamic runs quietly through internal governance forums. People accept the seat for what it signals about their standing, then arrive at the table without having read the report closely enough to know what to challenge.

Looking calm matters more than looking right

There is also a simpler, more human reason. Being the person who asks the hard question at the table costs something. It marks you out as the difficult one, the one who slows things down, when most leaders would rather be seen as steady, unflappable, easy to work with. That reputation is worth protecting, and staying quiet protects it far more reliably than speaking up does.

Raising it might mean owning it

Then there is the trap of not being the one directly in charge. Research on what is sometimes called the "voice bystander effect" found that people are less likely to flag a problem when they know others in the room have the same information, because the sense of responsibility gets shared out and diluted rather than landing on any one person. It draws on the much older finding by Darley and Latané that the more witnesses there are to a problem, the less any individual feels obliged to act. At a governance table this plays out as a quiet calculation: if I raise this, does it become mine to fix. Sponsors who are not close to delivery day to day often conclude, not unreasonably, that flagging a concern is the fastest way to inherit a programme they never asked to run.

Escalating bad news feels like admitting you can't lead

There is a fifth pressure, and it sits closer to the top of the reporting chain than the others. A sponsor or programme lead who escalates genuinely bad news is, in their own mind, also announcing that they have lost control of something they were trusted to run. Leadership is still widely equated with certainty, so admitting a programme is off track can feel less like transparency and more like a confession of inadequacy.

The research on this is old and consistent. What social psychologists call the MUM effect, first documented in the 1970s, describes a well established human tendency to delay or soften bad news relative to good news, regardless of the setting. In organisational hierarchies this hardens into something more specific: people shape what they tell their superiors not around what is true, but around what they believe their superiors want to hear, a pattern researchers have called upward distortion. The bias runs in a predictable direction. If a leader treats a miss as proof the team has lost its grip, the organisation quietly learns that confidence gets rewarded and candour gets punished, and every subsequent report gets written to the reward rather than the reality.

This is also where the sponsor's own anticipation of their stakeholders comes in. Most sponsors are not just reporting up, they are pre-empting what the person above them wants to see, softening the picture before anyone has even asked them to. By the time a status update has passed through two or three layers of this kind of anticipatory editing, calling it inaccurate understates what has happened. It has been rebuilt, one polite omission at a time, into a version of the truth that nobody at the table actually believes but nobody wants to be the one to contradict.

And even when they set the brief, they hedge it

The sharpest irony is what happens when the sponsor was the one commissioning the work in the first place. Being clear about what a good outcome looks like, and specific about what "on track" needs to mean, is the single most useful thing a sponsor can do. But clarity that detailed can feel like it tips into telling people how to do their jobs, and the fear of being seen as a micromanager runs deep in leadership research, showing up as a leading cause of leaders under-specifying what they actually need. So the brief stays loose, the reporting stays loose to match it, and by the time a status update lands on the table there is no shared definition of good against which to test it.

Underneath this sits a confusion between being nice and being kind. Kim Scott's work on candid feedback describes what happens when a leader cares about the relationship but avoids the direct challenge, sugar-coating a brief until it says nothing testable, and calls it what it is, a failure to be kind dressed up as consideration. Many sponsors genuinely believe this vagueness is what psychological safety looks like, that leaving room, staying soft, not pinning anything down too precisely, is what makes people feel safe to come to them with bad news. It is the opposite. Edmondson's own description of a psychologically safe team is one with a high tolerance for candour, not a high tolerance for ambiguity. A vague brief does not protect anyone. It just removes the one thing that would have let a sponsor tell, three months later, whether the answer they were being given was real.

What the theatre actually costs

Put five pressures together, status seeking, impression management, diffused responsibility, escalation fear, and a hedged brief, and what results is not really governance. It is governance theatre. The forum meets, the paper gets tabled, the status gets read out, everyone nods, and nothing that resembles insight, risk surface, or a real decision has actually taken place in the room. The structure is intact. The scrutiny it was built to provide is not.

That distinction matters because it tells you where the fix has to sit. This is not a PMO maturity problem, and it is not generic culture work. It is specifically about the oversight layer, the people whose job is to give the organisation confidence that delivery is real, value is still on track, and risk is being held within appetite. Strengthening that layer takes four moves, not one.

A quick diagnostic

Before building anything, it is worth looking honestly at four things in the room as it currently operates. Are the papers written around decisions the forum needs to make, or are they activity diaries dressed up as status reports. When a rating gets challenged, does that happen often, rarely, or effectively never. Do the minutes show genuine debate, or do they show agreement reached in minutes on items that took months to prepare. And do the people in the room have enough working knowledge of what "under the hood" should look like to know when an answer is a real answer rather than a well delivered deflection. Most of the gap becomes visible within a single cycle of watching for these four things.

Then, four moves

Reset role clarity. Write down, specifically, what a sponsor or business owner in this seat owns, what evidence they are entitled to demand before they sign off a rating, and which decisions only they are allowed to make. Most role gaps are not about capability. They are about nobody ever having said this out loud.

Build the questioning skill deliberately. This is learnable and specific, not a personality trait some people happen to have. A working question bank, practice at red-teaming a status report before it reaches the table, and rehearsal through simulated governance meetings will do more for scrutiny than any dashboard redesign.

Make challenge a duty, not a personality trait. Say explicitly that surfacing a hard truth is part of the job description for a governance seat, and be visibly consistent when someone does it, so the first person who tries it is not left wondering whether they just made a mistake.

Change the paper standard, lightly. Shift status reports from recording activity to demanding evidence, require that a green rating carry the leading indicators that justify it, and make status something that has to be earned and defended rather than simply declared.

None of this is solved by better dashboards on their own. Boards and programme sponsors have had increasingly detailed templates for years, and the overruns have continued regardless. What actually closes the gap is the combination, people equipped with the specific skill of interrogating status information, roles that are unambiguous about what they are accountable for verifying, and a culture that treats a hard question as evidence the governance is working rather than evidence something has gone wrong.

The CEO I spoke with had already sensed most of this, before I ever pointed him to the research behind it. Most organisations have some version of that same sense too, a nagging feeling that the green isn't quite telling the whole story. What stops them acting on it is not usually a lack of instinct. It is the same handful of pressures this piece has walked through, the need to look calm, the fear of inheriting someone else's problem, the reflex to soften bad news, the reluctance to pin down what good actually looks like. Sensing something is off and being willing to say so out loud in that room are two very different things.

A cheat sheet for the next status report

Twelve questions, grouped by what they are actually testing.

On the status itself

1. What specific evidence sits behind each green rating, the leading indicators, not just the activities that have been completed?
2. What would have to change for this status to move, and is anyone actively watching for it?

On assumptions and risk

1. What is the single biggest assumption this programme is currently resting on, and how is it being tested or monitored?
2. Are there risks currently marked "managed" that still sit outside our agreed risk appetite?
3. If this programme were to fail or fall well short, what would most likely be the cause, and how visible is that cause in what we're looking at today?

On outcomes and value

1. How do we know work marked complete is actually delivering usable value, not just clearing a milestone?
2. What's been quietly descoped or deprioritised that hasn't come to us as a reported change?

On decisions and candour

1. What decision do you actually need from this forum in the next 30 to 60 days, and what does delaying it cost?
2. What would you tell me right now if you knew I wouldn't read it as you having failed?
3. Has anything in this report been softened because of what you thought we wanted to hear?

Reality check

1. What do the people closest to the work believe, away from the version that's been prepared for this room?
2. What's one thing in this report that looks better on paper than it feels in reality?