Week 46 Day 3: Do You Feel Safe Bringing Me Bad News?

The leader who does not hear bad news is not leading a team without problems. They are leading a team that has learned to hide problems. The problems still exist. They just grow in the dark until they become crises that can no longer be hidden. By then, your options for response are dramatically narrower than they would have been if you had heard the bad news early.

Here is how to diagnose and repair a 'no' on this question. The diagnosis: if your team scored low on this question, the cause is almost always your past behavior, not your stated policy. You may have said 'bring me bad news early.' But at some point, you reacted to bad news in a way that taught the team it was not safe. Maybe you became visibly frustrated. Maybe you asked 'how did this happen?' in a tone that sounded like blame rather than curiosity. Maybe you escalated the issue in a way that exposed the messenger. You may not even remember the incident. The team remembers. The repair process has four stages. Stage one -- acknowledge the gap publicly: 'I asked whether you feel safe bringing me bad news, and the honest answer is that many of you do not. I take responsibility for that. I have not consistently created the conditions for safe reporting, and I want to change that.' Stage two -- identify the specific behavior to change: ask a trusted team member (or gather from the anonymous audit) what specific behavior makes reporting feel unsafe. Is it your facial expression? Your tone? Your tendency to immediately ask who was responsible? Your habit of escalating issues to your manager before the team has a chance to resolve them? The specific behavior is the repair target. Stage three -- implement a new protocol: 'When you bring me bad news, here is what will happen. I will say thank you. I will ask what you think we should do about it. I will help you solve it. I will not ask who caused it unless understanding the cause is necessary for the fix. I will not escalate it without telling you first.' Stage four -- demonstrate the new behavior visibly: the next time bad news arrives, follow the protocol publicly. The team is watching. One correct demonstration is worth a thousand policy statements. Then do it again. And again. The repair is not a one-time event -- it is a pattern that replaces the previous pattern. Expect it to take 8-12 weeks of consistent new behavior before the team's trust level measurably shifts. Trust erodes fast and rebuilds slowly.

The 'shooting the messenger' phenomenon is documented by Rosen and Tesser (1970) in their research on 'the reluctance to transmit bad news' (the MUM effect), which found that individuals systematically distort, delay, or withhold negative information from authority figures, and that this tendency increases when the authority figure has previously reacted negatively to bad news. The 8-12 week repair timeline is consistent with what Kim, Dirks, Cooper, and Ferrin (2006) call 'trust repair after violation,' their experimental research demonstrating that trust recovery after a behavioral violation requires sustained counter-evidence (repeated demonstrations of the new behavior) over a period of 2-3 months before the trustor's expectations update. Importantly, they found that a single violation can undo months of trust-building (consistent with the asymmetry principle from Slovic, 1993, discussed in Week 45), which explains why the repair period is longer than the violation period. The public acknowledgment (Stage one) implements what Tomlinson, Dineen, and Lewicki (2004) call 'attributional trust repair' -- their research found that trust repair is most effective when the violator publicly acknowledges the violation, attributes it to their own behavior (internal attribution) rather than to circumstances (external attribution), and commits to specific behavioral change. Internal attribution was critical: leaders who acknowledged 'I created this problem through my behavior' repaired trust significantly faster than leaders who acknowledged the problem but attributed it to organizational factors or team dynamics.