Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How the Halo Effect Twists Office Politics
Transcript
- Lucas: You know that colleague who always sounds brilliant in meetings—sharp, confident, never at a loss for words—and somehow gets the promotion even though the quiet person on the team did most of the heavy lifting? Luna: Oh, I've seen that movie. It's like the one skill—public speaking—creates a glow that makes everyone assume they're also great at strategy, project management, and maybe even accounting. Lucas: Exactly. That's the halo effect in action. Psychologist Edward Thorndike coined the term in 1920 after he had military officers rate soldiers on traits like intelligence, physique, leadership, and character. He found that if an officer thought a soldier was smart, they also rated him higher on every other trait—even though those traits aren't actually correlated. Luna: So a single positive impression spills over. And we do the same thing in the office every day. Lucas: That's the kind of thing that makes you realize how much our perceptions are influenced by these mental shortcuts. If this episode helps you navigate that, honestly, if it was worth a coffee to you, you can support us at buy me a coffee dot com slash fexingo. Luna: It keeps the show ad-free and independent, and we genuinely appreciate it. Now, back to that glow—how does the halo effect actually distort performance reviews? Lucas: Good question. Let's say you're reviewing an employee named Priya. She's an excellent presenter—clear, engaging, handles Q&A effortlessly. But when you look at her project deliverables, the code is messy, deadlines slip, and she rarely documents her work. The halo from her presentation skill can make a manager rate her higher on 'technical competence' and 'reliability' even though the evidence points the other way. Luna: So the reviewer is basically substituting one easy observation—'she's articulate'—for a harder evaluation of actual output. Lucas: Right. This is especially dangerous in 360-degree feedback and annual reviews, where managers have limited direct observation and rely on impressions. A study in the Journal of Applied Psychology found that when a manager had a positive overall impression of an employee, they rated that employee 0.7 points higher on a 5-point scale across all competencies, regardless of actual performance. Luna: Zero point seven points—that can be the difference between 'meets expectations' and 'exceeds expectations'. Lucas: Exactly. And it compounds. Over three years, that halo effect can push someone onto a fast track while a quieter but equally competent colleague stagnates. One Fortune 500 tech company I looked at—let's call it TechNova—realized this was happening and redesigned their review process. They forced managers to rate each competency separately, with a mandatory pause between each rating, and they required a written example of specific behavior before assigning a score. Luna: Did it work? Lucas: According to their internal HR report, promotions from the 'high potential' list became 30 percent more predictive of actual performance in the following year. The halo effect wasn't eliminated, but it was significantly reduced. Luna: That's a concrete win. So what about hiring? Interviews are a halo factory—one confident handshake and wow. Lucas: Totally. In hiring, the halo effect often shows up as 'similarity bias' or 'liking bias,' but it's all the same mechanism. A candidate who shares the interviewer's alma mater or hobby gets a halo boost. Structured interviews with a consistent question rubric are the best defense. Google, for example, uses a structured scoring system where each question is rated on a specific skill, and interviewers aren't allowed to discuss impressions until scores are submitted. Luna: So the key is to isolate attributes and evaluate them one by one—not let the 'likable' factor leak into the 'analytical skill' box. Lucas: Precisely. And it's not just about others—we also apply the halo effect to ourselves. If you ace one presentation, you might start believing you're a great project manager, and then you overlook your own weaknesses. That can lead to overconfidence and career missteps. Luna: Right. So the antidote is the same: separate your self-assessment into distinct areas and look for disconfirming evidence. Lucas: Exactly. And a simple tactic is the 'fact-check pause.' Before you give someone credit or assign a performance rating, ask yourself: 'What specific evidence do I have for this specific trait? Is there evidence that contradicts it?' That ten-second pause can break the halo reflex. Luna: I love that. It's like a mental friction against a lazy judgment. So for someone listening who wants to apply this tomorrow, what's the one takeaway? Lucas: When evaluating a colleague—or yourself—decompose the judgment. Don't ask 'Is this person good?' Ask 'How is their technical execution? How is their collaboration? How is their communication?' Answer each one with a concrete example. If you can't find an example for a dimension, that dimension is probably being halo-filled by another. Luna: That's powerful. And it's a skill you can practice in everyday meetings. Watch yourself next time someone makes a point you agree with—are you suddenly thinking they're smarter overall? Lucas: Exactly. So let's end with a challenge: this week, catch yourself in a halo moment. Maybe a charming vendor pitches you, or a team member says something insightful. Pause and ask what you actually know about their other capabilities. That awareness is the first step to fairer office politics.