The Dashboard Is Green. The Project Is Red.

There is a particular kind of problem that sounds like a technology problem but is actually a communication problem. You can throw all the tools you want at it and nothing will change.

I have been in organisations that had excellent project management software, detailed status dashboards, automated reporting, real-time collaboration tools — and still consistently delivered late, still had teams working at cross purposes, still surprised leadership with problems that had been visible for weeks.

The tools were not the problem. The tools were actually working perfectly. They were faithfully recording a communication problem that nobody was addressing.

The pattern goes like this: a team has a problem sharing bad news upward. This is almost universal and almost never talked about directly. So instead of surfacing the problem early, people update the dashboard optimistically, attend the status meeting and say things are fine, and quietly hope the situation resolves itself before the next milestone.

The dashboard shows green. The project is red. The gap between those two things is a culture problem, not a software problem.

The fix is not better tooling. The fix is making it psychologically safe to say “we are behind” before it becomes “we have failed.” That requires leaders to consistently reward early honesty and consistently not shoot the messenger. It is simple. It is hard. No software helps.

Before you buy the next tool, it is worth asking whether the problem you are trying to solve is actually a data problem or whether it is a conversation that nobody wants to have. This is something Greg Hay explores in his advisory work, and it is part of the thinking behind Claritam — which is built on the premise that honest, automated data is a precondition for honest conversations.

Why Bad News Does Not Travel Up

The gap between dashboard green and project red is not a data problem. It is a fear problem. People at every level of an organisation learn, usually through experience, that delivering bad news has personal consequences. The messenger gets questioned, the messenger gets extra scrutiny, the messenger gets remembered as the person who raised the alarm even when the alarm was justified. Over time, people learn to optimise the dashboard instead of optimising the project.

This is not malice. It is a rational response to an incentive structure that punishes honesty. The project manager who reports a two-week delay in week two is technically correct and professionally exposed. The one who reports it in week six, when the delay has grown to four weeks and is now unavoidable, has at least bought themselves time. The system rewards the second behaviour. The dashboard stays green until it cannot, and by then the project is in trouble.

The Compounding Cost of Late Honesty

When bad news arrives late, the options have narrowed. A two-week delay caught early can often be absorbed by reallocating resources or adjusting scope. A two-month delay discovered at the last milestone cannot. The organisation loses the ability to respond because the response time was spent maintaining the appearance of control. This is one reason digital transformation projects fail so consistently — the dashboard shows green while the adoption numbers tell a different story, and by the time leadership notices, the project is too far gone to rescue.

The cost is not just financial. Late honesty erodes trust. When leadership discovers that problems were visible for weeks before they were reported, the next response is to demand more reporting, more oversight, more layers of verification. The organisation gets heavier. The cycle reinforces itself.

What Leaders Can Actually Do

The fix is not a new tool. It is a change in what leaders reward. When someone brings bad news early, the leader’s response in that moment determines whether it will happen again. A leader who thanks the messenger, asks what support they need, and treats the early warning as a sign of competence will get more early warnings. A leader who questions the judgment, asks why it was not caught sooner, or implies disappointment will get fewer. The behaviour that gets rewarded is the behaviour that repeats.

This is simple to describe and hard to execute, because the leader who receives bad news is under pressure too. The instinct to question is natural. The discipline to thank is learned. The organisations that build this discipline are the ones where the dashboard and the project eventually agree. The same principle applies to meetings that should have been decisions — the culture that avoids hard conversations in one place avoids them everywhere.

The organisations that break this cycle are the ones where leadership explicitly asks for bad news. Where the question at a status review is not “are we on track” but “what is the thing most likely to go wrong.” Where the person who raises a problem early is thanked, not questioned. These organisations do not have better dashboards. They have better cultures. And the dashboards eventually reflect that.