Halo Effect

Where the term comes from

Psychologist Edward Thorndike described the effect in a 1920 paper, "A Constant Error in Psychological Ratings," after noticing that army officers' ratings of soldiers on separate traits such as intelligence, physique and leadership were far more correlated than the traits themselves could plausibly be. Raters were forming one general impression and applying it everywhere. A century of research on ratings has found the same pattern in classrooms, interviews and performance reviews.

How the halo effect shows up in interviews

Typical triggers in hiring:

• Brand-name history. A candidate from a well-known company or university gets assumed competence in skills they never demonstrated.
• Polished communication. A fluent, confident speaker gets high marks for problem-solving, even when the actual solution they described was ordinary.
• One great answer. A vivid story early in the interview colors how every later answer is heard.
• Appearance and rapport. Attractive or likable candidates tend to be rated higher across the board.

Example: a candidate for a contact-center quality analyst role previously worked at a large bank. The interviewer rates her 5 on data analysis and 5 on coaching. Her scorecard notes for coaching say only "strong background." She never gave a coaching example. That is halo at work, and it is invisible unless someone reads the evidence behind the scores.

The opposite, where one negative trait drags everything down, is the horns effect.

Halo effect in performance appraisal

The same error is common in performance reviews. A team member who closed one huge deal, or who is always visible and agreeable in meetings, gets top ratings on attendance, documentation and teamwork without anyone checking. Over time this distorts promotion decisions and pay, and other employees notice. A related problem is recency: one strong month just before review season acts as a halo for the whole year.

How it differs from related biases

• Halo vs. affinity bias: Affinity bias is liking someone because they resemble you. Halo is about one trait spreading across ratings. They often combine: you like a candidate who shares your background, and that warmth inflates every competency.
• Halo vs. confirmation bias: Confirmation bias is seeking evidence for a belief you already hold. Halo often creates the belief that confirmation bias then defends.

All of these are covered in our overview of interview bias.

How to reduce the halo effect

1. Rate each competency separately, with evidence. A rating with no supporting note for that specific competency is a warning sign.
2. Use anchored scales. If a 4 on coaching requires a concrete example of developing someone, a general good impression cannot earn it.
3. Hide the resume for some questions. Some teams have one interviewer assess skills without seeing employer names or schools.
4. Split competencies across interviewers. In a panel, give each person ownership of different areas so a single impression does not drive every score.
5. Score at the end, from notes. Not during the conversation, when impressions are strongest.
6. Look for flat profiles. A candidate rated 5 on every competency is possible, but worth a second look at the evidence. The same goes for performance reviews where everyone in a team gets identical marks across categories.

Training helps people recognize the pattern, but the scorecard design is what catches it.