Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Why Your Team Hides the Truth From You
Transcript
- Lucas: There is a specific kind of silence that happens in a manager’s office, and it is usually louder than any argument. If you have been managing for more than a year, you know the feeling: you ask your team for an update on a project timeline, and they give you the polished version. The one where everything is on track, the risks are mitigated, and the deadline is solid. But you can feel in your gut that something is off, yet you cannot find the crack in the armor. Luna: Right, because if you push too hard, you look like you do not trust them, so you let it slide until the crisis hits. It is the classic trap of assuming that transparency is a default setting rather than a cultivated habit. Lucas: Exactly. And what makes it worse is that most of us think we have solved this problem with things like open door policies or anonymous feedback boxes. We put up posters about psychological safety and then act surprised when our best employees quietly resign because they stopped sharing bad news with us. Today, I want to talk about the structural reasons why truth dies in middle management, and how to fix it before it costs you a key hire. Luna: I love that angle because it shifts the blame from individual personality flaws to systemic incentives. Most managers think honesty is just a moral choice, but it is actually a risk calculation. Lucas: It is absolutely a risk calculation. Let me give you a concrete example from a mid-sized software company I consulted with last quarter. They had a senior engineer who noticed a critical flaw in their new release candidate two weeks before launch. He reported it to his engineering lead, who was already stressed about hitting a marketing deadline. Instead of escalating the issue, the lead downplayed it, hoping to fix it later. When the bug caused a minor outage, the lead blamed the engineer for not being clear enough. The engineer never spoke up again about anything less than catastrophic. Luna: That is brutal, but realistic. The lead protected his own short-term metric, sacrificing long-term truth. Did the company ever realize they lost that engineer’s institutional knowledge? Lucas: They realized it six months later when he left for a competitor. The turnover cost them nearly sixty thousand dollars in recruiting fees and lost productivity, plus the client churn from that initial outage. But here is the thing nobody talks about: the system rewarded the lie. The lead hit his deadline, got his bonus, and stayed employed. The engineer paid the price for speaking truth. So now, every other manager on the team has learned that silence is safer than accuracy. Luna: So the incentive structure actively punishes honesty. That explains why good managers avoid tough conversations; they are trying to navigate a minefield where telling the truth might get them shot. Lucas: Precisely. And this brings us to the concept of the hierarchy of truth. In healthy organizations, truth flows freely from bottom to top. In dysfunctional ones, it gets filtered at every level. Middle managers become filters, not conduits. They strip away the nuance, the warnings, and the context because they are afraid of looking incompetent or causing alarm. By the time the information reaches executive leadership, it is sanitized to the point of uselessness. Luna: It reminds me of that old military saying about intelligence being the first casualty of war. Here, it is the first casualty of career ambition. Lucas: That is a perfect way to put it. And if you are a first-time manager, you are uniquely vulnerable to this. You are trying to prove yourself, so you might be tempted to present only the positive news to your own boss. You start curating reality instead of reporting it. It feels like protection, but it is actually isolation. You are building a bubble where you are the center of a false universe. Luna: I have seen that happen. A junior manager told me once she stopped sending weekly reports because her boss always seemed annoyed by delays. So she started sending only wins. She thought she was being efficient, but she was actually lying by omission. Lucas: And that is dangerous because decisions are made based on incomplete data. If your boss thinks the project is green when it is actually red, they will allocate resources elsewhere. Then when the crash comes, everyone is caught off guard. The real cost is not just the mistake, but the erosion of trust. Once people realize you are filtering information, they stop believing anything else you say. Luna: So how do we break that cycle? Because telling people 'just be honest' doesn't work when the consequences of honesty feel punitive. Lucas: You have to change the reward structure. First, you must explicitly reward the delivery of bad news. I mean literally celebrate it. When someone brings you a problem early, do not react with frustration. React with relief. Say, 'Thank you for telling me this now. We have time to fix it.' That signals that you value accuracy over comfort. Luna: That requires a lot of emotional discipline for a manager. It goes against every instinct we have to fix things immediately and calm down. Lucas: It does. But you have to separate the person from the problem. Critique the process, not the messenger. If someone reports a failure, ask questions about the system that allowed it to happen, not why they failed. This builds psychological safety. People need to know that their job security is not tied to their perfection. Luna: It also forces the manager to be accountable for the system. You can't just blame the employee if the system is broken. That shifts the dynamic from policing to problem-solving. Lucas: Exactly. Second, create formal channels for dissent. In meetings, assign someone the role of devil's advocate. Rotate it so it is not always the same person. Make it official. When dissent is a job requirement, it is no longer personal rebellion. It becomes part of the workflow. This removes the social risk of disagreeing with authority. Luna: I like that because it depersonalizes conflict. It is not 'I disagree with you,' it is 'my role is to challenge this assumption.' Lucas: Right. And third, practice vulnerability yourself. Admit your own mistakes publicly. Talk about times you were wrong or missed something. When leaders model fallibility, it gives permission for others to do the same. If you pretend you have all the answers, your team will hide their uncertainties. If you admit you don't know everything, they will share their insights. Luna: That is hard though. Managers feel like they need to be the expert. Showing weakness feels like losing authority. Lucas: It feels that way, but it actually builds deeper authority. People respect competence, but they follow authenticity. If you are always right, you are either lucky or lying. If you are honest about your gaps, you invite collaboration. That is how you build a team that solves problems together rather than hiding from you. Luna: So it is not about being weak, it is about being reliable. Trust is built on consistency and honesty, not on infallibility. Lucas: Spot on. Now, before we dive deeper into the mechanics of feedback loops, I want to take a quick second to talk about how we keep this show running. We do not have advertisers, and we do not run pop-ups. The only reason we can produce these deep dives every single week is because listeners like you chip in monthly through buy me a coffee dot com slash fexingo. It is not much, but it covers our hosting costs and keeps the content free for everyone. If you find value in what we do, consider joining that small group of supporters who help keep the lights on. Luna: Yeah, and honestly, knowing that you support us directly makes us want to dig even harder into these topics. It keeps us honest, too. Lucas: Thanks for keeping us going. Now, back to the team. Let's talk about the specific language you use when receiving bad news. There is a subtle shift that happens when you respond defensively. You might ask, 'How did this happen?' which sounds accusatory. Try asking, 'What did you see coming?' instead. It assumes foresight and invites analysis rather than defense. Luna: That is such a small change, but it completely reframes the conversation from past blame to future learning. Lucas: It is. And it trains your team to think ahead. Over time, they will start bringing you problems earlier because they know you are interested in the pattern, not just the punishment. You are building a learning organization instead of a blaming one. Luna: But what about the managers who are just naturally defensive? Some people really struggle to hear criticism, even when it is framed nicely. Lucas: Then they need coaching. Or they need to understand that their defensiveness is costing the team credibility. You can frame it as a professional development goal. 'If you want to move into leadership, you need to master receiving difficult information gracefully.' It becomes a skill gap, not a character flaw. Luna: I like that approach. It treats emotional regulation as a technical skill, which makes it easier to improve. Lucas: Exactly. And remember, you are not responsible for fixing every problem your team faces. You are responsible for creating an environment where problems are visible. Visibility allows for intervention. Secrecy guarantees failure. So focus on visibility first. Luna: Visibility over control. That is a powerful mantra for any manager trying to scale their impact. Lucas: It is. Because if you try to control everything, you become the bottleneck. Every decision slows down. Every risk is hidden until it explodes. But if you prioritize truth, you empower your team to solve problems locally. You get faster iteration and better outcomes. Luna: So the goal is to make yourself obsolete as a firefighter, and essential as a strategist. That is a nice way to put it. Lucas: I think that is the ultimate test of management. Are you needed because you are indispensable, or are you needed because you enable others to be indispensable? The former is a burden. The latter is a legacy. Luna: And that starts with listening to the truths that are hard to hear. It is uncomfortable work, but it is the only way to build a team that lasts. Lucas: Absolutely. Next time you sit down with your team, pay attention to the silences. Ask the questions that make people slightly nervous. Listen for what is not being said. You might be surprised by how much truth is waiting just beneath the surface, ready to help you succeed.