A Green Status Doesn’t Mean the Project Is Healthy
I have seen plenty of projects reporting green that were anything but healthy.
The dashboard looked fine. The milestones were green. The commentary was reassuring.
But underneath it, decisions were slipping, risks were building, suppliers were struggling or the team was starting to lose confidence in the plan.
That is the problem with project reporting.
It can become performative.
And project reporting is not performative art.
Its job is not to make the project look good. Its job is to tell people what is actually happening.
A project can stay green for quite a long time if nobody looks too closely.
No milestone has technically been missed yet.
The supplier says they can recover.
The decision is expected next week.
The target date has not moved.
So the status stays green.
But that does not necessarily mean the project is healthy. It may just mean the consequences have not arrived yet.
After many years working on projects and programmes, I pay far more attention to what sits behind the colour than the colour itself.
If a project is green, I want to know why.
Are the dates still credible?
Are key decisions being made?
Are risks increasing?
Are suppliers actually delivering?
Is the team relying on future recovery to make the plan work?
Those questions usually tell you far more than the RAG status.
Most projects do not suddenly become red.
They deteriorate gradually.
A decision slips. Then another one. A supplier loses some time. Testing gets squeezed. Contingency starts to disappear.
Nobody wants to overreact, so the project stays green.
Then, eventually, it becomes impossible to ignore and the status suddenly changes.
Except it was not really sudden.
The warning signs were there.
The reporting just did not show them clearly enough.
That is why good reporting matters.
Not because senior management needs another dashboard.
Because good reporting gives people time to act while they still have choices.
One question I like is:
What needs to be true four weeks from now for this project still to be green?
If the answer depends on several optimistic assumptions, a supplier recovering lost time and a couple of decisions being made quickly, then the project may not be as green as it looks.
This is also where experience helps.
You start to recognise the language that often appears when a project is beginning to wobble.
“We should be fine.”
“We can make the time up later.”
“The supplier has a recovery plan.”
“We haven't actually missed the milestone yet.”
None of those statements automatically means there is a problem.
But they are usually a reason to look a bit deeper.
Sometimes teams are simply too close to the project to see the overall picture.
That is where an independent review can help.
My No Fluff Project Assessment looks beyond the headline status and tests whether the project really has the clarity, control, planning and governance needed to deliver.
Sometimes the conclusion is that things are broadly under control.
Sometimes it finds issues that need attention before they become bigger problems.
Either way, that is what reporting should be doing in the first place.
Helping you understand reality.
Not decorating it.
You can find out more here:
The No Fluff takeaway
A green status does not mean the project is healthy.
It means somebody has decided to colour it green.
The important question is whether the evidence supports it.
Because the value of project reporting is not how good the dashboard looks.
It is whether it helps you spot trouble early enough to do something about it.
Comments