We have sat through program review meetings like this many times. It is rarely talked about directly. At best, it shows up as an eye-roll or a knowing look across the table. Then a quiet comment afterwards: “Well… we all know where that’s heading.” A list of corrective actions is agreed – and just as quietly, discounted.

The papers are well prepared. The slides are clean. The dashboard is green. On the surface, everything looks as it should. And yet, within a few minutes, you know. You have seen this before.

Not because anything has been said outright, but because the tone is off. The answers are technically correct, but not convincing. The detail is there, but it does not quite join up. The people closest to the work carry a tension that does not match what is being presented.

This shows up on almost every major program.

What sits underneath is usually straightforward. A dependency will not land when it needs to, because the work it relies on is not ready. A supplier is behind, whatever the status report says. The migration path only works if several things go right at the same time – and they will not. The team is stretched, and there is no real capacity left.

None of this is hidden. It is visible in the work, understood by the people doing it, and discussed openly where delivery is real – before the meeting, after the meeting, and in conversations where people speak plainly. But it does not appear in the report.

From that point on, the meeting takes on a familiar rhythm. The same issues are present, but they are described in a way that allows them to be acknowledged without forcing any action. What changes is the language.

A dependency that will not land becomes “still maturing.” A supplier that is behind becomes “working through complexity.” A migration path that does not work becomes “being refined.” A team with no capacity becomes “a little stretched.” Everyone in the room understands what this means.

This is where it matters.

Saying it plainly creates confrontation. Most people will go a long way to avoid that, even when they know it is in the best interests of the program.

No one wants to have an argument if they can avoid it. But sometimes it is inevitable.

Because once it is said plainly, the room changes. Decisions have to be made. Positions become visible. Accountability becomes personal.

So the issue is not stated unambiguously. It is described carefully enough to be recognised, but not clearly enough to force a response.

And that is the problem.

A response is what is needed. Leaving it hanging – understood but unaddressed – is how programs drift, then slip, then spiral.

The meeting moves on. The report reflects a version that can be lived with. The program continues – outwardly intact, but internally compensating.

This is not a data problem. The information is there. The difficulty is not understanding. The difficulty is saying it in a way that forces something to change.

What is missing is the moment where someone with enough weight and independence says, clearly and early, what the room already knows. Because once it is said plainly, something has to give – and that is precisely the moment many programs try to avoid.

Instead, they wait. For more evidence. Cleaner data. Something that feels indisputable. By the time that threshold is reached, the window to act has narrowed. The options are fewer, more expensive, and more disruptive.

So the program carries on in this suspended state. Reality is understood but never formally acknowledged. Reporting reflects what can be said, rather than what is known.

And it always ends the same way.

Programs do not miss the mark because they lack insight. They fail because they delay facing the truth – and acting on what they already know.

In too many cases, that delay is enabled. Euphemisms are tolerated. Ambiguity is allowed to stand. Language drifts just far enough from reality to avoid forcing action.

Everyone understands exactly what is meant. And still nothing changes.

Everyone understands exactly what is meant. And still – no one says it.

That’s how programs grind to a halt.

About the author

David Hilliard is founder of Mentor, specialists in strategic program execution.

You can call him on 0118 359 2444 or email david.hilliard@mentoreurope.com.