Why bad news fails to reach the boss

How risk disappears during a status update

A specialist tells the manager that the deadline is unrealistic without an additional team member. The manager tells the director that the team is having a difficult week but is working on a solution. The director reports that the project needs attention. By the time the message reaches the top, the situation still appears manageable. Nobody needed to lie deliberately. Each person may simply have softened the wording to avoid sounding alarmist or escalating a problem before trying to solve it. The MUM effect describes people's reluctance to communicate unwelcome news. At work, it may interact with hierarchy and concern for one's reputation. It is narrower than employee silence in general, which also includes withholding ideas, feedback, or objections. The distinction matters: sometimes the information is never voiced; at other times it is conveyed so cautiously that the recipient fails to recognize its importance. Every level may add assumptions about what the next recipient wants to hear. The manager believes the director expects a ready-made solution, while the director assumes that the board wants only a bottom-line status. The conditions and uncertainties most relevant to the decision then disappear from the message. It is worth asking whether the reporting process allows people to say, “We don't yet know, but a decision may soon be necessary.” If only reassuring, definitive messages are acceptable, the organization may receive an increasingly polished account that becomes progressively less useful for managing the actual risk.

What makes the messenger's role difficult

Lee examined the transmission of bad news through organizational hierarchies, while Milliken, Morrison, and Hewlin investigated why employees remain silent about workplace concerns. This research helps explain fears of negative evaluation and an adverse response from others. It does not mean that every delayed warning is caused by fear of the manager; uncertainty about the evidence or the absence of a clear recipient may also be responsible. Lee, 1993; Milliken et al., 2003 An employee may think, “If I report this now, it will look as though I can't handle the task.” A manager may fear that escalating the risk will damage the reputation of the entire department. The problem is often not yet certain: the deadline is at risk but has not slipped; the client is dissatisfied but has not ended the contract. That is precisely when the information may be most useful—and easiest to postpone until greater certainty arrives.

The first response becomes a lesson for the future

If a manager answers a warning with sarcasm or a public “How could you let this happen?”, people remember the cost of being the messenger. Later declarations of openness may not erase that experience. A calm first response allows the facts to be established before blame is considered. It does not require praising every alarm or abandoning accountability; it means that reporting a risk is not itself treated as misconduct. A useful response might be: “Thank you for raising this. What do we know, what remains uncertain, and when will a decision be needed?” The causes and the management of the work can be examined afterwards. If there has been negligence, it can be addressed on the basis of established facts. Combining all these conversations at the instant of the first warning obstructs the flow of information: the messenger starts building a defense instead of explaining the situation. Leaders should also distinguish challenging a claim from verifying it. Asking for evidence, sources, and alternative explanations need not imply that the employee is exaggerating or making excuses. The wording matters particularly when the signal is incomplete. If every early warning must immediately be proven beyond doubt, people will wait too long. The required level of certainty should fit the stage of the issue. A suspicion and a confirmed problem are reported differently, but both can be valuable when their status is explicit. This preserves rigor without demanding knowledge that nobody yet possesses.

Do not demand a complete solution with every warning

“Bring solutions, not problems” can encourage initiative, but applying it without exception delays important warnings. A specialist may recognize a threat without having the authority or resources to remove it. In the deadline example, the decision to assign another person belongs to the manager. Requiring the employee to solve the difficulty before reporting it traps the information below the level at which action can be taken. A team can agree reporting thresholds: what degree of delay, quality risk, or dependency requires prompt notice? It can also define a minimum information set: the observation, possible consequence, level of certainty, and decision required. This format conveys uncertainty without diluting the meaning. “There is a risk of a two-week delay unless we secure support by Friday” tells the recipient far more than “We're working through some challenges.”

Check whether the message loses urgency along the way

In a hierarchy, compare the summary with the original warning. Is the condition required to meet the deadline still visible? Has the stated level of certainty changed? Does the decision-maker know when action will be needed? The aim is not to bypass every management layer but to preserve decision-relevant information. A summary should shorten the message, not improve its mood. Where appropriate, the person who raised the concern can confirm that its meaning has survived. Leaders should also close the communication loop. If an employee repeatedly reports risks but never learns what happened next, they may conclude that speaking up is pointless. A brief update—whether a decision was made, deferred, or requires more data—shows that the signal reached an accountable recipient. Over time, people can learn which reports are useful without creating a culture in which the preferred good news is simply the absence of bad news. Review whether the status system rewards maintaining a positive image of a project for too long. If marking a project as “at risk” is treated as a manager's personal failure, the warning may be delayed until the final moment. It is more useful to treat status as information needed for a decision: what has to happen to reduce the risk, and who can influence that condition? Appropriate early warnings also deserve recognition when timely action prevents the feared outcome. The fact that no failure occurred does not prove that the alert was unnecessary; sometimes the warning is exactly what made prevention possible. Organizations should learn from those cases too, rather than valuing only dramatic crisis recovery.

Bad news is often delayed or softened before it reaches someone with the authority to act. Effective risk communication requires clear reporting rules and a predictable response from the recipient. The most valuable warning often arrives while the outcome is still uncertain but there is still time to change it.

Using Empatyzer to communicate difficult information

Empatyzer can help you prepare both a risk message and the response to it. In Talk to Em about a specific person, you can structure a message around the observation, possible impact, level of certainty, and decision required. An available profile of the recipient may help you choose an appropriate form, but it should never be used to soften the facts until their significance is lost. A manager can use Talk to Em about yourself to prepare an initial response that gathers information before assessing responsibility. It can also help plan how to close the communication loop so that the person who raised the concern knows what happened next. Empatyzer does not monitor the project or detect delays automatically; the data must come from the people responsible for the work. The tool supports communication, while setting reporting thresholds, providing resources, and deciding how to respond to risk remain the responsibility of the organization and its leaders.