Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Coach a Defensive Employee
Transcript
- Lucas: You give someone perfectly reasonable feedback — specific, behavioral, focused on impact — and instead of a nod, you get a wall of pushback. 'Well, actually...' 'The reason I did that was...' 'It sounds like you're saying I'm not good at my job.' Luna: The defensive employee. It's one of the hardest dynamics for a first-time manager, because you start second-guessing yourself: Was I too harsh? Did I phrase that wrong? Or is this person just uncoachable? Lucas: Right. And the worst part is, if you handle it wrong, you either stop giving honest feedback — which hurts the employee and the team — or you lean in harder and create actual conflict. So today I want to get really concrete about one specific approach: coaching the defensiveness itself, not just the work behavior that triggered it. Luna: If you're a manager who's been avoiding a feedback conversation because you dread the reaction — this one's for you. And before we dive in, Lucas, I want to say: if this episode helps you navigate a tough conversation you've been putting off, the reason we can keep doing these deep dives without ads is listener support. Lucas: Yeah. It's a small thing that makes a big difference. If you find yourself using something from today's episode — or any past episode — in your actual Monday morning, head over to buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. And thank you to everyone who already has. Luna: Okay, back to the defensive employee. Lucas, you mentioned coaching the defensiveness itself. What does that actually look like in a one-on-one? Lucas: Let me start with a concrete case. I was talking to a manager at a mid-sized SaaS company — let's call her Sarah — and she has a senior analyst named Priya. Priya is brilliant. Her work product is strong, her output is high. But in every feedback conversation — annual review, project debrief, even casual check-ins — Priya's first reaction is to explain why the feedback isn't valid. Luna: So Sarah starts to dread giving her any constructive input at all. And because Priya is a high performer, Sarah just thinks, 'Maybe I should let it go.' Lucas: Exactly. That's the trap. You don't want to lose a strong contributor, so you start editing your feedback down to only positive things. But then Priya misses development opportunities, and eventually her blind spots become problems. The defensiveness doesn't go away — it just metastasizes. Luna: So what did Sarah do? Lucas: She tried something we call the 'two-minute rule.' It's not about compressing feedback into two minutes — it's about the first two minutes of the conversation. The idea is: before you deliver any content about the work, you name the dynamic you're about to enter. You say something like, 'Priya, I have a piece of feedback about the client report. I know that when you hear critical feedback, your instinct is to explain your reasoning. That's totally understandable — you care deeply about your work. But for the next few minutes, I'm going to ask that you just listen first. Then we'll talk through your perspective.' Luna: That's interesting — you're pre-empting the defensiveness without accusing her of being defensive. You're naming it as a pattern, but you're also giving her permission to be that way later. Lucas: Right. And the research backs this up. When you prime someone that a difficult conversation is coming and that you expect a certain reaction, you reduce the surprise factor. The amygdala doesn't go into fight or flight as quickly. Sarah told me that after using this framing a few times, Priya started catching herself — she'd hear feedback, pause, and say, 'I want to explain, but I'm going to sit with that for a second.' Luna: That's huge. But what about when you're in the moment and the defensiveness erupts anyway? You didn't set the frame, and suddenly you're getting pushback. Lucas: That's the second technique: the 'negative observation.' This comes from a coaching framework I learned from a friend who works in executive coaching. When you see the defensive behavior happening in real time — the tone shift, the interrupting, the rationalization — you pause the conversation and you name what you just observed. Not as criticism, but as data. Luna: Like, 'I notice you just interrupted me and raised your voice. Let's pause. What's happening right now?' Lucas: Exactly. The key is to describe the behavior neutrally — what a video camera would have captured — and then ask a genuine question. You're not saying, 'You're being defensive.' You're saying, 'I noticed you did X. What's going on?' That shifts the conversation from content — arguing about the feedback — to process — talking about how you're talking. And usually the person will say something like, 'I think I felt attacked,' or 'I worry you're questioning my competence.' And then you can address the underlying fear instead of the surface argument. Luna: So you're essentially coaching the defensiveness as a behavior in its own right, separate from whatever the feedback was about. Lucas: Exactly. And over time, you're teaching the employee to self-monitor. The goal isn't to eliminate defensiveness — that's a normal human reaction. It's to shorten the recovery time. From a full-on wall of explanations to a ten-second pause and a deep breath. Luna: I want to push on something, though. What if the defensiveness isn't just fear — what if the employee genuinely disagrees with the feedback? How do you distinguish between healthy pushback and defensive blocking? Lucas: Great question. The litmus test is: is the person listening and then offering a counterpoint, or are they dismissing before you finish? Healthy pushback shows engagement — they can paraphrase your feedback before they challenge it. Defensive blocking is interruption, rationalization, or turning the feedback back on you. So one tool is to say, 'Before you respond, can you tell me what you heard me say?' If they can't accurately restate your feedback, they weren't listening — they were defending. Luna: That's such a clean diagnostic. And it forces them to slow down. I've used that with a team member before, and they said, 'Oh... I thought you were saying I didn't care about the project. But you're actually saying I need to update the timeline more proactively.' The whole conversation shifted. Lucas: That's the win. Because once they hear the actual feedback — not the one they feared — they can usually engage with it productively. The defensiveness was protecting them from a story they told themselves about what you meant. Luna: So for the manager listening right now who has a Priya on their team — what's the first step? Do you set up a dedicated 'feedback about feedback' conversation? Lucas: I would. But make it separate from performance review season. Schedule a 30-minute one-on-one with the explicit agenda: 'Let's talk about how we give and receive feedback together.' Frame it as a collaboration — you want to be a better coach for them, and you want their help in understanding how they best hear input. Ask them directly: 'When I give you critical feedback, what's your internal reaction? What would make it easier for you to hear?' You're modeling the transparency you want them to adopt. Luna: And you're also gathering intel. Maybe they had a previous boss who used feedback as a weapon. Maybe they've been burned by vague criticism. Understanding the backstory helps you tailor your approach. Lucas: Exactly. One manager I worked with discovered that his defensive employee had been told for years that she was 'too aggressive' without any specific examples. So any form of critical feedback triggered that old wound. Once he knew that, he started every feedback with a specific behavior — 'In yesterday's meeting, when you interrupted Jenna twice...' — and that made it feel less like a character indictment. Luna: It's almost like you're re-teaching their brain that feedback is about actions, not identity. Lucas: That's exactly right. And it takes time. I'd say plan on three to five conversations before you see a consistent change. But if you don't see any improvement after that — if the defensiveness is chronic, across contexts, and the employee refuses to self-reflect — you may have a deeper fit issue. Not everyone is ready for a coaching environment. Some people need a more directive style, and if that's not your approach, you might need to reassign or even exit them. Luna: That's a hard truth. But it's better than letting the defensiveness poison team dynamics — other team members notice when someone can't take feedback, and it sets a bad precedent. Lucas: Yeah. And the irony is, the most defensive employees are often the highest performers, because they've built their identity around being right and being good. The feedback threatens that identity. So the manager's job is to uncouple 'I made a mistake' from 'I am a mistake.' That's the deeper work. Luna: I love that framing. So if I'm a manager, and I have that conversation next week — how do I close it? What's the last thing I say? Lucas: I'd end with a question that invites ownership. Something like: 'What's one thing I can do to make our feedback conversations more productive for you? And what's one thing you'll try to do differently when you feel yourself getting defensive?' You're co-creating the solution. That alone reduces defensiveness, because now they're part of the design process. Luna: And you're signaling that this is a relationship, not a power dynamic. It's not you versus them — it's both of you versus the problem. Lucas: Exactly. The best managers I've seen treat defensiveness not as a character flaw, but as a communication pattern that can be reshaped. It takes patience and a little bit of courage to call it out in the moment. But the payoff — a team where feedback flows freely — is enormous. Luna: Alright, next week we're going to talk about something a lot of managers struggle with: how to delegate when you're the one who used to do the work. See you then. Lucas: Take care, everyone.