Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Why Good Managers Ignore Bad News
Transcript
- Lucas: There is a specific kind of panic that sets in on a Monday morning when a manager realizes their team has been hiding something big for weeks. It usually starts with a small anomaly—a missed deadline that was quietly rescheduled, or a client email that never made it to the inbox. By the time the truth surfaces, the window for correction has closed, and the manager is left asking why no one told them sooner. Luna: It is always worse than they expected because the silence stretches out so much longer than anyone admits until it happens. You think they will speak up next week, but they wait another month. Lucas: Exactly. And the irony is that most managers pride themselves on being approachable. They hold regular one-on-ones, they send Slack messages asking how things are going, and they genuinely believe they have an open door. But when a direct report walks into that meeting, they aren't thinking about the manager's openness; they are thinking about the last time someone brought bad news and what happened to them. Luna: Right, because if the reaction was even slightly negative—like frustration or disappointment—they learn to filter the signal immediately. Lucas: That is the core mechanism here. We call it the 'filter of consequence.' When I look at data from organizational psychologists, the number one reason employees withhold information is fear of negative career impact. It isn't laziness. It isn't malice. It is self-preservation. A high performer knows that admitting a mistake might label them as risky, so they double down on the fix instead of sharing the problem early. Luna: So the manager ends up with a polished surface while the foundation cracks underneath because everyone is trying to protect their reputation. Lucas: Precisely. Let me give you a concrete example from a recent case study involving a senior product manager at a fintech firm. She discovered a significant compliance risk in their new payment feature just ten days before launch. Instead of flagging it, she spent those ten days working sixty-hour weeks to patch it internally, hoping to present a finished solution rather than a broken process. The patch held, barely, but the stress nearly burned her out completely. Luna: And if the patch had failed during the launch window, the fallout would have been catastrophic for both her and the company. Lucas: Which brings us to the central question: how do we shift the culture from 'hide the mess' to 'surface the risk'? It starts with redefining what bad news means in your team meetings. Most managers treat bad news like a failure. We need to start treating it like data. Data is neutral. Failure is emotional. If you can separate the two, you lower the stakes of speaking up. Luna: But how do you actually teach a team to see failure as data without sounding like you are preaching? People react viscerally to criticism. Lucas: You model it yourself first. The most effective leaders I know start their weekly stand-ups by sharing a current blind spot or a mistake they made that week. It sounds counterintuitive, but when the leader exposes vulnerability, it grants permission for others to do the same. It signals that the hierarchy is flat when it comes to truth-telling. If the boss can admit they misread the market, the analyst can admit they misread the code. Luna: That requires a lot of ego suspension on the manager's part, though. It feels risky to admit weakness publicly. Lucas: It does feel risky, but the alternative is blindness. Blindness is fatal in business. There is a concept called 'premortem analysis' that project managers use. Before a project launches, they ask the team to imagine it has already failed spectacularly. Then they work backward to list all the reasons why it failed. This forces people to voice their doubts and fears in a hypothetical space where no one gets punished. It normalizes the conversation about failure before any real damage occurs. Luna: I love that because it makes the criticism abstract and theoretical, so people feel safe enough to be honest about the risks. Lucas: It removes the personal attack element. You aren't attacking the person; you are attacking the plan. That distinction matters immensely. Another practical step is changing how you respond in the moment. When someone does bring you bad news, your immediate reaction sets the tone for the next ten years of their honesty. If you sigh, check your watch, or ask 'why didn't you tell me sooner,' you have just reinforced the filter of consequence. You have taught them that silence is safer. Luna: So the correct response is almost mechanical? Like, thank them immediately regardless of how bad the news is? Lucas: Thank them, yes. But also validate the difficulty. Say something like, 'I appreciate you bringing this to me directly. It must have been hard to decide when to speak up.' That acknowledgment is powerful. It shows you understand the social cost they incurred to be honest. Once you acknowledge that cost, you lower the barrier for the next time. You are essentially paying them back in psychological currency for taking the risk. Luna: That is such a simple shift in language, yet it changes the entire dynamic of the relationship. It moves from adversarial to collaborative. Lucas: Collaborative is the right word. Because ultimately, the manager cannot solve problems that they do not know exist. By hiding bad news, the team is doing the manager's job for them, which robs the manager of context. And when the manager finally finds out, they have less time and fewer resources to fix it than if they had known earlier. It is a net loss for everyone involved. Luna: So transparency isn't just a moral imperative; it is a strategic efficiency tool. It saves time and money by catching errors early. Lucas: Absolutely. Efficiency is a great angle because it appeals to business-minded teams. But there is also a retention angle. High performers want to work in environments where they feel trusted. If they constantly have to hide their struggles or mistakes, they feel like they are walking on eggshells. That anxiety drains energy. Energy drained on fear is energy taken away from innovation and problem-solving. Luna: Right, you cannot expect creative output from people who are conserving all their mental bandwidth on self-protection. Lucas: Exactly. So, to summarize the actionable steps: First, model vulnerability by sharing your own misses early. Second, use premortems to normalize risk discussion. Third, reward the messenger by thanking them and validating the difficulty of speaking up. Fourth, focus on the system failure, not the person. These four steps create a feedback loop where bad news travels fast and far. Luna: It really comes down to consistency. One good response won't fix years of bad habits, but consistent positive reinforcement will rebuild trust over time. Lucas: Consistency is key. Trust is built in drops and lost in buckets. Every time someone shares bad news and is met with curiosity instead of judgment, you add a drop. Every time they are punished, you lose a bucket. It is an asymmetric game, which is why managers need to be intentional about every interaction. Luna: I wonder if there are metrics we can track to see if this is working? Like, maybe the frequency of issues reported before they become crises? Lucas: That is a brilliant idea. You can track the 'lead time' of problem identification. Measure how many days between the emergence of a risk and its reporting to leadership. If that number shrinks over time, your culture is improving. If it stays static or grows, you still have a filtering problem. It turns a soft skill into a hard metric. Luna: Tracking lead time is smart. It gives the manager a dashboard view of their team's psychological safety without having to ask directly. Lucas: Direct questions can be biased because people will lie to look good. Behavioral data tells the truth. If your tickets are being fixed quietly in the background rather than flagged in the project management tool, your data is lying to you too. Luna: So the tools themselves need to encourage visibility, not just completion. That is a design issue as much as a management issue. Lucas: It is both. Your tools should highlight blockers, not just completed tasks. Make the visible status of a blocker a celebrated part of the workflow, not a shameful secret. When a blocker is raised, the team should rally to help, not point fingers. That shifts the narrative from blame to support. Luna: Rallying around blockers changes the social dynamic entirely. It makes problem-solving a team sport rather than an individual burden. Lucas: It does. And that is the ultimate goal. You want a team that solves problems together, not a team of individuals hiding problems alone. When you build that culture, you stop losing control through micromanagement because you have eyes everywhere, voluntarily shared by the people closest to the work. Luna: Voluntary sharing is the magic phrase. Forced reporting is surveillance; voluntary reporting is partnership. Lucas: Partnership. That is exactly what it is. And partners share the hard stuff because they care about the outcome. If your team doesn't feel like partners, they will act like employees—doing only what is asked and nothing more. Luna: So the test is whether they feel ownership over the success, not just responsibility for the tasks. Lucas: Ownership drives the desire to protect the mission, which includes protecting it from hidden threats. It aligns their self-interest with the team's health. When they see the whole picture, they don't hide the pieces. Luna: I think a lot of managers fail because they think they have to be the hero who fixes everything, rather than the coach who enables the team to see the field. Lucas: The hero myth is dangerous. Heroes die in movies. Coaches win championships. A coach trusts the players to see the open lane. If the player is screaming that the lane is blocked, the coach listens and adjusts the play. That is the dynamic we are aiming for. Luna: Adjusting the play based on real-time intel is just better strategy than sticking to the script when the script is wrong. Lucas: Agreed. Agility wins in business. And agility requires accurate, timely information. Silence is the enemy of agility. Luna: So building a culture of bad news is really just building a culture of speed and accuracy. Lucas: Speed and accuracy. Those are the two pillars of modern business. Everything else is decoration. If you have those two, you can survive almost anything. If you don't, even the best strategy will fail because you are flying blind. Luna: Flying blind is the scariest position for a manager to be in, especially when the stakes are high. Lucas: It is. But it is avoidable. It starts with that first difficult conversation where you choose curiosity over judgment. It starts with listening to the quiet voice that says, 'Hey, something is off here.' Luna: And trusting that voice enough to act on it, rather than dismissing it as noise. Lucas: Exactly. Noise becomes signal when you pay attention to it. The trick is teaching your team that their signal is valuable, even when it is ugly. Luna: Valuing the ugly signal is the hardest part for human nature, but the most necessary for business success. Lucas: It is. And once you get there, you realize that the bad news wasn't the problem. The lack of trust was the problem. Fix the trust, and the bad news becomes just another Tuesday. Luna: Just another Tuesday. That is the dream for any manager who wants to sleep well at night. Lucas: Sleep well, lead clearly, and listen closely. That is the formula. Luna: Thanks for keeping us grounded in the reality of how teams actually work, Lucas. Lucas: My pleasure, Luna. Now, let's talk about how we fund this show without selling our souls to advertisers. Luna: Because we rely on the listeners who value this kind of deep dive into management dynamics. Lucas: A small group of you chip in monthly through buy me a coffee dot com slash fexingo, and that literally funds the production costs so we can keep this ad-free and independent. Luna: It keeps the lights on and lets us take the time to research these topics properly. Lucas: If that resonates with you, check out the link in the show notes. No pressure, just an option if you want to support the work directly. Luna: We appreciate every single contribution that helps us keep making these conversations possible. Lucas: Back to the topic—what is one thing you will try differently in your next team meeting to encourage more honest reporting? Luna: Starting the meeting by sharing my own uncertainty or a recent mistake I am still untangling. Lucas: That is a powerful place to start. It invites others to join you in the messy middle rather than waiting for the polished finish. Luna: The messy middle is where the real work happens, after all. Lucas: Indeed. Until next time, keep your ears open and your defenses down.