Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How Recency Bias Distorts Your Career Trajectory
Transcript
- Lucas: There is a specific kind of horror that only exists in corporate America, and it usually arrives in October or November when performance reviews are due. It is the moment where an employee who has been quietly excellent for eighteen months looks at their manager’s notes and realizes the narrative being built doesn’t match reality. Luna: It is almost always because they took two weeks off in July, or because they had one particularly rough week in September, and now the whole year is colored by those few days. Lucas: Exactly. And the psychological term for this is recency bias, which is essentially the brain’s way of saying, 'What I remember most vividly is what matters most.' It is a heuristic, a mental shortcut, but in the context of career advancement, it is a dangerous one because it rewards volatility over consistency. If you are loud and chaotic right before the review, you look more active than someone who delivered steady, high-quality results for eleven months straight. Luna: I have seen this happen with creative teams specifically, where the person who stayed late to fix a crisis on Friday gets all the credit, while the person who prevented the crisis entirely gets ignored because nothing happened. Lucas: That is the classic prevention paradox. But let me give you a concrete example that illustrates just how deep this bias runs. A few years ago, there was a well-documented case involving a senior software engineer at a major cloud infrastructure provider. Let us call him David. David had spent two years stabilizing their core payment system. He reduced latency by forty percent and eliminated critical bugs. He was invisible, which is exactly what he wanted to be. Luna: Invisible is good for an engineer, but invisible is bad for a promotion candidate. Lucas: Precisely. Then, three weeks before his annual review, David went on a planned vacation. While he was gone, a minor integration issue arose with a third-party vendor. It was resolved quickly, within four hours, and caused no downtime. But during those three weeks, David was absent. When he returned, he checked in, did a solid week of work, and then sat down for his review. His manager’s primary memory of David’s performance that year was his absence during that incident. Luna: So the manager forgot the two years of stability and focused entirely on the three weeks of silence. Lucas: Right. The manager described David as 'reliable but occasionally detached,' which is code for 'not ready for promotion.' The data showed David was the top performer in his group for six consecutive quarters, but the recency bias had overwritten that dataset with a much smaller, louder file. It is not that the manager is evil; it is that human memory is flawed. We weight the most recent data points disproportionately. Luna: This makes me think about how we structure our own weekly updates. Do we actually highlight the quiet wins, or do we only talk when something breaks? Lucas: Most people do not. Most people treat their status updates as operational logs rather than strategic narratives. They say, 'I fixed ticket four-zero-two.' They do not say, 'By fixing ticket four-zero-two, I prevented a potential outage that would have cost the client ten thousand dollars in service level agreement penalties.' One is a task; the other is value. Recency bias punishes the task-listener and rewards the value-storyteller. Luna: So the solution is to force the manager to remember the value, not just the activity. Lucas: Yes, but you cannot just rely on memory. You have to create artifacts. I want to pause here for a second to talk about how we keep this show running. If today was worth a coffee to you, that is the link — buy me a coffee dot com slash fexingo. It keeps the lights on and allows us to dig into these deeper psychology topics without relying on ads that might distract from the message. We appreciate every single listener who supports us directly. Luna: Thank you. It really helps us bring you these kinds of detailed breakdowns on workplace dynamics. Lucas: Back to David, the engineer. The interesting part is what happened after the review. David was furious, but he also realized he had played the game wrong. He stopped waiting for the annual cycle. He started sending a bi-weekly 'impact memo' to his manager and his skip-level leader. These were not long documents. They were three bullet points: one win, one lesson learned, one forward-looking initiative. Luna: Bi-weekly seems like a manageable cadence. Is that too frequent for busy managers? Lucas: It is only too frequent if the content is fluff. David kept them tight. Because he sent them regularly, his manager began to associate David with consistent, proactive communication. When the next review cycle came around, even though David took another vacation, the pattern was established. The manager could not rewrite history because the evidence was distributed evenly across time. The recency bias was diluted by volume. Luna: It is basically building a wall of facts so the bias can only knock down a small section at a time. Lucas: That is a perfect analogy. And it applies to more than just engineers. Think about sales teams. The salesperson who closes the biggest deal in December often gets the Employee of the Year award, regardless of what they did in January through November. If they had a slow spring, it disappears from memory. The recency effect flattens the entire year into a single peak or trough. Luna: So for salespeople, the strategy should be to ensure the final quarter isn't the only quarter that gets remembered. Lucas: Absolutely. One tactic some top performers use is to schedule their 'big news' strategically. If they know a major project is launching in Q1, they might try to secure the executive sponsorship and initial wins in Q4 of the previous year. They front-load the positive recency. It is slightly manipulative, perhaps, but it is a rational response to a biased system. Luna: Front-loading the wins. I like that. It feels counterintuitive because we usually think of wrapping up at the end of the year. Lucas: We do, because we think of the calendar year as a container. But psychologically, the container is fuzzy. The most recent month is always the sharpest. Another angle to consider is how you handle failures. If you make a mistake in March, and you spend April and May fixing it and preventing recurrence, do you mention the mistake in May? Most people hide it. They hope the manager forgets. Luna: Because they are afraid it will taint the current narrative. Lucas: But hiding it leaves a gap. If the manager asks, 'Why did we lose that account?' and you have no record of addressing it, it looks like negligence. The better approach is to frame the failure as a solved problem. 'In March, we lost Account X due to a billing error. Here is the new protocol we implemented in April that ensures zero recurrence. Account Y signed under this new protocol in May.' You control the narrative arc. Luna: You turn the failure into a credential. That is powerful reframing. Lucas: It is. And it protects you from the negativity bias, which is the cousin of recency bias. Negativity bias means we remember bad things twice as loudly as good things. Recency bias means we remember the most recent thing, regardless of valence. Together, they mean that a recent mistake can erase a year of success unless you actively overwrite it with visible progress. Luna: So the key takeaway is that you cannot assume your work speaks for itself. You have to provide the soundtrack. Lucas: Exactly. Work is silent until you translate it. Let me ask you this: do you think remote work has made recency bias worse or better? Luna: I think it has made it worse because we lack the ambient awareness of an office. In an office, you see someone helping a colleague for six months. In Zoom, you only see them in their scheduled meetings. Lucas: That is a profound point. The 'watercooler moments' are often where informal reputation is built. When those disappear, the only data left is the formal meeting transcript. Which is dry, sparse, and highly susceptible to recency distortion. Remote workers have to be twice as intentional about documenting their influence. Luna: Documentation becomes the new watercooler. You have to write yourself into the record. Lucas: Precisely. And this brings us back to David, the engineer. After his bi-weekly memos started, his relationship with his manager changed completely. The manager began to consult him on strategic decisions earlier because he knew David was thinking ahead. The trust wasn't built on charisma; it was built on predictability and visibility. Luna: Predictability is underrated in office politics. We always think charisma wins, but consistency builds safety. Lucas: Safety is huge for managers. A manager wants to promote someone who reduces their anxiety, not someone who creates excitement followed by confusion. David reduced his manager’s anxiety by making his output transparent. That is the real currency of career advancement. Luna: So if you are listening to this and you feel like your hard work is going unnoticed, start looking at your documentation habits. Are you leaving gaps where recency bias can creep in? Lucas: Yes. Audit your last three months. Where did you go silent? Did you take a project offline without announcing it? Did you solve a problem without telling anyone? Those silences are where your reputation leaks away. Fill them in. Make the invisible visible. Luna: It is not about bragging. It is about ensuring the record is accurate. Lucas: It is about accuracy. History is written by the victors, but in corporate America, history is written by the people who send the clearest emails in the last thirty days. Luna: A sharp way to put it. So, for our listeners, the action item is simple: pick one recurring project you are working on, and set a reminder to send a brief update on its progress to your stakeholders every two weeks. Lucas: Keep it to three sentences. Win, lesson, next step. Do it consistently for ninety days. You will be amazed at how much clearer your value becomes, both to yourself and to your team. Luna: And you will likely find that your next performance review feels less like a battle and more like a confirmation. Lucas: If you can control the narrative, you control the outcome. That is the power of fighting bias with structure. Luna: Thanks for tuning in to The Office Politics Podcast. We will see you next time.