Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / The Halo Effect in Office Politics How Reputation Bleeds
Transcript
- Lucas: So there's a colleague in your office—let's call her Priya—who shows up five minutes early to every meeting, takes neat handwritten notes, and always says 'Good morning' with a smile. Everyone on the team thinks she's brilliant even though her actual project output is consistently average. Meanwhile, Sam sits in the back, delivers excellent code on time, but dresses a little sloppily and never makes eye contact. Sam keeps getting passed over. That's the Halo Effect at work. Luna: Yeah, it's like one good trait—punctuality, warmth—throws a golden glow over everything else. And one awkward trait buries you. Lucas: Exactly. And it's not just anecdotal. There's a 2019 study in the Journal of Applied Psychology—researchers looked at how a single early impression in a meeting, like speaking up with a confident suggestion, inflated subsequent performance ratings by 12 percent across unrelated categories. Twelve percent. That's the difference between 'meets expectations' and 'exceeds expectations' for a lot of companies. Luna: And that 12 percent compounds. If you get a slightly better rating one quarter, you get better projects, more visibility, more chances to shine again. Lucas: Right. It's a reputation flywheel. But here's the uncomfortable part—the Halo Effect isn't just something that happens to us. We do it to others all the time. And if you want to navigate office politics well, you need to both manage your own halo and check your bias when evaluating colleagues. Luna: Honestly, if this episode helps you think through one career decision—maybe how to position yourself before a review—it's worth the price of a coffee. And if it is, people can support the show at buy me a coffee dot com slash fexingo. Keeps us ad-free and focused on exactly these kinds of topics. Lucas: Yeah, it's a small way to keep the conversation going. So let's dig into the mechanics. The term 'halo effect' was coined by psychologist Edward Thorndike in 1920. He had military officers rate soldiers on traits like intelligence, physique, leadership, and character, and found that a high rating on one trait pulled up ratings on all the others. If you thought someone was physically impressive, you also thought they were smarter. Luna: A hundred years later and we still do the same thing in open-plan offices. So how do you deliberately build a halo? Lucas: First, you pick the one or two signals that matter most in your specific culture. At a law firm, that might be showing up with the brief fully memorized. At a design agency, it might be having a sharp sense of typography. You don't need to be perfect at everything—just excellent at the thing that people associate with 'good' writ large. Luna: So you're saying identify the anchor trait. The one thing that, if you nail it, makes people assume you're good at the rest. Lucas: Exactly. And it's not just about your own halo—you can also leverage it when you're championing someone else's work. If your intern presents a clean pivot table, you can say 'Look how organized this is' before they even get to the analysis. You're framing the halo before the data arrives. Luna: But isn't there a risk that the halo backfires? Like if you over-invest in one signal and then slip up? Lucas: Big risk. The Halo Effect cuts both ways. One visible mistake can also drag down everything else. There's a concept called the 'reverse halo' or 'horn effect'—a single negative trait colors everything negatively. The key is to build a halo from a signal that's durable. Being reliably prepared is more durable than being the one who tells the best joke. Luna: Because jokes can fall flat. But showing up prepared every time—that's a pattern. It's harder to dismiss. Lucas: Right. And you don't want your halo to be too narrow. If you're known as 'the spreadsheet person,' you might get stereotyped and never considered for strategy roles. So you want a halo signal that's transferable. 'This person is thoughtful' is broader than 'this person knows Excel.' Luna: So it's about managing the lens through which people see you. But what about when you're the one evaluating others? How do you check your own halo bias? Lucas: One technique is to evaluate each competency separately, ideally on different days. When you rate someone's 'collaboration' right after you rated their 'communication,' the halo spills over. If you force yourself to rate all team members on one dimension at a time, you reduce the spillover. Luna: That's actually practical. I also heard about using a rubric with specific behavioral anchors—like instead of 'is a good leader,' you list 'delegates tasks clearly, checks in weekly.' It makes the halo harder to hide behind. Lucas: Exactly. And the best managers I've seen do something even simpler: they ask 'What would I think of this person if I had only their output and never met them?' That question forces you to strip away the halo of their charisma or their punctuality. Luna: It's almost like a mental de-biasing exercise. So let me ask you—in your own career, have you deliberately used the Halo Effect? Lucas: Early on, yeah. I made sure that when I presented a report, I'd front-load the one insight that was most surprising. I knew that if I could get the team to say 'Wow, that's clever,' the rest of the meeting would go smoothly. I was essentially using the Halo Effect to build credibility for a longer conversation. Luna: So you seeded a halo. And then you had to deliver on the rest, of course—but the halo gave you the benefit of the doubt. Lucas: Exactly. It's not a substitute for substance. It's a complement. You still need good work. But if the halo gets people to pay attention to your good work, that's a political win. Luna: And on the flip side, if you suspect someone else's halo is inflating their reputation, you can protect yourself by documenting specific contributions. After a project, I send a brief update listing what I did. It's not bragging—it's evidence that competes with the halo. Lucas: That's smart. Because the Halo Effect thrives on vagueness. The more specific you are about your own contributions, the harder it is for someone else's halo to overshadow you. Luna: One thing I've noticed is that the Halo Effect is especially strong during performance reviews. If a manager had one positive interaction with you—like you solved a minor tech issue—they might rate you higher on strategic thinking. Lucas: Right. There's a famous study from the 70s where researchers showed that teachers who were told certain students were 'bloomers' gave those students higher grades, even though the students were randomly selected. The teachers' belief created a halo that influenced their perception of actual performance. Luna: So it's self-fulfilling too. If your manager thinks you're a 'bloomer,' they give you more attention, you perform better, and the halo gets confirmed. Lucas: That's the Pygmalion Effect, which we covered in episode 103. But it's a cousin of the Halo Effect. The point is, once a halo is in place, it's sticky. So the best time to manage it is at the beginning—first impressions, first projects, first meetings. Luna: So if you're starting a new job or a new project, you want to be very intentional about the first signal you send. What would you suggest? Lucas: I'd pick one thing that aligns with the team's biggest pain point. If the team is drowning in data, be the person who brings clear summaries. If they're struggling with morale, be the person who acknowledges people's contributions publicly. That first signal sets the halo for everything you do after. Luna: And then reinforce it consistently. One good signal is a fluke. Two is a pattern. Lucas: Exactly. And be aware that the Halo Effect also applies to how you perceive your own work. You might think a project is better than it is because you like the client, or because you had a good lunch meeting. Always separate the work from the context. Luna: So it's not just about managing others' perceptions—it's about managing your own judgment. Because if you're blinded by your own halo, you might over-invest in a weak idea. Lucas: Right. I've seen people kill themselves trying to defend a flawed project just because they had a great kickoff meeting. That kickoff meeting halo made them ignore all the red flags. Luna: So the takeaway for today: Halo Effect is real, it's powerful, and it's not going away. Use it deliberately—choose your signal, reinforce it, but stay aware of its blind spots. Lucas: And if you're on the receiving end of someone else's halo, don't just accept it. Look for specific evidence. Ask yourself: if I took away the trait that I first noticed, what would I think of their actual work? Luna: That's a good mental model. So next time you're in a meeting and someone says 'Priya is so prepared,' you can ask—prepared for what? And does that actually mean she's strategic? Or just early? Lucas: Exactly. And if you're Sam in the back, maybe it's time to sit up front and say something insightful in the first five minutes. Because the halo is waiting to be assigned.