Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Why Good Managers Avoid Tough Conversations
Transcript
- Lucas: There is a specific kind of silence that happens in a mid-sized marketing agency when a senior account executive starts missing deadlines. It isn't the silence of disagreement or creative block. It is the silence of a manager who has decided it is easier to do the work themselves than to have the uncomfortable conversation with someone they like. Luna: Right. And that silence usually lasts about three weeks before the client calls, and then the manager has to explain why their direct report failed. The damage is already done by the time the truth comes out. Lucas: Exactly. And what is fascinating is that most new managers enter the role thinking their job is to be liked. They think leadership is about creating a warm, supportive environment where everyone feels safe. But if you spend too much time making people feel safe from criticism, you end up making them unsafe from reality. Luna: That is such a sharp distinction. Safe from criticism versus safe from reality. I have seen that play out in sales teams where the rep knows their numbers are soft but the manager keeps saying things will turn around in Q3. Lucas: And by Q4, the rep has lost momentum, the pipeline is empty, and now the manager has to fire them or let them go. The initial conversation could have been a simple course correction. Instead, it became a personnel crisis. This week we are talking about why good people avoid hard conversations and how to fix that habit before it costs you your team's respect. Luna: It feels like a moral failure to some managers, like they are betraying the person by being critical. But I would argue it is actually a betrayal of the team to withhold that information. Lucas: Precisely. When you don't give clear feedback, you are robbing your employee of the chance to improve. You are treating them like a child who needs protection from bad news, rather than an adult professional who needs data to succeed. Let me walk you through a case study from a software firm I consulted with last year. Their engineering lead was brilliant but consistently late on documentation. Luna: So the code was great, but nobody else could use it effectively because there were no manuals or comments? Lucas: Correct. And the manager knew this. Every sprint review, every one-on-one, he would say, Great work on the backend, let us try to circle back to the docs next quarter. He softened the blow by attaching it to praise. He thought he was being encouraging. By the time six months passed, two junior developers had quit because they felt stuck trying to reverse-engineer his work. Luna: Wow. So the manager thought he was preserving harmony, but he actually created chaos for the rest of the team. That is a huge hidden cost. Lucas: It is. And here is the thing: the manager wasn't malicious. He was anxious. He feared that if he addressed the documentation issue directly, the engineer would get defensive, shut down, or leave. So he chose the path of least resistance. But that anxiety is contagious. The team picks up on the fact that certain topics are off-limits, and suddenly no one speaks honestly about blockers. Luna: Yeah, I have definitely noticed that vibe. When the boss avoids mentioning elephant in the room, everyone stops talking about elephants entirely. Then the building burns down and everyone is shocked. Lucas: Shocked and furious. And this brings us to the core mechanism of avoidance. We call it the empathy trap. New managers confuse empathy with agreeableness. They think being empathetic means absorbing the other person's discomfort so they do not have to feel it themselves. But true empathy requires you to hold space for someone else's growth, even if that growth is painful. Luna: So it is less about making them feel comfortable right now, and more about helping them become competent over time. Which is inherently uncomfortable. Lucas: Exactly. Competence is uncomfortable. Growth is uncomfortable. If your one-on-ones are entirely smooth and pleasant, you are probably not doing your job. You want to leave the meeting with both parties slightly unsettled but aligned on a clear action plan. If everyone leaves happy, you likely dodged the bullet. Luna: I love that metric. Leave slightly unsettled but aligned. That is going to be my litmus test for future meetings. Lucas: So how do you break the habit? I recommend a simple structural shift called the Direct-Praise Sandwich. Most people know the sandwich method, but it is usually praise criticism praise. That buries the lead. You want to put the criticism first, immediately followed by the context, and then anchor it with support. Luna: Wait, so instead of starting with the good stuff to soften the blow, you start with the problem? Lucas: You start with the observation, not the judgment. You state the behavior you saw, the impact it had, and then you ask for their perspective. For example, instead of saying, Your docs are terrible, you say, I noticed the API documentation was incomplete for the last release, which caused a three-day delay for the integration team. What was your process there? Luna: That changes the entire tone. It moves it from a character attack to a process check. The engineer can explain if they were blocked by something else, or if they genuinely underestimated the time. Lucas: It invites collaboration. Once they explain, you can say, Okay, I hear you. Here is what we need to change so that does not happen again. Maybe you need help prioritizing, or maybe you need to allocate specific hours for writing. You move from critique to co-creation of the solution. Luna: That feels much more respectful of their intelligence. It treats them like a partner in solving the problem rather than a problem to be fixed. Lucas: And that is the difference between micromanaging and managing. Micromanagement is telling them exactly what to do. Managing is clarifying the outcome and removing obstacles. If you wait until the crisis point to address the obstacle, you have failed as a manager. Luna: It is interesting how this ties back to trust. I think people assume that avoiding conflict builds trust. But really, consistency builds trust. Showing up and addressing things clearly is consistent. Sweeping them under the rug is erratic. Lucas: Spot on. Trust is built on predictability and clarity. When you are vague, you create anxiety. Employees start guessing what you are thinking. Do they hate me? Am I getting fired? Is the project cancelled? That ambiguity is far more stressful than direct feedback. Luna: Yeah, the guessing game is exhausting. I would rather hear, You missed the deadline, please tell me why, than wonder if I am secretly being phased out. Lucas: Exactly. Now, before we dive deeper into the script for these conversations, I want to take a quick moment to talk about how this show exists. We deliberately do not run ads on these episodes. It keeps the audio clean and lets us focus entirely on the content without commercial interruptions. If you find value in our analysis and want to support that choice, the link is buy me a coffee dot com slash fexingo. Luna: It really helps keep the production quality high when listeners chip in directly. Thanks for keeping the feed ad-free. Lucas: So let us get practical. How do you handle the pushback? Because sometimes when you deliver that direct feedback, the employee gets defensive. They might say, Everyone makes mistakes, or, I have been working sixty-hour weeks, so cut me some slack. Luna: That is the moment where many managers fold. They apologize for bringing it up. Why do they do that? Lucas: Because they fear losing the relationship. They worry that if they hold the line, the employee will resent them. But here is the counter-intuitive truth: employees respect managers who hold boundaries. Resentment comes from inconsistency, not from standards. If you set a standard and enforce it fairly, they may be annoyed in the moment, but they will respect you long-term. Luna: So staying calm and firm is actually the kindest thing you can do? Even if it feels harsh? Lucas: Even if it feels harsh. Think of it like a coach. A coach who yells insults is toxic. But a coach who says, You dropped the ball, we need to practice tackling, is valuable. The feedback is about the action, not the person. You separate the behavior from the identity. Luna: Separating behavior from identity. That is key. It is not that you are lazy, it is that the report was late. Big difference. Lucas: Huge difference. If you attack identity, they fight to protect their ego. If you address behavior, they can solve the problem. So when they push back, you simply restate the impact. I understand you are busy. The impact remains that the client is waiting. How do we fix that gap? Luna: It shifts the dynamic from adversarial to collaborative almost instantly. You are no longer fighting each other; you are fighting the problem together. Lucas: That is the goal. And remember, you do not have to have all the answers in that first meeting. It is okay to say, This is important, I want to think about the best way to support you, let us reconvene tomorrow with a plan. Giving yourself a beat prevents emotional escalation. Luna: Taking a pause is smart. It shows you are thoughtful about the solution, not just reactive to the frustration. Lucas: Absolutely. And one final piece of advice for new managers: document everything. Not to build a case for firing, but to build a case for clarity. If you have a follow-up email summarizing the discussion, the agreed actions, and the timeline, you remove ambiguity. It protects both of you. Luna: Paper trails are boring but essential. They stop memory from becoming a weapon later on. Lucas: They ensure fairness. If six months from now there is a dispute about performance, you have a record of the conversations, the support offered, and the expectations set. It proves you were trying to help them succeed. Luna: So the tough conversation is not the end of the relationship. It is the beginning of a clearer, more honest working partnership. Lucas: Precisely. It resets the baseline. You have moved from implicit assumptions to explicit agreements. That is how you build a high-performing team. Not by avoiding friction, but by resolving it quickly and respectfully. Luna: I think that is the secret. Friction is inevitable. Unresolved friction is destructive. Resolved friction is productive. Lucas: Well said. So next time you feel that hesitation before having a hard talk, remember: the silence is costing you more than the words ever will. Address it, anchor it, and move forward.