Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / The Hindsight Bias Trap in Office Politics
Transcript
- Lucas: So let me start with a number that I find genuinely unsettling: in one study, when people were asked after an event to recall their original prediction, over eighty percent of them remembered being more confident than they actually were at the time. Luna: That's hindsight bias in action — the 'I knew it all along' effect. Lucas: Exactly. And in office politics, this is a weapon. It's how managers assign blame for failures they claimed were unpredictable, and how colleagues take credit for outcomes they didn't actually foresee. Luna: I've definitely been on the receiving end of that. A project I led had a hiccup — a vendor missed a deadline — and in the postmortem, my boss said, 'Well, we all knew that vendor was risky.' But he had signed off on the vendor selection without a word. Lucas: That's the classic move. Hindsight bias lets people rewrite history to make themselves look prescient and shift the cost of uncertainty onto someone else. And it's not just malicious — our brains do it automatically. The problem is that it kills learning. Luna: Because if everyone already 'knew' the outcome, why bother analyzing what actually went wrong? Lucas: Right. You get superficial lessons — 'we should have seen that coming' — instead of real structural fixes. Let me give you a concrete example from a Fortune 500 retailer. A couple years ago, they launched a new pricing algorithm intended to boost margins on seasonal inventory. The launch was a disaster: sales dropped nine percent in the pilot region. Luna: Ouch. Who got the blame? Lucas: The mid-level product manager who championed the algorithm. Senior leaders pointed to the nine percent drop and said, 'We had reservations about the model's sensitivity from the start.' A formal review was initiated, and that manager's career took a real hit. Luna: But something later came out? Lucas: Four months after the review, an engineer discovered that a data feed had been misconfigured during the pilot. The algorithm was getting price signals from the wrong inventory category — basically, it was optimizing for winter coats in a region that was stocking summer gear. The model itself was fine. Luna: So the nine percent drop had nothing to do with the algorithm's logic — it was a data pipeline bug. Lucas: Exactly. But by the time that came out, the manager had already been reassigned, and the narrative that 'the algorithm was flawed' was locked in. The company didn't go back and revisit the postmortem. Hindsight bias had already done its damage. Luna: And ironically, the real lesson — check your data feeds before launch — was lost because everyone thought they already knew the lesson. Lucas: So how do you fight this? I think there are three concrete tactics. The first is the decision journal. Before a major decision — hiring someone, approving a budget, launching a feature — write down your prediction, your confidence level, and the reasoning. Date it. Then, when the outcome is known, compare. Luna: I've started doing that for hiring decisions. I write down: 'I think this candidate will ramp in three months, confidence seventy percent.' Later, I can look back and see where my calibration was off. Lucas: That's exactly it. The journal creates a record that's immune to retrospective rewriting. Over time, you can track your own accuracy and adjust. It's humbling — most people discover they're less accurate than they thought. Luna: Okay, what's the second tactic? Lucas: The premortem. Before a project launches, gather the team and say: 'It's six months from now, and this project has failed spectacularly. What happened?' List all the reasons. That forces people to surface risks they might otherwise dismiss because they 'feel' good about the plan. Luna: And those risks become part of the official record, so later no one can claim they 'knew' the risk but didn't speak up. Lucas: Right. A premortem also reduces the hindsight bias that emerges after a failure — because you've already named the possible failure modes. When one of them actually happens, you don't get that 'we should have known' retroactive shock. You say, 'We identified this risk. Now we execute the contingency.' Luna: That also protects the team psychologically. It normalizes failure as something to plan for, not something to assign blame over. Lucas: Exactly. And that brings me to the third tactic: the no-fault retrospective. After any significant outcome — good or bad — run a review that explicitly forbids assigning blame. The rule is: assume everyone acted in good faith with the information they had at the time. Then ask: what in the process allowed this outcome to happen? Luna: That's harder than it sounds. People want to know who dropped the ball. Lucas: Sure, but if you focus on process, you find system-level fixes. The retailer example: a no-fault review would have caught the data feed issue much sooner, because the focus would have been on verifying inputs, not on evaluating the product manager's judgment. Luna: So the three tactics are: decision journal, premortem, and no-fault retrospective. I want to add one more from my own experience — the base rate check. Lucas: Tell me. Luna: When you catch yourself thinking 'I knew that would happen,' pause and ask: what's the base rate of this outcome in similar situations? For example, if a sales rep misses quota, your gut might say 'I knew he was lazy.' But the base rate of missed quotas in that territory might be thirty percent. Suddenly your 'I knew it' feels less like insight and more like statistical noise. Lucas: That's powerful because it forces you to compare your gut against actual frequency, not just your memory. And our memories are terrible at base rates — we remember the vivid failures and forget the mundane successes. Luna: And if we're talking about office politics, the base rate check is especially useful when evaluating other people's calls. A colleague's bad decision looks obvious in hindsight, but if you check the base rate — how often does that kind of decision succeed? — you might find they were playing reasonable odds. Lucas: That's a real generosity move. It also protects you from being the person who always 'knew' things after the fact — that person gets tuned out. People start to resent the Monday-morning quarterbacking. Luna: And on that note — I think this is a good moment to mention something. If these conversations help you navigate your own workplace dynamics, and you've gotten some value out of them, there's a simple way to support the show. Lucas: Yeah, we keep the podcast ad-free, and listener support is what makes that possible. A couple of dollars a month genuinely makes a difference — it covers hosting, editing, and keeps us going. Luna: If you've ever used one of these tactics and it helped, consider tossing a few bucks into the tip jar. It's buy me a coffee dot com slash fexingo. Lucas: And even if you don't, we're glad you're here. Now, back to the tactics — I want to push on one nuance. The decision journal works great for individual decisions, but how do you scale it to a team? Luna: That's a good question. I've seen teams keep a shared 'prediction log' for major milestones. Before each quarter, everyone writes down three predictions about their projects — with confidence levels. Then at the end of the quarter, the team reviews them together. Lucas: That's a team-level decision journal. And it has the added benefit of surfacing disagreements before they become political. If two people have opposite predictions with high confidence, you can explore the assumptions driving that gap. Luna: Exactly. And when you do that, hindsight bias has less room to operate, because you've captured the uncertainty in real time. Lucas: There's also a personal dimension here. If you suspect you're being unfairly judged by hindsight bias — say, in a performance review — you can proactively provide your decision journal or your premortem notes. It's hard for a manager to say 'you should have known' when you have a written record showing you flagged the risk and it was accepted. Luna: That's a strategic move. It reframes the conversation from 'why didn't you foresee this?' to 'we accepted this risk together.' Lucas: Exactly. And that's the core of office politics: managing perceptions and narratives. Hindsight bias is a narrative weapon, but with the right tools, you can disarm it. Luna: So to wrap up: keep a decision journal, run premortems, hold no-fault retrospectives, and do the base rate check. Four practices that protect you and your team from the 'I knew it all along' trap. Lucas: And if you start using them, let us know. We'd love to hear how it goes. For now, that's it for this episode — see you next time.