Why good boards love bad news early

Every board says it wants to hear bad news. Fewer behave in a way that makes it likely.

Bad news that arrives early is an asset. It keeps options open: there is still time to change supplier, add resource, re-plan, or tell customers before they hear it elsewhere. The same news six weeks later is a crisis, with fewer choices and a larger bill.

So the question for a board is not whether bad news exists. In any organisation doing anything worthwhile, it does. The question is how long it takes to reach the people who can act on it.

What slows it down

Bad news rarely hides because people are dishonest. It slows down for ordinary reasons:
- the person who spots it is not sure it is their place to raise it;
- the last person who raised something was made to feel responsible for it;
- reports are designed to show status, not uncertainty, so everything is green until it is suddenly red;
- meetings reward confident updates over honest ones.

That last point deserves attention. A meeting where every update is met with nods and no questions should worry a board more than one with awkward pauses and difficult follow-ups. A transformation update that prompts no curiosity is not reassurance. It is a sign that the real conversation is happening somewhere else.

Policy is not the same as practice

One of the most common gaps I find is between what a control says and what it does. In one review I carried out, an organisation's multi-factor authentication policy was in place and looked correct. It had been set up eighteen months earlier, and everyone assumed it was working. When we checked, only 8 of 22 users had registered to use it. The report said "enabled". In practice, most accounts were protected by a password alone.

Nobody had hidden anything. Nobody had looked. The bad news had existed for eighteen months; it simply had no route to the surface.

What boards can do

Boards cannot manufacture candour, but they can make it cheaper to offer:
- Thank people for early escalation, visibly, including when the issue turns out to be smaller than feared.
- Separate learning reviews from blame. If every incident review ends with a name, the next incident will be reported later.
- Ask for the amber, not just the red. "What are you least confident about?" is a better question than "Is this on track?"
- Ask for evidence, not assurances. "How do we know?" may be the most useful question a board can ask.
- Measure time to surface. When an issue emerges, ask when it was first noticed and how long it took to reach the board, and track whether that gap is shrinking.

The aim

The goal is not zero surprises. That is not achievable, and a board that demands it will simply receive fewer honest reports. The goal is zero late surprises.

Candour is the ultimate control. Every other control depends on someone being willing to say it is not working.