Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Says I Dont Need Feedback
Transcript
- Lucas: You give a team member some thoughtful, specific feedback — something that could genuinely help them — and before you finish your second sentence, they say, 'I don't need feedback.' Luna: Oof. That's a tough one. And it usually comes from someone who's actually pretty good at their job, right? Lucas: Exactly. That's what makes it so tricky. If a low performer said that, you'd have a straightforward conversation about humility and growth. But when it's a strong contributor — maybe your top engineer or your best sales rep — the pushback feels almost rational. Like, 'I produce results, so why are you bothering me?' Luna: And the irony is, they probably need the feedback more than anyone, because their blind spots are the ones that eventually derail them. Lucas: What's interesting is this connects directly to something a few listeners have asked us about recently. And I'll be honest — the reason we can spend time digging into these nuanced scenarios, ad-free, is that a small number of listeners chip in monthly over at buy me a coffee dot com slash fexingo. It's not a big ask. It's just what keeps the lights on so we can do deep dives like this one. Luna: Yeah, and we're grateful for that. It lets us focus on the real challenges managers face, not on selling you something. Lucas: Right. So back to the 'I don't need feedback' person. Let me tell you about a case I came across recently. There's a mid-size software company — about 200 people — and their lead backend developer, let's call her Priya. She's brilliant. She's been there four years, she writes clean code, she ships fast. But she's also notoriously prickly about any input on her work. Luna: Classic profile. High performer, low receptivity. What happened? Lucas: Her manager, a guy named Tom, noticed that Priya's code reviews had become tense. Junior developers were afraid to suggest improvements because she'd shut them down. Tom tried giving her feedback on her collaboration style, and she said, 'I don't need feedback on that. My code speaks for itself.' Luna: So she conflated feedback on her process with criticism of her technical ability. Lucas: Exactly. And Tom realized he needed a different approach. He couldn't just say, 'You need to be more open to feedback,' because that would reinforce her defensiveness. So he did something clever. He scheduled a separate 1:1 with no agenda — just a conversation about her long-term career goals. Luna: Interesting. So he shifted the frame from evaluation to development. Lucas: Yes. He asked her, 'Where do you see yourself in three years?' She said she wanted to become a principal engineer, maybe a tech lead. Tom then said, 'Great. The principal engineers at this company are not just the best coders. They're also the people who elevate everyone around them. If you want that role, you're going to need to demonstrate that you can mentor others and accept input gracefully.' Luna: So he tied the feedback to her own ambition, not his opinion. Lucas: Right. He made it about the gap between where she is and where she wants to go. That's a much harder argument to reject. She couldn't say 'I don't need feedback' because the feedback was framed as a prerequisite for her own goal. Luna: Did it work? Lucas: It broke through the initial wall. She still pushed back a little — she said, 'I don't think I'm that bad.' But Tom had a specific example ready. He said, 'Last week in the sprint retro, you interrupted Jen when she was suggesting a refactor. I noticed Jen didn't speak again for the rest of the meeting.' That concrete observation made it real. Luna: Specificity is key. Vague feedback is easy to dismiss. 'You need to be more collaborative' — that's a nothingburger. But 'you interrupted Jen twice in the retro, and she went silent' — that's a fact. Lucas: Exactly. And Tom followed up with a small behavioral ask. He said, 'For the next two weeks, in every meeting where someone is giving you input, I want you to say two things before you respond: first, "Tell me more about that." Second, "Thank you." That's it. Just try it.' Luna: That's a really low bar. It's almost too simple, but the habit of pausing and thanking — it rewires the interaction. Lucas: It does. And after two weeks, Tom checked in. Priya admitted that the interactions felt less adversarial. She said, 'It's weird, but people seem more willing to share ideas with me now.' That was a breakthrough. Luna: So the takeaway for managers is: don't fight the 'I don't need feedback' statement head-on. Reframe the conversation around growth, use specific examples, and give a tiny behavioral experiment. Lucas: Exactly. And there's one more layer. Sometimes the 'I don't need feedback' person has a point — they genuinely are performing well. But that doesn't mean they've peaked. As a manager, your job is to show them that feedback is not a remedial tool. It's a performance multiplier. Michael Jordan had a coach. Serena Williams had a coach. The best in any field actively seek feedback. So if someone says they don't need it, you can gently ask: 'Who do you know at the top of their game who doesn't have a coach?' Luna: That's a powerful question. It reframes the entire premise. Lucas: Right. And if they still resist — if after all that, they're still closed — then you have a different problem. It's not about feedback anymore. It's about whether they're a cultural fit for a growth-oriented team. And that's a harder conversation. Luna: Have you seen cases where the person never came around? Lucas: Yes. There's a famous example from a large tech company — I won't name it — where a senior engineer was so resistant to any input that eventually the team voted with their feet. Three junior engineers quit, citing that person's behavior. At that point, the company had to let the senior engineer go, despite his technical contributions. It was a painful lesson that individual brilliance doesn't justify team damage. Luna: That's the real cost of the 'I don't need feedback' mindset. It's not just that the person doesn't grow. It's that they stunt the growth of everyone around them. Lucas: So the gentle version is: reframe, be specific, give a small experiment. The firm version is: make clear that feedback receptivity is a non-negotiable for the team's health. And if they can't accept that, they might not belong in a collaborative environment. Luna: And I think for managers listening, it's worth examining your own role too. Are you creating psychological safety? Are you delivering feedback in a way that feels like an attack? Sometimes the employee's defensiveness is a response to how you're showing up. Lucas: That's a great point. Tom, in our case study, had to look in the mirror. He realized he had been giving feedback in a fairly blunt way — just pointing out what was wrong. He shifted to a more curious tone. So if you're getting 'I don't need feedback' a lot, ask yourself: is it them, or is it me? Luna: And if it's them, you now have a playbook. Lucas: Exactly. Reframe the goal, cite a specific moment, suggest a tiny experiment. It won't work every time, but it'll work more often than arguing with someone who's already told you they don't need to hear it.