Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Why Your Team Stops Sharing Bad News
Transcript
- Lucas: Let's talk about the lie that every good manager tells themselves: that if they create an open environment, their team will tell them when things are going wrong. It sounds reasonable, but it's usually false. The reality is that most teams develop what researchers call the Bad News Filter. Luna: Which is basically just employees curating reality to protect their own skin, right? Lucas: Exactly. And the tragedy is that they're not doing it out of malice or incompetence. They're doing it because, historically, bad news has been treated as a performance problem rather than a data point. When I was covering tech mergers last year, I spoke with a mid-level product lead who admitted she delayed reporting a critical API failure for three days because her director had publicly scolded the previous person who found a bug. Luna: That makes sense. If the messenger gets shot, people stop bringing messages. Lucas: Right. And so by the time the API issue actually crashed the platform, it wasn't a surprise failure. It was a predictable outcome of a culture where speed mattered more than accuracy. Today, looking at the broader labor market in September 2026, we see this pattern repeating in almost every sector. High performers leave because they feel blindfolded, and new managers struggle because they think silence means everything is fine. Luna: So the real skill isn't asking for feedback, it's designing a system where bad news doesn't trigger a crisis mode. Lucas: Precisely. Most managers ask for candor but punish vulnerability. You might say, 'Tell me what's broken,' but then your body language tightens, your voice goes up a pitch, or you immediately start assigning blame. Employees are incredibly attuned to these micro-signals. They learn within weeks whether it's safer to be honest or to be strategic. Luna: I've seen this happen even in small startups where everyone claims they're like family. The second someone points out a flaw in the founder's plan, the mood in the room completely shifts. Lucas: And that shift is lethal for long-term growth. Let's look at the mechanics of this. There are three specific behaviors that reinforce the Bad News Filter. First is the reactive fix. When a problem is presented, the manager immediately jumps to solution mode. Second is the public critique. Addressing errors in group settings creates audience anxiety. Third is the delay penalty. Punishing the person who finds the error late, rather than rewarding them for finding it early. Luna: Wait, punishing the person who finds it late? Isn't that just holding people accountable for timelines? Lucas: It becomes punitive when the focus is on the individual's mistake rather than the systemic gap that allowed the mistake to persist. If you fire the person who reports a security leak, other employees will simply hide the leak next time. You get the same outcome, but now you also lose the trust of the rest of the team. Luna: So the metric shouldn't be how fast we catch errors, but how openly they're reported. Lucas: Yes. In fact, some forward-thinking organizations now track 'near-miss reporting' as a key health indicator. A near-miss is a potential failure that was identified before it caused damage. If your near-miss numbers are dropping, it doesn't mean you're getting better. It means your team has stopped trying to save you. Luna: That is a terrifying way to measure success. So how do we flip it back? Lucas: The first step is decoupling discovery from consequence. When an employee brings you bad news, your immediate reaction must be curiosity, not correction. Ask questions like, 'What did you see?' or 'How did this slip through?' instead of 'Why did you let this happen?' It sounds subtle, but it changes the entire dynamic of the conversation. Luna: It moves the focus from the person to the process. Lucas: Exactly. Process is fixable. People are fragile. If you treat bad news as a gift of information, you reward the behavior you want to see. If you treat it as a personal failing, you reward concealment. I remember reading a case study about a manufacturing plant that implemented a 'No-Blame Incident Report' policy. Within six months, reported incidents went up by four hundred percent. Luna: Four hundred percent increase in problems? That sounds like a disaster. Lucas: On the surface, yes. But underneath, it meant they finally had visibility into the wear and tear on their equipment. Once they knew what was breaking, they could fix it proactively. Before that, machines were failing catastrophically during peak production, causing massive downtime. The increase in reports was actually a decrease in actual failures over the following year. Luna: Because they could address the root cause instead of just putting out fires. Lucas: Right. Now, there's a second layer to this that new managers often miss. It's about how you handle the timing of the news. Employees often delay reporting because they think they need to have a solution ready before they bring the problem to you. But if you require a solution upfront, you incentivize half-baked ideas or complete silence. Luna: So you're telling them it's okay to come to you with just the problem, no fix attached? Lucas: Yes. Say something like, 'I don't need you to solve this yet. I just need you to flag it so we can figure it out together.' That removes the pressure to be heroic and allows for collaborative problem-solving. It also builds confidence. New employees especially are terrified of looking incompetent. Giving them permission to report uncertainty is a huge relief valve. Luna: It feels counterintuitive though. Doesn't that make the manager look like they don't have control? Lucas: Actually, it does the opposite. Control comes from accurate information. If you're flying blind because your team is hiding mistakes, you have zero control. Transparency is the foundation of authority. When you respond calmly to bad news, you demonstrate emotional stability, which is one of the most trusted traits in leaders today. Luna: Emotional stability as a management tool. I like that. Lucas: It is. And there's one more thing. You have to model the behavior yourself. If you never admit your own mistakes to your team, they will never admit theirs to you. Share your own near-misses. Tell them about a project you misjudged. It normalizes imperfection and shows that the goal is learning, not perfection. Luna: Vulnerability from the top trickles down to honesty throughout the ranks. Lucas: Precisely. Now, before we wrap up this thought on team dynamics, I want to take a brief moment to acknowledge how this show stays independent. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these. Luna: Yeah, it really keeps the ads out and lets us dig into topics like this without corporate interference. Lucas: It does. And it helps us keep the quality high for all of you. Anyway, back to the topic. There's one structural change you can make to reinforce this culture. It's the post-mortem meeting. Luna: Those can get toxic really fast if not handled well. Lucas: They absolutely can. The key difference between a toxic post-mortem and a useful one is the absence of names. Focus entirely on the sequence of events. What happened? Why did it happen? How do we prevent it next time? Never ask 'Who messed up?' Instead ask 'Where did our process fail?' This shifts the blame from individuals to systems. Luna: Systems are easier to fix than personalities. Lucas: Much easier. And it protects your team members from feeling targeted. When people know they won't be scapegoated for honest mistakes, they become much more proactive about identifying risks earlier. It turns your team from a group of defensive actors into a collaborative unit. Luna: So the ultimate goal is to make the team smarter than the manager, not just obedient to them. Lucas: That's exactly it. Obedience is fragile. Intelligence is resilient. When your team feels safe to share bad news, you gain a collective intelligence that no single manager could replicate. You end up with a organization that learns faster and adapts quicker. Luna: Which is pretty much the only advantage anyone has left in this market. Lucas: Agreed. So the next time you receive bad news, pause. Check your reflexes. Ask yourself if you're reacting to the problem or reacting to the messenger. That split second of reflection can transform your entire team's dynamic. Luna: Less about being right, more about being aware. Lucas: Exactly. Awareness beats certainty any day. Thanks for listening.