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: So we've made it to episode 100 of Manager Mondays, and I wanted to tackle something I hear about constantly from first-time managers. Luna: Give me a hint — is it the employee who responds to everything with 'I already know that'? Lucas: Exactly. It's such a specific gut-punch, isn't it? You're giving feedback, or explaining a new process, and before you finish the sentence, you get that flat 'Yeah, I know.' It shuts down the conversation instantly. Luna: Right, and it's different from someone who genuinely knows their stuff. This feels dismissive, like they're closing the door before you can even walk through it. Lucas: There's a 2025 Gallup study that found 42 percent of managers say this behavior — specifically the 'I already know' reflex — is one of the top three things that erodes their trust in a team member. Not the person's competence, but the dynamic itself. Luna: Forty-two percent? That's huge. So this isn't just an annoying quirk — it's a trust killer. Lucas: Exactly. And here's the thing — when I dig into it with managers, they usually assume the employee is arrogant or resistant. But often, it's actually a defense mechanism. The employee feels insecure about not knowing, so they preemptively claim they already do. Luna: Huh, so it's almost like a verbal flinch. They're protecting themselves from feeling exposed. Lucas: Yes. And once you see it that way, it changes how you respond. Instead of getting frustrated, you can use a technique I call the 'confirmation loop.' It's a three-sentence framework that asks the employee to demonstrate their understanding — not just claim it. Luna: Okay, walk me through it. How does it work in practice? Lucas: First sentence: you acknowledge their familiarity. 'Great, you're already up to speed on this.' Second sentence: you frame it as alignment, not teaching. 'Just so we're on the same page, could you summarize how you see this applying to the current project?' Third sentence: you make it a low-stakes ask. 'I'd love to hear your take on the key steps.' Luna: So you're not challenging them — you're inviting them to prove it. If they really know, they'll give a coherent summary. If they don't, they'll stumble, and you can step in naturally. Lucas: Exactly. And I've seen this work. A product manager at a mid-sized SaaS company — I can't name the company, but she had a senior engineer who would say 'I know' to almost every feature spec she presented. She started using the confirmation loop for six weeks. By week four, the 'I know' responses dropped by 80 percent. Luna: Eighty percent? That's not subtle. So the engineer either realized he didn't actually know, or he learned that claiming knowledge meant he'd have to prove it. Lucas: Both, probably. And the bonus was that the quality of their one-on-ones improved. They moved from defensive posturing to actual problem-solving. Luna: I love that. But let me push back a little — sometimes the manager is the problem. Harvard Business Review published a study a few years ago showing that managers overestimate how clearly they communicate. Sixty-seven percent of managers thought they were clear, but only 23 percent of employees agreed. Lucas: That's a huge gap. So you're saying the 'I know' might be a response to the manager repeating themselves without adding new value. Luna: Right. If you start every meeting by re-explaining something they've heard three times, 'I know' is actually a rational response. It's the employee saying, 'You're wasting my time.' Lucas: That's a fair point. So part of managing this is honestly auditing your own communication. Are you giving them new context, or are you just reciting what they already heard in the last email? Luna: And if you are repeating yourself, own it. Say, 'I know I've mentioned this before, but I want to make sure we're aligned given the deadline shift.' That frames it as collaboration, not instruction. Lucas: Right. And that actually ties into something I've been thinking about — the difference between 'I know' as a sign of expertise versus a sign of resistance. How do you tell them apart? Luna: I think the giveaway is follow-through. The expert who says 'I know' will then do the thing correctly and independently. The resister who says 'I know' will either not do it, or do it poorly and blame the instructions. Lucas: So you watch what happens after the conversation. If they deliver, great. If they don't, then you have a pattern to address — not just the phrase, but the gap between their claim and their output. Luna: Exactly. And that's where you can have a real coaching conversation. 'Last week you said you already knew the process, but the deliverable missed these three steps. Let's figure out what's getting lost.' Luna: Hey Lucas, before we go further — this is the kind of practical advice that makes me think about how much value this show gives me every week. And honestly, if today's episode was worth a coffee to you, the listener, it'd mean a lot if you supported us. Lucas: Yeah, we keep Manager Mondays ad-free, and listener support is what makes that possible. If you've ever gotten a tip here that helped you handle a tough conversation, you can find us at buy me a coffee dot com slash fexingo. Luna: No pressure at all — just a simple way to say this is worth your time. And it goes directly to keeping the show going. Lucas: Alright, back to the 'I know' dynamic. Another angle I want to explore is when the behavior is actually a sign of a deeper cultural problem. Luna: What do you mean? Lucas: If multiple team members start saying 'I know' to the same manager, it might mean that manager is over-explaining or micromanaging. But if one employee says it to everyone — peers, other managers, even leadership — it's likely a personality pattern, not a situational response. Luna: And that pattern can be toxic, especially if the employee is otherwise high-performing. Because they might actually deliver, but they make everyone around them feel dismissed. Lucas: That's the hardest case. You have a star contributor who's also a trust-killer. In that scenario, I think the manager has to have a direct, private conversation. Not about the phrase, but about the impact. Luna: How do you phrase that without making them defensive? Lucas: Something like: 'I know you're highly competent, and I respect that. But when you respond with 'I know' before I finish explaining, it makes it hard for me to know if we're truly aligned. Could we try a different rhythm where I share the context first, and then you confirm?' Luna: That's good — it focuses on your experience as the manager, not on their behavior being wrong. And it offers a specific alternative. Lucas: And if they're open to it, you can even agree on a code word. I've had managers use something playful like 'confirmation loop' as a shorthand. The employee knows that when the manager says that, they need to summarize their understanding. Luna: That builds a shared language. And it actually strengthens the relationship, because now you have a way to call out the behavior without it feeling like an accusation. Lucas: I think there's also a place for letting some 'I knows' slide. If the employee is consistently hitting their numbers and collaborating well otherwise, you don't need to fix every single interaction. Luna: Right, pick your battles. If the phrase is the only friction, and the work is solid, maybe that's a personal annoyance you learn to live with. Lucas: But if it's part of a broader pattern of dismissiveness — interrupting, not taking feedback, blaming others — then it's a symptom you can't ignore. Luna: So to tie it together: start by assuming good intent and checking your own clarity. Use the confirmation loop to invite demonstration. Watch for follow-through. And if it's consistent, have a direct conversation about impact. Lucas: That's a solid framework. And I'll add one more thing — celebrate when they stop saying it. If you've been using the loop for a few weeks and the employee starts saying 'I've got that, here's my plan,' acknowledge it. 'I really appreciate how you're communicating now.' Luna: Positive reinforcement works. And it shows you're paying attention to the change, not just the problem. Lucas: Alright, next episode we'll dig into managing the employee who always says 'That's not my responsibility' — and no, we haven't done that one yet. Thanks for being here for episode 100.