Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / The Halo Effect in Performance Reviews
Transcript
- Lucas: Let's talk about the moment every employee dreads and every manager fears: the annual performance review. We often assume these are objective audits of competence, but cognitive psychology suggests otherwise. Specifically, I want to look at the halo effect, a bias where one standout positive trait creates a glow that makes everything else about an employee seem superior by association. Luna: Right, so if someone is incredibly charismatic or lands one massive deal, their messy spreadsheets or poor communication style just gets ignored? Lucas: Exactly. It’s not just ignoring the negatives; it’s actively interpreting ambiguous behaviors as positives because of that initial shine. Think about a senior software engineer who writes brilliant code but has zero patience for mentoring juniors. In a halo-driven review, that impatience might be reframed as 'high standards' or 'efficiency focus,' rather than what it actually is: toxic team friction. Luna: That sounds exhausting for the people actually doing the mentoring while getting overlooked. Does this happen mostly with technical roles? Lucas: It happens everywhere, but it’s particularly dangerous in roles where output is hard to quantify immediately. Take sales. A top performer brings in two million dollars in revenue. Their manager might overlook the fact that they monopolize conference calls or undercut colleagues in cross-functional projects. The revenue number is so loud it drowns out the cultural damage. Luna: So the company keeps the money but loses the team cohesion. That’s a classic short-term win, long-term loss scenario. Lucas: We deliberately don't run ads on these shows. If you want to support that choice and help us keep this content ad-free, the link is buy me a coffee dot com slash fexingo. Thanks for keeping us going. Luna: Appreciate it. So back to the sales rep—how does this bias survive when HR tries to standardize reviews across the department? Lucas: It survives because managers are lazy thinkers. Evaluating ten distinct competencies requires active cognitive effort. Noticing one big win requires only passive observation. When you ask a manager to rate an employee on 'collaboration,' 'innovation,' and 'reliability,' they default to the most recent or most vivid memory. If that memory is the huge sale, the rest of the scale gets inflated by default. Luna: But isn't innovation also important? Maybe the big sale innovative. Lucas: Maybe, but often it wasn't. Often it was just brute force persistence or a lucky break. The problem is the manager conflates the outcome with the underlying behavioral traits. They see the result and assume the character must be excellent across the board. It’s a heuristic shortcut our brains love, but it’s terrible for talent management. Luna: So if you’re the employee, how do you fight this? Do you just point out your weaknesses to prove you’re balanced? Lucas: You have to make the invisible visible. You need to document the things that don’t have a hard number attached to them. If you’re the engineer who mentors juniors, don’t just say you did it. Show the pull requests you reviewed, the new hires you onboarded, the documentation you wrote. Force the manager to look at data points outside your primary output metric. Luna: Make the soft skills hard data. That’s smart. But what if the manager is just resistant to seeing anything other than the headline number? Lucas: Then you have to change the framing of the conversation. Instead of defending your mentoring, frame it as risk mitigation. Say something like, 'I’ve spent twenty percent of my time this quarter stabilizing the junior team’s workflow, which reduced our bug backlog by fifteen percent.' Now you’re linking the 'soft' behavior to a 'hard' business outcome. You’re giving the manager a hook to justify rating you highly on collaboration without having to guess. Luna: Linking behavior to outcome. That’s basically translation work. Are you saying we all have to become translators now? Lucas: In a way, yes. The modern workplace rewards those who can articulate the value of non-obvious contributions. The halo effect punishes those who assume their good work speaks for itself. It’s a harsh reality, but recognizing the bias is the first step to neutralizing it. Luna: What about the flip side? The horns effect, where one mistake ruins everything? Lucas: Oh, absolutely. That’s the dark twin. If a usually reliable employee misses one deadline, the halo effect reverses. Suddenly, their great code looks sloppy, their helpful emails look desperate, and their punctuality becomes questionable. One negative anchor drags down the whole ship. It’s just as irrational, just in the opposite direction. Luna: So it’s not just about being too nice. It’s about the brain refusing to hold nuance. It wants a hero or a villain, not a complex human. Lucas: Precisely. Humans are narrative creatures. We want stories with clear arcs. A complex employee with mixed strengths doesn’t fit neatly into a story, so our brains simplify. We create a caricature. For the manager, it’s easier to write 'Excellent Performer' than to draft a nuanced paragraph explaining exactly where someone shines and where they struggle. Luna: And that laziness hurts the company. If you promote the halo-ed sales rep into management, they’re going to bring that same bias into their own team. Lucas: Which is why the halo effect is such a structural risk. It compounds. A manager who was rewarded for charisma over competence will likely replicate that pattern. They’ll hire similar people, promote similar people, and build a team that looks great on the surface but lacks depth. It creates an echo chamber of mediocrity disguised as excellence. Luna: So how do organizations fix this? Is there a tool or a framework that actually works? Lucas: Calibration sessions are the best defense. This is where multiple managers sit together to review ratings before they go final. If Manager A says John is a nine out of ten, and Manager B says John is a five out of ten based on his client interactions, that discrepancy forces a conversation. It breaks the isolation of the individual reviewer and exposes the bias. Luna: Group pressure can counteract individual bias. That makes sense. But doesn’t groupthink also have its own risks? Lucas: It does, but it’s still better than solitary judgment. The key is diversity in the calibration room. You need people who interact with the employee in different contexts. If you only have the employee’s direct supervisor and their peer, you’re still missing pieces. Bring in someone from a different department who collaborated with them. That third perspective shatters the halo. Luna: So, more eyes, different angles. It’s about triangulation. Lucas: Exactly. Triangulation. Just like navigation. You can’t know where you are with one landmark. You need three. In performance management, you need three perspectives to get close to the truth. Luna: I like that. It shifts the burden from the individual employee fighting their boss’s bias to the system requiring multiple inputs. But it only works if the culture supports honest feedback. Lucas: If the culture is political, calibration sessions become battlegrounds. Managers will defend their stars aggressively. That’s why psychological safety matters. People need to feel safe saying, 'Actually, I think Sarah’s client wins came at the cost of her internal teamwork.' Without that safety, the halo remains unchallenged. Luna: So it’s not just a cognitive issue. It’s a cultural one. The bias thrives in silence. Lucas: Right. And silence is expensive. When you let the halo effect dictate promotions, you send a message to the rest of the team that personality trumps contribution. Or worse, that only visible wins matter. That erodes trust over time. Luna: For the listener listening to this during their next review prep, what’s the one thing they should walk away with? Lucas: Document the full picture. Don’t just list your achievements. List the behaviors that enabled those achievements, and the collateral damage you avoided. Make the context part of the record. Force your manager to see the ecosystem, not just the trophy. Luna: See the ecosystem, not just the trophy. I’m stealing that line. Lucas: Steal it. It’s accurate. And if you’re the manager, ask yourself: am I rating this person’s potential, or their actual impact? Am I confusing charm with competence? Luna: Those are uncomfortable questions. But necessary ones. Lucas: They are. Because once you realize your brain is lying to you, you can start correcting for it. And that correction is what separates good leaders from merely popular ones. Luna: So, is there hope for the rest of us who aren’t the charismatic star? Lucas: There is. Consistency beats intensity. Over time, the halo fades if the consistency holds. People remember who showed up reliably day after day, even if they don’t have a single giant headline. Quiet reliability is a form of capital that accumulates. Luna: Accumulating quiet capital. That feels less glamorous, but probably more sustainable. Lucas: Much more sustainable. The halo is a flash. Reliability is a flame. Which one do you want burning in your career? Luna: I’ll take the flame. Thanks, Lucas. Lucas: Thanks, Luna. Let’s see if we can keep the flame lit through the next quarter.