Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Manage a Boss Who Hates Bad News
Transcript
- Luna: So Lucas, we've talked a lot about bosses who are manipulative or absent or credit-stealing. But there's one type that might actually be the most dangerous in a quiet way — the boss who punishes the messenger. Lucas: Yeah, the 'shoot the messenger' boss. And I think people underestimate how costly that dynamic is, because it doesn't just hurt your feelings — it breaks the information chain inside the organization. When people stop bringing bad news upward, small problems become disasters. Luna: There's actually a textbook example of that. The Challenger disaster in 1986. Lucas: Exactly. That's the case I wanted to anchor this episode on. For listeners who don't know the full story — on January 28, 1986, the Space Shuttle Challenger exploded seventy-three seconds after launch, killing all seven crew members. The direct cause was an O-ring failure in one of the solid rocket boosters. But the deeper cause — the organizational cause — was that engineers at Morton Thiokol, the contractor that built the boosters, had tried to raise the issue the night before. Luna: And their boss, essentially, didn't want to hear it. Lucas: Right. The key figure is an engineer named Roger Boisjoly. He and a few colleagues had identified a serious flaw: the O-rings lost their seal at low temperatures. The night before the launch, temperatures were forecast to be well below freezing. Boisjoly and his team presented their data to management, arguing that the launch should be delayed. And initially, they got some traction — Thiokol's management recommended against launch. Luna: But then NASA pushed back. Lucas: Yeah, NASA's management was under pressure. The launch had already been delayed multiple times, and there was political visibility — President Reagan was going to mention the Challenger in the State of the Union address. So NASA's managers asked Thiokol to reconsider. And what happened next is textbook: Thiokol's senior management held a private caucus — without the engineers — and reversed their recommendation. Luna: So Boisjoly and his team were literally excluded from the decision-making process after they'd brought the bad news. Lucas: Exactly. And later, in the investigation, it came out that Boisjoly had written memos months earlier warning about the O-ring problem. His direct supervisor had read them, but no action was taken. The boss didn't want to escalate bad news upward either. So it's not just about the boss yelling at you — it's about a culture where bad news is punished, stoped, or ignored at every level. Luna: And the cost was seven lives and the entire shuttle program. Lucas: Right. So let's bring this down to the everyday office. Most of us aren't dealing with life or death decisions. But the pattern is the same: you have bad news — a project is behind schedule, a client is unhappy, a deadline will be missed — and your boss's first reaction is anger, blame, or dismissal. After that happens a few times, you just stop telling them. Luna: Which then means they're making decisions based on incomplete information. Lucas: Yes. And eventually, the bad news surfaces anyway — in a quarterly review, in a client complaint, in a missed target — and now it's a crisis instead of a manageable problem. So the question is: how do you manage a boss who has that reaction? How do you keep delivering bad news even when your instinct is to hide it? Luna: What's the first tactic? Lucas: The first one is something called the 'pre-mortem.' This is a technique from decision science, popularized by psychologist Gary Klein. Instead of waiting for a problem to happen and then reporting it, you frame the conversation as a forward-looking risk assessment. You say something like, 'I want to walk through a scenario that could happen if we stay on this path.' Luna: So you're not saying 'this is going wrong,' you're saying 'this could go wrong.' Lucas: Exactly. The boss's brain hears it differently. It's not a criticism of their decision — it's a strategic exercise. And because it's hypothetical, they're less likely to get defensive. I've seen this work with a boss who would literally start shouting if you said 'we have a problem.' But if you said 'let's do a quick pre-mortem on this timeline,' he'd engage like a problem-solver. Luna: Second tactic? Lucas: The second is to always lead with your proposed solution. Bad news is easier to swallow if you don't look like you're just dumping a problem. So you frame it as: 'Here's what's happening, and here are three options I see for how we handle it.' You're not the messenger — you're the problem-solver who happens to be delivering context. Luna: That makes sense. If you come in with just the problem, you're just bringing pain. If you come with options, you're bringing value. Lucas: Bingo. And the third tactic is probably the most counter-intuitive: ask your boss a specific question in your one-on-one. Something like, 'What information would you want to know, even if it's bad, to make the best decision for the team?' You're literally asking them to define their appetite for bad news. Some bosses will say 'everything,' but a lot of them will actually tell you their boundaries — like 'don't come to me with small operational hiccups, but definitely tell me if a client is at risk.' Luna: So you're basically negotiating a communication protocol. Lucas: Yes. And once they've stated it out loud, they're more likely to honor it when you actually bring bad news, because you can say, 'You told me you wanted to know this.' It's a form of commitment and consistency — a psychological principle. People tend to follow through on things they've said publicly. Luna: I want to go back to the pre-mortem idea for a second. Can you give a real example of how you'd phrase that? Lucas: Sure. Let's say you're working on a product launch that's in six weeks. You see red flags — the vendor is late, the testing is behind. Instead of going to your boss and saying 'the launch timeline is at risk,' you say, 'Hey, I want to run a quick pre-mortem on the launch. Let's assume it's six weeks from now and the launch failed. What do we think the most likely causes would be?' Luna: And then you list the vendor delay and testing issues as possibilities. Lucas: Right. The boss is now brainstorming with you. They might even say, 'Yeah, that vendor is a risk. Let's find a backup.' You've just communicated the bad news without ever saying 'we have a problem.' The boss feels smart because they helped solve it. And you've protected the information flow. Luna: That's elegant. I think a lot of people avoid these conversations because they're afraid of the emotional reaction. The boss might yell, or blame them personally. Lucas: And that's real. Some bosses are just volatile, and no technique will completely neutralize that. In those cases, the most important thing is to document everything. If you bring bad news and they explode, send a follow-up email summarizing what you discussed. Something like, 'Thanks for the conversation. As discussed, the timeline is at risk because of X. I'll keep you updated.' That way, if the problem becomes a crisis later, there's a paper trail that you raised it. Luna: And if the boss consistently punishes bad news to the point where it's affecting the team's performance or your mental health, that's probably a sign you need to think about leaving. Lucas: Absolutely. But before you get to that point, try the pre-mortem, try the solution-first framing, and try asking them directly what they want to know. You might be surprised how much of a boss's reaction is just a habit they haven't examined. Sometimes all it takes is one conversation to reset the pattern. Luna: And if today's episode was useful to you, if it gave you a concrete tool or a new way to think about a frustrating dynamic, that's exactly why we do this show. Keeping this podcast ad-free and listener-supported means we can keep digging into these real workplace challenges without selling anything. If you'd like to help with that, you can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, and I'll just add — we hear from listeners all the time saying a specific episode helped them navigate a tough situation. That means a lot to us. So if you're one of those people, or if you just want to keep this resource available, that link is there. No pressure, just appreciation. Luna: Exactly. So back to the tactics — one more thing I want to mention. The pre-mortem works best when you make it a regular practice, not just a one-off. If you do it in every project kickoff, it becomes normal. The boss stops seeing it as 'bad news' and starts seeing it as 'how we do things.' Lucas: That's a great point. And it's actually what high-reliability organizations do — like aircraft carriers and nuclear power plants. They institutionalize the practice of imagining failure. Because they know that the cost of not hearing bad news is catastrophic. For the rest of us, the cost is a missed deadline or a lost client, but the principle is the same. Luna: Alright, so to wrap up — if you have a boss who shoots the messenger, try the pre-mortem, lead with solutions, and ask them directly what they want to know. And if all else fails, document everything. Lucas: And remember, you're not alone. A lot of people are dealing with this. The fact that you're trying to find a better way to communicate already puts you ahead. Good luck out there.