Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Says I Already Know That
Transcript
- Lucas: You're in a one-on-one with a direct report. You're walking through a new process or a piece of feedback, and before you even finish your sentence, they say, 'Yeah, I already know that.' Maybe they say it with a shrug, maybe with a little edge. And now you're stuck — because if they already know it, why aren't they doing it? And if you push back, you risk sounding like you're accusing them of lying. Luna: I've been on both sides of that conversation. As a manager, it's frustrating. As the employee, I've definitely said it when I felt like I was being told something obvious — or when I was embarrassed I didn't know it and wanted to save face. Lucas: Exactly. That's the key insight. The phrase 'I already know that' is rarely about the information itself. It's about identity. The person is protecting their sense of competence. And if you, as their manager, take it at face value, you miss the real issue. Luna: So what do you do in the moment? Do you call it out, or let it slide? Lucas: I think there's a middle path. I've been reading some work by Amy Edmondson at Harvard — she writes about psychological safety. One of her points is that people shut down learning when they feel their status is threatened. So the first move is to lower the threat. You don't say, 'Well you're not doing it.' You say something like, 'Great, so you've got a head start. What's your take on how we should apply it here?' Luna: That's clever. You're not challenging their claim; you're inviting them to demonstrate their knowledge. If they actually know it, they can show you. If they don't, they'll have to clarify. Lucas: Right. And that's step one. Step two is to get curious about the gap between knowing and doing. Because a lot of times, people know the concept but haven't translated it into habit. So you might follow up with, 'I'd love to hear how you've been applying it — what's working, what's tricky?' That shifts the conversation from proving to problem-solving. Luna: And if they still resist? If they say something like, 'No, I know it, it's fine'? Lucas: Then you might need to name the pattern. But do it with empathy. You could say, 'I notice that when I bring up a new approach, you often say you already know it. And maybe you do. But I also want to make sure we're on the same page, because if there's something you're unsure about, this is a safe space to ask.' That directly addresses the psychological safety piece. Luna: That's a good script. It gives the person an off-ramp. They can admit they don't know without losing face. Lucas: Exactly. And I'll be honest — this takes practice. I've managed engineers who would say 'I know' to everything, and my first instinct was to prove them wrong. But that escalates. The goal isn't to win a debate; it's to get the work done and help them grow. Luna: What about when the behavior is a symptom of something deeper? Like, the person is bored or burned out? Lucas: That's a great point. Sometimes 'I already know that' means 'I've been doing this too long and I'm checked out.' If it's a pattern, you might need to explore whether the role is still challenging them. I had a team member once who started saying that about everything — turned out he wanted more responsibility but didn't know how to ask. Once we gave him a stretch project, the defensiveness disappeared. Luna: So the phrase can be a signal for a different conversation entirely. Lucas: Right. And that's the third step: look for the root cause. Is it ego? Is it fear? Is it boredom? Is it that the person genuinely knows the material but disagrees with the approach? Each one requires a different response. But the common thread is that you don't take the statement at face value. Luna: I think a lot of first-time managers hear 'I already know that' and think they're being disrespected. But reframing it as a communication breakdown — or a cry for help — makes it less personal. Lucas: Absolutely. And if today was actually useful to you — if you've got a team member who does this and you're thinking about how to handle your next one-on-one — this is exactly the kind of practical help we try to offer every week. The way we keep this show ad-free and focused on real scenarios is listener support. If you find value in it, you can head to buy me a coffee dot com slash fexingo. No pressure, just a way to keep the conversation going. Luna: Yeah, even a small contribution helps us invest in better research and keep delivering episodes like this. We really appreciate it. Lucas: Alright, back to the tactics. One more thing I want to mention: timing. If the 'I know' happens in a group setting, handle it differently. In a team meeting, you don't want to embarrass someone. So you might say, 'Great, let's hear from someone else too' and then follow up one-on-one later. Luna: That's smart. Preserve their reputation publicly, address the behavior privately. Lucas: Exactly. And in that one-on-one, you can use the same framework: acknowledge their knowledge, get curious about application, and explore what's really going on. Over time, you build enough trust that they stop needing to say 'I know' because they trust that you already respect their competence. Luna: So the goal is to make the phrase unnecessary. If they feel safe and challenged, they won't need to defend themselves. Lucas: Right. And that's really the heart of management: creating an environment where people can say 'I don't know' without fear. Because that's where real learning happens.