Mum Effect

Most leadership teams say they want candor. Yet many organizations still deliver bad news late, softened and stripped of the detail needed to act. A product launch remains "on track" until the final milestone fails. A key customer concern appears as a minor account issue until renewal is already at risk. A program reports green status while the people closest to the work quietly know that a dependency has failed. These patterns are not always signs of dishonesty. They often reflect the Mum Effect:

a reluctance to communicate information that will be unwelcome for the recipient

What the Mum Effect explains

The Mum Effect describes a well-established tendency to hesitate more when sharing bad news than when sharing good news. The Wiley encyclopedia entry defines it as a messenger's hesitation to share bad news, relative to good news, with a recipient for whom the news is negative 1 . The term captures more than silence. People can delay a message, dilute its implications, emphasize uncertainty, use euphemisms, or lead with positive details until the central problem becomes difficult to recognize.

In an organization, the effect creates information asymmetry between the people nearest to a problem and the people responsible for allocating resources or changing direction. Frontline staff see the failed handoff, customer frustration, or technical constraint first. By the time that fact reaches an executive forum, several layers of interpretation may have transformed it into a manageable-looking variance. The organization then loses time, which is often the most valuable resource in a deteriorating situation.

The effect is not irrational at an individual level. Delivering bad news can damage a relationship, create discomfort, or cause the messenger to be linked with the event. Research on face concerns finds that people may hesitate because they fear distressing the recipient or want to avoid the negative emotional state associated with communicating the message 2 . The leadership problem begins when a reasonable human tendency becomes an unchallenged organizational routine.

How hierarchy amplifies silence

Hierarchy changes the cost of speaking. The person carrying bad news upward usually has less power than the recipient and may depend on that recipient for resources, evaluation, promotion, or protection. The message can therefore feel like a personal threat even when it concerns an external event. A delayed shipment becomes "my failure to manage the supplier." A deteriorating customer relationship becomes "my inability to retain the account." The messenger anticipates not only the news but also the recipient's interpretation of the messenger.

This is the hierarchical Mum Effect. Research on employees' failure to report negative events to managers defines it as subordinates purposefully withholding information or sharing it in a way that silences the dirty details of a situation 3 . That distinction is crucial. Senior leaders may believe they are receiving updates, while the organization is actually passing upward a version of reality optimized for acceptability rather than action.

The risk rises in environments that equate leadership with certainty. If a manager treats bad news as evidence that the team lacks control, people learn to present control. If a board punishes every miss without distinguishing forecast quality from execution quality, executives learn to delay revisions. If status meetings reward confidence, teams will bring confidence. The system produces the behavior it appears to condemn.

Where the effect damages performance

Projects are a visible setting for the Mum Effect because schedules, dependencies and milestones make deterioration easy to mask for a time. A team may report that a risk is "being managed" because the more accurate statement, "the plan no longer works", would trigger uncomfortable questions. Research on software projects identifies reluctance to report the exact position of troubled projects as a major contributor to failure, because delayed disclosure narrows the range of available interventions 4 .

Commercial organizations experience the same pattern in sales forecasts and customer health reporting. A declining account can remain in an optimistic pipeline category because the account team hopes for recovery and fears being seen as ineffective. Product teams can keep a feature in scope because admitting that users do not value it feels like abandoning prior investment. Operations teams can understate capacity constraints because the visible consequence of escalation is often additional scrutiny before it is additional help.

The cumulative cost is high. Leadership makes capital, staffing and sequencing decisions from reports that understate risk. Problems that could have been solved through a small intervention become expensive rescues. The organization later describes the outcome as a surprise, even though several people had observed early indicators. The surprise was not a lack of information. It was a failure of transmission.

Why requests for candor fail

A chief executive can say, "Bring me bad news early" and still receive it late. The statement only works if employees have evidence that the leader's behavior matches the invitation. People watch what happens to the last messenger. Did the executive ask questions, help remove barriers and distinguish facts from blame? Or did the meeting turn into a cross-examination, a public ranking of competence, or a demand for certainty that no one could provide?

The original experimental work on the Mum Effect found that good news was communicated more fully and spontaneously than bad news and it also found greater variability in willingness and obligation to transmit bad messages, suggesting ambiguity about the norms that govern bad-news communication 5 . Organizations need to remove that ambiguity. Vague encouragement leaves people to infer the real rule from incentives, hierarchy and past reactions.

Candor also fails when leaders confuse transparency with raw volume. Employees may disclose every small concern and still avoid the few messages that carry personal or political risk. The goal is not indiscriminate escalation. It is timely, evidence-based escalation of material deviations, paired with a clear decision request. That requires a common language for what counts as material and who needs to know.

Build mechanisms for early truth

The practical answer is to make the transmission of bad news an expected operating process. Teams need predetermined triggers that convert a potential social judgment into a routine procedural step. A project that crosses a cost, timeline, quality, or customer-impact threshold should automatically enter a review pathway. The messenger should not have to decide whether the issue is serious enough to raise, especially when the act of raising it may expose the messenger to blame.

A strong system uses several linked practices.

1. Define escalation thresholds before delivery begins, including schedule slippage, forecast variance, control failures, customer impact and safety or compliance signals
2. Require red-and-amber status reports to state the evidence, the current forecast, the decision needed and the owner of the next action
3. Track forecast accuracy over time so that teams receive credit for early revision rather than only for reporting good outcomes
4. Separate problem diagnosis from performance evaluation in the first escalation conversation
5. Use independent reviews or pre-mortems to surface risks that teams may feel unable to raise directly

These mechanisms do not remove interpersonal discomfort. They reduce its influence on whether critical information moves. When the procedure requires escalation, the messenger can say, "The threshold was crossed", instead of feeling personally responsible for disrupting a narrative of progress.

Make leaders safe recipients

The recipient's response determines whether the next message arrives sooner or later. Leaders should treat early bad news as a form of organizational value, even when the underlying event is disappointing. The first response should establish facts and choices:

What changed? What evidence supports the revised view? What is the likely impact if no action is taken? What decision, resource, or cross-functional intervention is now needed? Those questions signal that the meeting is about resolving the issue, not finding a culprit

A leader can still demand accountability. The sequence matters. Diagnose before judging. Separate a preventable execution error from a signal that emerged despite reasonable controls. Ask whether the team escalated as soon as the evidence met the agreed threshold. If it did, reinforce that behavior even while addressing the cause of the failure. That distinction teaches the organization that reporting a problem and creating a problem are not the same act.

Leaders also need to model disclosure. When executives explain a decision that did not work, name the assumptions that failed and describe the corrective action without theatrical self-protection, they lower the social cost of candor for everyone else. That behavior creates a more credible invitation than any values statement.

Measure the speed of truth

Organizations measure revenue, quality, delivery and employee engagement. They should also measure how quickly material negative information reaches the people who can act. Useful indicators include time from first signal to escalation, the gap between initial forecast and final outcome, the share of risks identified by independent review rather than the operating team and the frequency with which issues move directly from green to critical without an intervening warning.

None of these metrics should become a new compliance theater. Their purpose is diagnostic. A long delay between an early signal and executive awareness may indicate unclear thresholds, poor cross-functional trust, or a leader who punishes bad news. A pattern of sudden red status may mean that teams lack permission to use amber honestly. A reliable stream of early warnings, followed by rapid decisions, is a sign that the organization is learning before it is forced to react.

The Mum Effect cannot be eliminated because people will always anticipate the emotional and political consequences of delivering unwelcome information. It can, however, be managed. Leaders who design escalation mechanisms, respond constructively and reward accurate early signals shrink their blind spots. They create an organization where bad news travels fast enough to remain useful.

• 1MUM Effect, The
• 2Breaking good and bad news: face-implicating concerns as mediating the relationship between news valence and hesitation to share the news
• 3Can we talk? Why employees fail to report negative events to their managers
• 4A framework to manage reluctance to bad news reporting on software projects
• 5Some message variables and the Mum Effect