Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says I Was Never Told About That
Transcript
- Lucas: Luna, I want to talk about a phrase that I bet every manager has heard at least a dozen times in their career: 'I was never told about that.' Luna: Oh, I've heard it. Usually after I've sent three emails, mentioned it in a team meeting, and followed up individually. Lucas: Right. It's one of those statements that feels almost like a conversation stopper because if you push back, you sound like you're blaming the other person. But if you just accept it, you're setting yourself up for more of the same. Luna: So what do you do when you know — you know — you communicated it, but they're genuinely convinced they never got the message? Lucas: Let me start with a real case. I was talking to a regional operations manager at a mid-sized logistics firm — about 400 employees. She told me that three of her six warehouse leads consistently said they 'never knew' about policy changes or process updates. Lucas: She'd pull the email receipts, show them the thread where they were CC'd, and they'd say something like, 'Oh, I must have missed that one.' It happened enough that she started to wonder if she was the problem. Luna: And was she? I mean, maybe the communication channel wasn't working for those people. Lucas: That's exactly the right question. And in this case, she did a little audit. She found that on average, each warehouse lead received about 47 emails a day — not all from her, but from the company, from HR, from safety. So there was genuine information overload. Luna: Okay, so some of it is real. But what about the other part — the passive resistance? Because I've also seen employees use 'I was never told' as a way to avoid accountability. Lucas: Exactly. And that's the tricky part — sorting out which is which. In that same firm, two of the three leads actually started following the new process once she changed her communication method. The third one kept saying it even after she started putting sticky notes on his desk. Lucas: If today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. We keep this show ad-free because listeners like you chip in. It's a small way to say this kind of conversation matters. Luna: Yeah, honestly, if this episode helps you handle one tricky conversation, that's the whole point. And the link is simple. Lucas: So back to that third lead. The manager eventually sat down with him and asked a simple question: 'Can you tell me what you remember about the new safety checklist we discussed last week?' He couldn't say anything. Not a single detail. Luna: So it wasn't that he wasn't told — it was that he didn't process it. Maybe he wasn't listening, or maybe he was overwhelmed, but either way, he wasn't absorbing the information. Lucas: That's the distinction I want to make today. There are really three buckets when someone says 'I was never told.' Bucket one: they genuinely missed it — information overload, wrong channel, bad timing. Bucket two: they heard it but didn't engage with it — passive intake, no mental ownership. Bucket three: they're using it as a shield to avoid responsibility. Luna: And the fix is different for each bucket. What did the manager do for bucket three? Lucas: She introduced something I call the 'receipt check.' Before a new policy or deadline goes into effect, she asks the employee to paraphrase back what they understand. Not 'Do you have any questions?' but 'Can you walk me through your next steps based on what we just discussed?' Lucas: That shifts the burden from 'Did you tell me?' to 'Do I own this?' And if they can't paraphrase, you know right then that the message didn't land — and you can address it in the moment. Luna: That's powerful because it also gives the employee a dignified way to say, 'Actually, I didn't catch that,' without feeling defensive. Lucas: Right. The second tool is what I call a 'decision journal.' It's a shared document — could be a simple Google Doc — where every key decision, policy change, or process update gets logged with a date and a brief summary. The manager writes it, but the employee is expected to check it once a day. Lucas: It sounds basic, but for the overwhelmed employee — bucket one — it gives them a single source of truth they can refer back to. No more 'I must have missed that email.' It's all there. Luna: And for bucket two, the passive listener, does that help? Lucas: It can, but you usually need a third tool — the 'pre-mortem.' Before you share a new piece of information, you briefly explain why it matters to them personally. Not just what the change is, but what happens if they don't act on it. Luna: Give me an example. Lucas: Sure. Instead of saying, 'We're updating the inventory reconciliation process starting next Monday,' you say, 'We're updating the inventory reconciliation process starting next Monday because last quarter, two mis-shipments cost us $14,000 in credits. If we all follow this new checklist, we can prevent that. Here's how it affects your shift specifically.' Luna: Now they have a reason to care. It's not just another email — it's a story with a stake. Lucas: Exactly. And here's the key: after you do that, you still do the receipt check. 'What's your understanding of why we're making this change and what you'll do differently?' Luna: So you're layering the motivation on top of the instruction. I like that. But what about the manager who's thinking, 'I don't have time to do this for every single piece of communication'? Lucas: Fair point. And you don't have to. You reserve these tools for the employees who consistently say 'I was never told.' For everyone else, the standard communication works fine. But for the repeat offenders, you invest the extra five minutes upfront to save an hour of follow-up later. Lucas: The manager I mentioned — the one at the logistics firm — she used the decision journal and the receipt check with her three leads. Within two weeks, two of them stopped saying they weren't told. The third one? He eventually admitted he'd been tuning out because he didn't think the updates applied to him. Luna: Oh, that's interesting. So for him, it was less about communication and more about engagement. He didn't see himself as part of the loop. Lucas: Bingo. And that's a different conversation entirely — about role clarity and ownership. But at least she knew what she was dealing with. Before the receipt check, she was just guessing. Luna: So the takeaway for me is: don't assume malice or laziness. Use a framework to diagnose which bucket your employee is in, then apply the right tool. Lucas: Exactly. And one more thing — when you do have that conversation, avoid the finger-wagging tone. Don't say, 'I sent you that email on Tuesday.' Instead say, 'I want to make sure we're on the same page. Can you tell me what you heard about the new process?' Luna: It's subtle but it changes the dynamic from accusation to collaboration. And if they still say 'I wasn't told,' you can gently say, 'Let's check the decision journal together and see what's there.' Lucas: Right. No shaming, just a shared reference point. Over time, the employee learns that 'I was never told' isn't a get-out-of-jail-free card — but also that you're willing to meet them where they are. Luna: That's the balance every manager needs to strike. Accountability without alienation. Lucas: And that's what we're aiming for. Next week, we'll look at another common phrase managers dread — 'That's not how we used to do it.' Luna: Oh, that's a good one. See you next Monday. Lucas: Take care, everyone.