Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Coach an Employee Who Always Says I Know
Transcript
- Lucas: So you give a piece of coaching to a direct report — something you think is pretty straightforward, maybe even helpful — and they look you in the eye and say, 'Yeah, I know.' Luna: Oof. That two-word wall. I've been on both sides of that exchange. Lucas: Right. And as a manager, it's maddening because the conversation just stops. You've been dismissed without the conversation actually ending. So today I want to talk about the 'I know' reflex — what it really means, and how to coach through it. Luna: Let me guess — it's not about arrogance as often as we think. Lucas: Exactly. I spent a lot of years assuming 'I know' was a power move. But when I started digging into it — and I've seen this echoed in research on defensive communication — it's usually anxiety or perfectionism in disguise. The person hears your feedback as an accusation that they didn't know, and they rush to prove their competence. Luna: So they're basically saying, 'I'm not the kind of person who needs this feedback.' Which is a protection of identity, not a rejection of the content. Lucas: That's exactly it. And once you reframe it that way, the coaching approach changes completely. I want to walk through a framework I've seen work really well. It comes from a VP of Engineering at a mid-stage SaaS company — about 200 people, they were scaling fast — who had a senior developer, really talented, but his 'I know' habit was starting to erode trust with the junior developers he was supposed to mentor. Luna: Because the juniors felt like they couldn't offer suggestions without getting shut down. Lucas: Exactly. So the VP sat him down and said, 'I want to talk about something I've noticed. When someone shares an idea or a suggestion, you often respond with "I know." And I think that's costing you something.' Notice he didn't say 'you have a problem' — he named the behavior and its impact. Luna: That's step one: label the pattern, not the person. Lucas: Yes. And step two was actually more interesting. The VP and the developer agreed on a code word. Whenever the developer caught himself about to say 'I know,' or whenever the VP heard it, they'd say 'reset' — just a neutral signal. That took the shame out of it. Luna: So it becomes a game, almost. A shared awareness instead of a confrontation. Lucas: And then step three was the real coaching move. The VP shifted from giving advice to asking questions. Instead of saying, 'Hey, when you're reviewing a junior's code, try asking them what they considered before writing it that way,' he'd ask, 'What approach do you think would help a junior feel more comfortable sharing their thought process?' Luna: Ah, Socratic coaching. You're making them own the solution. Lucas: Which is harder to brush off with 'I know,' because you haven't been told anything — you've been asked. The developer couldn't say 'I know' to a question. He had to actually think. And over time, the VP said the reflex faded because the developer started to see that his job wasn't to prove he already knew everything; it was to help other people know more. Luna: That's a beautiful reframe. Let me push on this a little, though — what about the employee who is genuinely arrogant? Not anxious, not perfectionist, but actually believes they don't need coaching? Lucas: That's a real category, and the approach is different. With genuine arrogance, the 'I know' is often accompanied by a dismissive tone or a roll of the eyes. In that case, you need to name the impact more directly: 'When you say "I know" in that tone, it stops the conversation and makes people feel like their input isn't valued.' And then you have to be willing to set a boundary: 'If this pattern continues, it will affect your opportunities for leadership roles.' Luna: So you're escalating from coaching to performance management. Lucas: Right. But I'd say that's maybe 20 percent of cases. The other 80 percent are the anxious perfectionists. And for them, the key is to create a low-stakes space where not knowing is okay. One thing that helps is to normalize your own ignorance. Say, 'I didn't know that until last year,' or 'I still struggle with this.' Luna: It lowers the threat level. If the manager can admit not knowing, the employee doesn't have to defend knowing everything. Lucas: Precisely. And one more tactical thing: if you hear 'I know' in a one-on-one, you can just pause. Silence is uncomfortable. Often the person will fill it by actually engaging with what you said. You can say, 'Okay, help me understand what your thinking was there,' and then wait. Luna: That's a power move, but a gentle one. You're not challenging their knowledge, you're inviting them to share it. Lucas: Honestly, this whole topic reminds me why we keep Manager Mondays ad-free. If today's episode helped you think about a conversation you need to have, that's the link — buy me a coffee dot com slash fexingo. It's just a small way to keep the show independent. Luna: Yeah. And we mean it when we say a coffee's worth. That literally funds the hosting and the time we spend researching these frameworks. Lucas: So the key takeaway: don't fight the 'I know.' Understand it. Label the pattern, use questions instead of statements, and create safety for not knowing. That's how you turn a wall into a door. Luna: I love that. And I want to add one more thing — there's a great piece by Ed Batista, the executive coach, where he talks about 'protective reflexes.' He says these behaviors are like a turtle pulling into its shell. The shell isn't the problem; the turtle just needs to feel safe enough to come out. Lucas: That's exactly the framing. And as a manager, you're not trying to crack the shell — you're trying to warm the environment so the turtle emerges on its own. Luna: So next time you hear 'I know,' take a breath. Ask a question. And remember that the person on the other side is probably more scared of being seen as incompetent than they are of you. Lucas: That is the mic-drop line. I'm Lucas. Luna: I'm Luna. Lucas: And this has been Manager Mondays. See you next week.