What happens when information becomes more reassuring as it moves up the organization.
Consider a project that is slipping behind schedule.
A supplier has missed a delivery. Testing is taking longer than expected. The team closest to the work knows that meeting the deadline now depends on almost everything else going right.
At the first management review, the delay is described as recoverable. At the next, the project remains on track, subject to a few dependencies. By the time the update reaches the executive committee, the warning has become a footnote.
Weeks later, the deadline is missed. Someone asks: Why were we not told?
The question assumes the warning never arrived. It may have arrived several times, each time in a form that made it easier to overlook.
Every organization must summarize. Executives cannot examine every project dependency, maintenance record, or customer complaint. They depend on managers to decide what deserves attention. The difficulty begins when those judgments become influenced by what the next person wants to hear.
A manager may believe the team can recover. Another may want stronger evidence before escalating. A third may see little reason to unsettle leadership over a problem that could still be resolved.
None of these judgments is necessarily unreasonable. Together, however, they can produce an account more confident than the evidence supports. The deadline stays fixed while the conditions required to meet it become increasingly improbable.
By the time the uncertainty becomes impossible to soften, some of the choices available earlier may have disappeared.
It is tempting to attribute this to weak managers or deliberate concealment. Sometimes that explanation fits. But information can lose its meaning without anyone consciously deciding to mislead.
People learn how to deliver difficult news by watching what happens when others do.
A manager reports a delay and spends the meeting defending the team’s competence. An analyst questions a forecast and is asked to find assumptions that support the original number. An employee raises a recurring concern, receives no response, and eventually stops mentioning it.
These experiences shape the next report. Qualifications become less prominent. Doubts are held back until they can be proved. Problems remain within the team a little longer, in the hope that they can be resolved before anyone senior needs to know.
Some silence comes from fear. Some comes from exhaustion. Some comes from an earnest desire to solve a problem rather than pass it upwards. From the executive chair, these different motives can produce the same misleading picture: little appears to require intervention.
The pressure intensifies when an unwelcome fact threatens someone’s standing. A project delay becomes a judgment on the project manager. A weakening business case calls an executive’s earlier decision into question. Reporting then carries a personal consequence alongside its business purpose.
This is why an invitation to “speak openly” can accomplish so little. Employees weigh those words against what they have seen rewarded, challenged, or ignored.
Leaders influence the quality of the next warning through their response to the current one. They can ask what has changed, how confident the team is, and what becomes harder if action is delayed. They can examine poor performance without treating the disclosure itself as evidence of failure. And they can explain what became of a concern, including why they decided to accept the risk.
These are ordinary exchanges, but they establish whether an honest account is useful to the person receiving it.
Reporting needs to preserve uncertainty too. A green status tells leadership very little if delivery depends on an unconfirmed shipment, untested equipment, or overtime the team cannot sustain. Those conditions belong in the assessment because they determine how much confidence the conclusion deserves.
The aim is to make a warning understandable while there is still time to consider it. A concern need not be a certainty to merit attention.
Some setbacks will remain unforeseeable. Others will look obvious only in hindsight. Leaders cannot be expected to anticipate every failure, and employees cannot escalate every doubt.
But when a known problem becomes an executive surprise, the review should follow what happened to the warning. Who first noticed it? How was it described? What changed as it moved through the organization? What response encouraged the next person to soften it, postpone it, or leave it out?
The missed deadline is the visible failure. Understanding how the warning lost its force may do more to prevent the next one.
What do you think?
This strategic reallocation of resources can help companies create a significant competitive advantage.