Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Always Says I Already Know That
Transcript
- Lucas: Alright, let's talk about the employee who responds to every piece of direction with some version of 'I already know that.' It sounds simple, but it's actually one of the more subtly corrosive phrases in a team. Luna: It can stop a conversation cold. You're trying to explain a process or give feedback, and suddenly you feel like you're being dismissed. Lucas: Exactly. And the instinct is to assume it's arrogance or a know-it-all attitude. But in my experience, it's often something else. I worked with a product manager at a mid-sized SaaS company—let's call her Priya—who said this constantly. Every time her lead suggested a framework or a workflow, she'd say 'Yeah, I already know that.' Luna: What was really going on with her? Because it sounds like she was shutting down learning before it even started. Lucas: Turned out, she was terrified of being perceived as inexperienced. She'd been hired into a senior role, and she felt like she had to prove she belonged every single day. Saying 'I already know that' was a shield—it preempted any suggestion that she might not know something. But the cost was that her team stopped bringing her new ideas. Luna: So the defense mechanism actually created the opposite of what she wanted—it made her look less collaborative, not more competent. Lucas: Right. And her lead made it worse by pushing back harder, saying things like 'Well, if you already know it, then why aren't you doing it?' That just escalated the cycle. Priya dug in deeper. Luna: So what's the alternative? How do you break that loop without making the person feel attacked? Lucas: There's a technique I've seen work really well. It's called the 'knowledge check'—but not the way it sounds. Instead of questioning whether they really know it, you flip the frame. You say something like: 'Great, I'm glad you're familiar with this. Can you help me understand how you see it applying to our current project? I want to make sure we're aligned.' It acknowledges their knowledge while inviting them to demonstrate it in a specific context. Luna: That's smart—it turns a potential confrontation into a collaborative check-in. And it gives them a chance to prove their competence on their own terms. Lucas: Exactly. And if they can't articulate the application, that's your opening to fill in the gap without them losing face. You say, 'That's close—here's one piece that might be new.' The key is to assume positive intent. Most of the time, they're not trying to be difficult; they're trying to protect themselves. Luna: Has that worked in practice with someone like Priya? Lucas: It did. Her lead started using that approach—'Priya, you've got experience with agile sprints, walk me through how you'd structure this one.' And over a few weeks, she started actually asking questions instead of shutting down. The defensiveness softened because she felt her expertise was being recognized, not tested. Luna: So it's about shifting from 'I'm telling you something' to 'Let's build this together.' That makes sense, but what about the team dynamic? If one employee has a pattern of saying 'I already know that,' it can make other team members hesitant to share ideas. Lucas: That's a real risk. In Priya's case, the team started routing suggestions through the lead instead of talking to her directly. So the lead had to address that, too. He set up a norm in team meetings: 'No phrase is off limits, but let's try to start responses with curiosity instead of certainty.' He modeled it himself by saying 'I hadn't thought of that' or 'Tell me more' when someone brought up an idea. Luna: Leading by example. And I imagine that over time, Priya started mirroring that language because she saw it was safe to do so. Lucas: Exactly. And it's worth noting there's a difference between occasional defensiveness and a chronic pattern. If it's happening in every one-on-one and the person genuinely does know the material, you might actually have a delegation problem. Maybe they're bored and need more challenging work. But that's a separate conversation. Luna: Right—sometimes 'I already know that' is a signal that you're micromanaging. If they're right, and they do know it, then why are you telling them? So the manager has to check their own behavior too. Lucas: Huge point. The phrase can be a mirror. I've had to ask myself: Am I giving this person information they actually need, or am I just covering my own bases? If it's the latter, I should just send the documentation and say 'Let me know if anything is unclear.' Luna: So we've got the knowledge check technique, setting team norms, and self-reflection. Is there a specific script you'd recommend for the moment it happens in a one-on-one? Lucas: Yeah. Let's say you're giving feedback on a report, and they say 'I already know that.' Instead of reacting, pause, then say: 'Okay, I appreciate that. Since you're familiar, can you walk me through how you incorporated that into your analysis? I want to see your thought process.' That does two things: it takes the sting out, and it gives you concrete evidence of whether they actually applied the knowledge. Luna: And if they can't walk you through it, then you have a foundation for a coaching conversation without calling them out. Lucas: Exactly. 'I noticed there's a gap between what you said you knew and what the analysis shows. Let's figure out together what's missing.' That keeps it collaborative. And over time, the phrase 'I already know that' tends to fade because the employee sees that it doesn't protect them—it actually creates more work. Luna: That's a powerful shift. One thing I've noticed is that this can be especially common with junior employees who are insecure, or with senior hires who feel they have to justify their salary. The motivation is different, but the solution is similar. Lucas: Right. For a junior person, it might be fear of looking dumb. For a senior person, it might be fear of being seen as outdated. In both cases, you want to create a culture where not knowing is okay—where the response to 'I don't know' is 'Great, let's learn it together.' That's the ideal. But you can't get there if you're constantly battling that defensive phrase. Luna: And that's really the core of this episode—it's not about 'managing' the phrase, it's about understanding the person behind it. Because the phrase is just a symptom. Lucas: Exactly. And if we've helped you see your own team a little differently, or given you something to try in your next one-on-one, that's the whole point. We deliberately don't run ads on these episodes—it's a choice we made to keep the content clean and focused. If you want to support that, the link is buy me a coffee dot com slash fexingo. No pressure, just an option if you find value here. Luna: Yeah, it's a small way to keep this going without any commercial noise. And we really appreciate everyone who's ever chipped in. Lucas: So back to the topic. One last thing I'd add: if you're a first-time manager and you're dealing with this, don't beat yourself up if it takes a few tries. The first time you use the knowledge check, it might feel awkward. But it works, and it gets easier. Luna: And your team will notice that you're trying to connect rather than correct. That builds trust over time. Lucas: Exactly. So next time you hear 'I already know that,' take a breath, assume good intent, and try the collaborative approach. You might be surprised how quickly the dynamic shifts. Luna: Great advice. We'll see you next Monday.