Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Resists Feedback
Transcript
- Lucas: So you've got a team member who's smart, delivers results, but every time you offer a piece of feedback — even something small — they deflect, get defensive, or just shut down. You're not alone. A 2023 study from the Center for Creative Leadership found that thirty-seven percent of new managers say they avoid giving corrective feedback entirely, and six months later, those teams show twenty-three percent lower performance. Luna: Wow, that's a huge stat. So avoiding the conversation actually makes things worse — but it's understandable why managers hesitate. Lucas: Exactly. Today we're going to talk about how to manage someone who resists feedback — not by getting louder or more forceful, but by changing the frame entirely. And before we go deep, a quick note: Manager Mondays, like all Fexingo shows, stays ad-free because of listener support. If you've gotten something useful out of these episodes — maybe a framework that helped you handle a tough one-on-one — a couple of dollars a month genuinely makes a difference. You can find us at buy me a coffee dot com slash fexingo. Luna: It's a small thing that adds up. And it keeps the shows coming without any sponsor interruptions. Lucas: Right. So let's get into it. I want to start with a concrete case. A friend of mine — let's call her Priya — manages a team of seven engineers at a mid-sized SaaS company. One of her senior engineers, let's call him Dan, is technically excellent. Ships on time. But whenever Priya suggests a different approach or flags a potential issue in his code, Dan immediately explains why her feedback doesn't apply. 'That's an edge case.' 'The test environment was off.' 'I already considered that.' Luna: The classic 'yes, but' pattern. I've seen that before. It's exhausting because you start to feel like you're always the one who's wrong. Lucas: Exactly. And the natural instinct for a new manager is to either escalate — be more direct, more firm — or just give up and stop offering feedback altogether. Both are bad. Escalation makes Dan more defensive. Withdrawal means his blind spots never get addressed, and eventually the team suffers. Luna: So what's the first move? How do you break the cycle? Lucas: Step one: reframe feedback as a shared goal. Instead of saying 'I think this approach could be improved,' which Dan hears as criticism, you say 'Help me understand how we can make this feature more resilient to edge cases.' You're not evaluating him — you're problem-solving together. That lowers his defensiveness because you've invited him into the solution. Luna: It's subtle but powerful. You're still delivering the same feedback, but you've changed the frame from 'you did something wrong' to 'let's solve this together.' Lucas: Exactly. The research backs this up. When feedback is framed as a collaborative inquiry rather than a judgment, the recipient's brain activates areas associated with reward and learning, not threat. It's called the 'feedback orientation' shift. Luna: So what did Priya actually do? Did she try that? Lucas: She did. In their next one-on-one, she said, 'Dan, I want to talk about the deployment process for the new module. I see some potential risk around how we're handling error logging, and I'd like your input on how we could make it more robust.' He initially started to explain why it was fine, but she stayed in inquiry mode — 'What would happen if a third-party API goes down? What's our fallback?' Within a few minutes, he was actively brainstorming solutions. She didn't have to 'give feedback' at all. Luna: That's clever. But I imagine some people are just habitually defensive. Is one conversation really enough? Lucas: It's not. For habitually defensive people, you need step two: use specific behavioral observations, not generalizations. Instead of saying 'You always dismiss my suggestions,' which triggers a denial, you say, 'In our last three code reviews, when I pointed out the edge case in the payment module, your response was that it was an edge case and not worth addressing. I want to understand your thinking there.' That's concrete. It's not about their character — it's about a pattern of behavior. Luna: And you've named the pattern without labeling them. That's key. Nobody wants to hear 'you're defensive.' Lucas: Right. And then you ask a question that makes them reflect: 'What would make that type of feedback feel more useful to you?' That shifts them from defense to ownership. Luna: I've used that before. It often reveals that the person actually wants feedback — they just want it in a different format. Maybe they prefer written feedback so they can process it, or they want it one-on-one rather than in a group. Lucas: Exactly. And that leads to step three: create a feedback contract. This is a written — or at least explicit — agreement about how you'll both give and receive feedback going forward. It covers frequency, format, and the goal of the feedback. For Dan, Priya said, 'How about this: before our weekly one-on-one, I'll send you two things I noticed that went well, and one thing I think we could improve. You can have time to think about it before we talk.' He agreed. Luna: That's smart because it removes the surprise element. Defensiveness often comes from being caught off guard. Lucas: Exactly. The contract also includes a rule: when feedback is given, the receiver's job is to say 'Thank you, I'll think about that' — not to defend or explain. You can add context later, but the immediate response is just acknowledgment. That alone can break a habit. Luna: But what about when the resistance is actually justified? Sometimes a manager's feedback is wrong, or it doesn't account for things the employee knows. How do you distinguish between defensive resistance and legitimate pushback? Lucas: That's a great point. And it's important to distinguish. The key is intent and pattern. If someone pushes back once with a solid reason — 'Actually, I tried that approach last quarter and it caused latency issues' — that's not resistance, that's expertise. Healthy pushback is data-driven and specific. Defensive resistance tends to be vague — 'It's fine,' 'You don't understand,' 'That won't work' without evidence. Luna: So as a manager, you have to be honest with yourself. Is this person being defensive, or are they just better informed on this particular topic? Lucas: Exactly. And that's where trust matters. If you have a pattern of being wrong, the resistance might be earned. But in Priya's case, Dan's resistance was across the board — even on things he later admitted were valid. So it was a pattern. Luna: Let's talk about the manager's own role in creating the feedback culture. If you're a first-time manager and you've got a defensive team member, there's a tendency to take it personally. Lucas: Absolutely. And that leads to either over-accommodation — 'I'll just give positive feedback only' — or over-confrontation — 'I'm going to prove I'm the boss.' Neither works. The thing is, resistance to feedback is often a learned behavior. Maybe the employee had a previous manager who used feedback as a weapon, or they were in a culture where mistakes were punished. Your job is to slowly rebuild that trust. Luna: How long does that usually take? A few weeks? Months? Lucas: It depends. For someone like Dan, with a strong habit of deflection, Priya saw noticeable improvement after about six to eight weeks of consistent use of these three steps. The key is consistency. If you slip back into 'you should have done X,' you reinforce the old pattern. You have to be disciplined about the new frame. Luna: What about the rest of the team? If one person is resistant to feedback, it can create a norm where others think that's acceptable too. Lucas: That's a real risk. Especially if the resistant person is senior or high-performing. Other team members watch how you handle it. If you avoid it, they learn that feedback is optional. If you handle it well — with respect and structure — they see that feedback is part of the culture, and it's safe. Luna: So there's a secondary benefit. Managing one person well sets the tone for everyone. Lucas: Exactly. And that's why the feedback contract is so powerful — it's not just for that one person. You can use it as a team-wide tool. 'Here's how we'll give feedback to each other.' That normalizes the process. Luna: Let's circle back to the Center for Creative Leadership study. Thirty-seven percent of new managers avoid giving corrective feedback. That's a huge number. What's the cost beyond the twenty-three percent lower performance? Lucas: There's a retention cost. If feedback isn't happening, employees don't grow, and they eventually leave — especially high performers who want to improve. And there's a culture cost: silence becomes the norm, issues fester, and resentment builds. The manager who avoids feedback is actually avoiding their core responsibility. Luna: That's a hard truth. But it's also empowering because it means you can make a real difference by leaning into it. Lucas: Right. And you don't have to be perfect. You just have to start. One small shift — like asking a question instead of making a statement — can change the dynamic. The feedback-resistant employee is often just waiting for proof that feedback is safe. You're the one who provides that proof. Luna: So to wrap up, the three steps are: reframe feedback as a shared goal, use specific behavioral observations, and create a feedback contract. And remember that your own consistency is what makes it work. Lucas: Exactly. And one final thought: when you get that first sign that the resistance is softening — maybe they say 'That's a good point' instead of 'Yes, but' — acknowledge it. Say 'I really appreciate you considering that.' Positive reinforcement works for managers too. Luna: I think that's a great note to end on. Thanks, Lucas. Lucas: Thanks, Luna. And thank you to everyone listening. If this episode gave you a new approach to try, we'd love to hear how it goes. We'll catch you next time.