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 give a piece of feedback, something constructive, and before you've finished the sentence, the employee says, 'Yeah, I already know that.' Luna: Oof. That one lands like a door slamming shut. Lucas: It really does. And it's one of the most common — and most tricky — patterns I hear from managers. Especially new managers, because you're still building your authority, and that phrase can make you feel dismissed. Luna: So today we're drilling into that specific response: 'I already know that.' What it means, what it costs the team, and how to handle it. Lucas: Right. And I want to anchor this in something concrete. There's a 2023 piece in Harvard Business Review that looked at what they call 'the confidence-competence gap.' The researchers found that people who frequently say they already know something are actually less likely to retain new information. Their brains basically close the door. Luna: So the phrase itself can be a self-fulfilling prophecy — they think they know, so they stop listening, and then they actually don't learn. Lucas: Exactly. It's not just rudeness. It's a learning-blocking mechanism. And as a manager, your job isn't to be offended — it's to coach past the block. So let's talk about three things you can do when you hear those words. Luna: I'm taking notes. What's step one? Lucas: Step one: don't argue with the claim. If you say, 'No, you don't know that,' you've just started a fight. Instead, acknowledge it neutrally and then pivot to application. So you might say, 'Great, I'm glad you're familiar. Can you walk me through how you'd apply that in our current project?' Luna: That's smart. It shifts from 'I know' to 'show me.' And if they can't show you, they realize there's a gap. But it's not confrontational — it's a genuine request. Lucas: Exactly. And that's the second step: always test for application, not recall. Knowing a concept and being able to use it in a specific context are two different things. Most people who say 'I already know that' are recalling a definition. They haven't necessarily practiced the application. Luna: Right. I've seen this with a senior developer I managed once. He'd read every blog post on agile methodology, but when we faced a tricky sprint, he couldn't adapt the framework. He knew the words, not the moves. Lucas: That's a perfect example. And that leads to step three: normalize not knowing. If the culture on your team is that not knowing is a weakness, people will pretend they know. So you have to model the opposite. Say things like, 'I don't know, let me look that up,' or 'I've read about this, but I'm still figuring out how to apply it.' Luna: So the manager's own admission of uncertainty gives permission for others to be learners, not knowers. Lucas: Yes. And I want to be specific about the follow-up conversation, because a lot of managers ask me, 'What do I actually say in the moment?' So let me give you a script. You hear 'I already know that.' You pause, make eye contact, and say: 'Good, that saves us some time. I'm actually less interested in whether you know it and more interested in how you'd coach someone else on it. Let's role-play that for five minutes.' Luna: Oh, I love that. Because now they have to teach it, which is a much higher bar. And teaching reveals gaps fast. Lucas: It does. And it's respectful — you're treating them like a peer, not a student. But you're also getting real data on whether they actually know it. And if they stumble, you have an organic entry point for coaching. Luna: What if they say 'I already know that' in a meeting, in front of others? That's a different pressure. Lucas: It is. In public, you don't want to embarrass them. So you might say, 'Great, then you can take the lead on explaining this part to the team.' Same principle — public acknowledgment, private coaching if needed. Luna: That actually builds their credibility instead of undermining it. And if they can't explain it well, you've created a natural learning moment for the whole team. Lucas: Exactly. Now, one thing I want to flag: sometimes the employee genuinely does know the concept, but they're bored. They've heard it before, and they're signaling that they need a new challenge. That's a different root cause. Luna: So you have to diagnose: is this a learning agility problem or a motivation problem? Lucas: Right. If it's boredom, the solution isn't more coaching on the same topic — it's delegation, or a stretch assignment. But if it's a defensive reflex, you need the coaching approach we've been talking about. Luna: How do you tell the difference? Lucas: Ask a follow-up question: 'What part of this is most relevant to your current work?' If they can give a thoughtful answer, they're engaged but bored. If they brush it off with 'all of it' or 'none of it,' you're likely dealing with a defensive pattern. Luna: That's a useful diagnostic. And it helps you avoid overcorrecting — you don't want to give more coaching to someone who actually needs more autonomy. Lucas: Precisely. Now, I want to get practical about your own emotional response as the manager. When someone says 'I already know that,' it can sting. You feel dismissed, especially if you prepared that feedback. But if you react from that sting, you lose the room. Luna: So what do you do internally in that split second? Lucas: You take a breath and remind yourself: this isn't about me. This is about their learning barrier. And then you use the script. The pause itself communicates confidence. Luna: I think that's one of the hardest parts of being a new manager — not taking the pushback personally. Lucas: It is. And it's a skill you build over time. But there's a shortcut: prepare your script before you need it. If you know you're going into a feedback conversation and you anticipate this response, have the pivot ready. 'I'm glad you're familiar — let's apply it.' Luna: Preparation reduces the emotional charge. That's good advice. Lucas: Speaking of preparation — one thing that helps us prepare these episodes every week is the support from listeners. If Manager Mondays has helped you navigate a tricky conversation or think differently about a team dynamic, a couple of dollars a month is genuinely what keeps these going. You can find us at buy me a coffee dot com slash fexingo. Luna: Yeah, it really does make a difference. We keep the show ad-free, and that's because of listeners who chip in. No pressure, just if it's added value for you. Lucas: Exactly. And we're grateful either way. Now, back to that script — I want to talk about what happens after the initial conversation. Because one interaction doesn't change a habit. Luna: Right. So you need a follow-up plan. What does that look like? Lucas: You set a specific observation period. Say, 'Over the next two weeks, I'm going to watch for moments where you apply this. Let's check in on Friday and you can show me what you've tried.' That creates accountability and a concrete next step. Luna: And if they still say 'I already know that' in the check-in? Lucas: Then you escalate the conversation. You say, 'I've noticed this pattern, and I want to be direct with you. When you say you already know something, it closes off the opportunity for us to learn together. I need you to approach feedback with curiosity, not closure.' Luna: That's firmer. It names the pattern and the impact. And it gives them a clear behavioral expectation. Lucas: Exactly. At that point, it's not about the content of the feedback anymore — it's about their responsiveness. And that's a performance issue, not a coaching issue. Luna: So there's a progression: first, redirect with application. Second, if it persists, name the pattern. Third, if it still doesn't change, it becomes about their ability to grow. Lucas: That's the framework. And it works because it gives the employee multiple chances to adjust before it becomes a formal conversation. Most people will respond to the first or second intervention. Luna: But what about the person who just genuinely knows more than you on a topic? As a manager, you might not be the expert. How do you handle that without losing credibility? Lucas: Great question. In that case, you lean into your role as a coach, not a subject matter expert. You say, 'You're the expert here. I want you to teach the team what you know. Help me understand the implications for our timeline.' You're not pretending to know more — you're facilitating their expertise. Luna: That's a different dynamic. You're managing someone who actually does know, but they might be dismissive of anyone who doesn't. Lucas: Right. And in that case, the 'I already know that' is often paired with impatience. So your job is to channel that impatience into teaching. 'If you already know this, then you're the perfect person to help the rest of us understand it faster.' Luna: That turns a liability into an asset. You're leveraging their knowledge for the team's benefit. Lucas: Exactly. And it also subtly checks their humility — because if they can't explain it clearly, they might not know it as well as they think. Luna: So the 'I already know that' response, whether it comes from defensiveness, boredom, or genuine expertise, all roads lead to the same managerial move: redirect to application or teaching. Lucas: That's the takeaway. One phrase, three possible root causes, but one consistent response: 'Great, show me how you'd use it or teach it.' Luna: I think that's a script everyone can remember. And it builds a culture where knowing is less important than doing and sharing. Lucas: That's the goal. Next time you hear those words, don't hear a door slamming. Hear an invitation to pivot. And if you have your own stories of managing a 'know-it-all,' we'd love to hear them — you can reach us on LinkedIn or through the Fexingo site. Luna: Thanks for listening, and we'll see you next Monday with another manager challenge.