Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says I Told You So
Transcript
- Lucas: So you've got a team member who was right about the Q3 forecast, right about the vendor switch, right about the client's reaction to the new pricing. And they make sure everyone knows it. Luna: The 'I told you so' employee. Yeah, I've had one of those. It's exhausting because they're often smart and their calls are good, but the way they deliver it just grates. Lucas: Exactly. And as a manager, you're in a bind. You don't want to punish accuracy, but you can't let someone turn every retrospective into a victory lap. It kills psychological safety. Other people stop offering their own opinions because they're afraid of being wrong publicly. Luna: So how do you handle it? Do you address the behavior directly, or try to redirect it? Lucas: I think you start by understanding the root. Often, this isn't pure arrogance. It's insecurity. The person feels that if they don't claim credit for their correct calls, nobody will notice their contribution. They're worried about being overlooked. Luna: That's a good point. I had a data analyst once who was brilliant at spotting trends, but every Monday meeting she'd say, 'Well, I predicted this last month.' It annoyed everyone, but when I talked to her one-on-one, she confided that she'd been passed over for a promotion before and felt she had to advocate for herself. Lucas: Right. So the behavior is a symptom. The real need is recognition and a sense of being valued. Once you know that, you can give them a healthier outlet. For example, you could create a space where predictions are recorded formally — like a team forecast log — and then review them monthly without attaching names. Luna: That's smart. It removes the need for the individual to claim credit because the data speaks for itself. And it turns the 'I told you so' into a team learning exercise. Lucas: Exactly. I saw this work beautifully at a previous company. We had a team of senior analysts who were all kind of competitive about being right. The VP of Analytics set up a system where every quarter, each person submitted three predictions for the business, and then we scored them anonymously. The best predictor got a small prize, but more importantly, the conversation shifted from 'I was right' to 'What did we learn from the misses?' Luna: And that probably helped the whole team improve their forecasting. Lucas: It did. The accuracy of the group's predictions went up about 20 percent year-over-year. But the cultural shift was even bigger. People started saying things like, 'My mental model was off because I didn't account for this factor,' which is a much more collaborative way to learn. Luna: So you're not trying to shut down the person's need to be right. You're just giving them a more productive channel for it. Lucas: Precisely. And if that doesn't work, then you do need a direct conversation. But I'd frame it around impact, not intent. Say something like, 'When you highlight that you predicted the outcome, it sometimes discourages others from sharing their perspectives. I want everyone to feel safe contributing, even if they're wrong.' Luna: That's a good script. It's not accusatory. It's about team dynamics, which is your job as manager. Lucas: Right. And then you can offer them an alternative. Say, 'Next time, could you share your reasoning in the moment, before the outcome is known? That way we all benefit from your insight proactively.' That turns the behavior from retrospective gloating into forward-looking contribution. Luna: I love that. It's a reframe. Instead of being the person who says 'I knew it,' they become the person who says 'Here's what I think will happen, and here's why.' Lucas: Exactly. And if they do that, you as the manager should recognize that publicly. Thank them for their prediction and highlight how it helped the team. That meets their need for recognition in a positive way. Luna: What about the situation where the person is actually wrong a lot, but still says 'I told you so' for the few things they get right? Lucas: That's tougher. You might need to gently point out the pattern. In a one-on-one, you could say, 'I noticed you called the vendor delay correctly, and that was valuable. I also noticed that in three other cases last quarter, the outcome was different from your prediction. How can we improve our forecasting process together?' Luna: So it's not about shaming them for being wrong, but about making it a shared learning exercise. Lucas: Exactly. And sometimes the person isn't even aware that they're doing it. A former colleague of mine had a habit of starting sentences with 'I said that months ago.' He was a great strategist, but people stopped wanting to brainstorm with him. After a few gentle nudges, he started catching himself and saying, 'This reminds me of a pattern I noticed earlier.' Same insight, but the tone was completely different. Luna: That's a great example. It's a small language shift, but it changes how the team perceives him. Lucas: Absolutely. And as a manager, you can model that language yourself. When you make a correct call, don't highlight it. Instead, say something like, 'The data suggested this outcome, and I'm glad we acted on it.' That sets an example of humility. Luna: I think the real challenge is when the employee's 'I told you so' is accompanied by a kind of schadenfreude — like they're almost happy things went wrong so they could be right. Lucas: That's a different level. That's a culture issue. If someone seems to take pleasure in the team's failure to validate their own prediction, that's not just a habit; it's a sign of a deeper misalignment with the team's goals. That might require a more serious conversation about values and whether they're committed to the team's success as a whole. Luna: Right. Because at that point, it's not about recognition anymore. It's about them versus the team. Lucas: Yeah. And that's a conversation about whether they're willing to shift their perspective. You can ask directly, 'What would it take for you to feel equally invested in the team's success, even when your prediction doesn't come true?' Luna: That's a powerful question. Lucas: But I think for most people in this category, it's not that extreme. It's more about habit and a bit of ego. And with a good system and direct but kind feedback, you can turn them into a contributor who shares their foresight generously, not smugly. Luna: And along those lines, if we've helped you think through a management challenge like this, or given you a framework to handle a difficult conversation, a small number of listeners already help keep this show going through buy me a coffee dot com slash fexingo. It means we can keep these episodes free and without ads. Lucas: Yeah, we really appreciate that. It allows us to focus on real, specific advice rather than trying to sell you something. So thanks if you're one of those people. Luna: Alright, back to our topic. One more thing I've seen work is to create a 'predictions board' in your team chat or project management tool. People post their forecasts at the beginning of a project, and then after the fact, you review them. It's a visual reminder that predictions are hypotheses, not judgments. Lucas: That's a great tactical tip. It makes prediction a team sport. And if you do it consistently, the person who used to say 'I told you so' might start saying 'I wonder if this will play out the way I expect.' And that's a much healthier team dynamic. Luna: So to wrap up: understand the root need, create an alternative outlet, give direct feedback on impact, and model humility yourself. Lucas: That's a solid framework. And remember, the goal isn't to silence the person who's often right. It's to make sure their insight lifts the whole team instead of alienating them.