PerfCopilot
Get started
Editorial illustration of a single glowing trait casting a halo of light across a row of separate competency scorecards on a desk, the rest of the cards lit by its glow.

Related: how to reduce bias in performance reviews.

The Halo Effect in Performance Reviews (and How to Counter It)

By Samira Bahmanyar · HR Manager

Definition The halo effect in performance reviews is the tendency for one strong, salient trait (charisma, polish, a single big win) to inflate a person's ratings on every other competency, even unrelated ones. Its inverse, the horns effect, lets one weak trait drag every rating down. Both replace per-competency judgment with a single overall impression.

A sales rep who presents beautifully gets rated high on planning, teamwork, and process too, whether or not the evidence supports it. That is the halo effect, and it quietly turns a multi-competency review into one gut feeling wearing five different scores.

Key Takeaways

  • The halo effect was named by psychologist Edward Thorndike in his 1920 study of how officers rated aviation cadets (Thorndike, A Constant Error in Psychological Ratings, 1920).
  • The horns effect is the same bias in reverse: one weak trait pulls every rating down.
  • The fix is structural: rate each competency separately against specific evidence, not against one global impression of the person.

Try it on your own data: PerfCopilot runs a bias checker on any review draft, then turns real work into a cited, bias-checked draft — generate a performance review or see it for GitHub activity. Free for up to 5 seats.

What is the halo effect?

The halo effect is a cognitive bias where one positive impression of a person spreads a "glow" across unrelated judgments, so a single strong trait inflates every rating. In reviews it means a charismatic or visible employee scores high on planning, collaboration, and reliability without separate evidence for each. It is the brain treating a person as one rating, not a set of skills.

The bias has a precise origin. In 1920, psychologist Edward Thorndike asked army officers to rate aviation cadets on separate qualities like physique, intellect, leadership, and dependability. He expected the ratings to vary independently. Instead, they correlated far "too high and too even," as if each cadet were simply "rather good" or "rather inferior" overall (Thorndike, 1920). Thorndike named that pull toward one global impression the halo effect.

types of performance review bias

The horns effect: the same bias in reverse

The horns effect is the negative mirror of the halo effect: one weak or off-putting trait drags down ratings on everything else, including competencies where the person is strong. A quiet operations analyst who avoids the spotlight gets marked "needs improvement" on impact, even when their work prevented three outages. Same mechanism, opposite direction.

Most managers recognize the halo effect but forget the horns version exists, which is why your most introverted high performers are often the most under-rated people on the team. They never trip the "glow," so steady, low-visibility excellence reads as average. A fair process has to catch both, because together they explain why ratings cluster around overall vibe instead of tracking actual contribution.

The honest trade-off: you cannot delete an impression once you have it. The halo and horns effects run automatically, below awareness. The realistic goal is not a bias-free manager. It is a review process that forces you to check each rating against evidence before the impression gets to decide.

Halo effect examples across teams

The halo effect shows up on every team, not just one. A few concrete patterns:

In each case, one salient trait, visibility, charm, polish, or a single big win, sets a global impression that the other scores then quietly conform to. That is exactly the unconscious mechanism Nisbett and Wilson demonstrated in 1977: students who watched a lecturer behave warmly rated even his appearance and accent as appealing, while those who saw the same person act cold rated the same traits as irritating, and they sincerely believed their judgments were independent (Nisbett & Wilson, The Halo Effect, 1977).

Why it distorts ratings and calibration

The halo effect breaks reviews in two ways. First, it collapses a multi-competency rubric into a single judgment, so "rate planning, execution, collaboration, and growth" becomes "do I think this person is good?" answered five times. Second, it corrupts calibration, because when managers walk into the room with impressions instead of evidence, the loudest advocate for the most charismatic employee wins.

Here is the reframe that matters: the halo effect is not a kindness problem or a strictness problem. It is an evidence-attribution problem. The manager has formed one accurate impression (this person is charismatic) and then let it stand in for evidence they never actually gathered on four other competencies. The bias is not in the impression. It is in letting the impression vote on questions it was never qualified to answer.

That is why calibration meetings so often turn into debates over personality. With no per-competency evidence on the table, the halo and horns effects are all anyone has to argue with. A calibration meeting only corrects bias when every rating arrives attached to specific, dated examples that a peer can challenge.

How to counter the halo effect

Generic advice ("just be objective") fails because the halo effect operates below awareness. You cannot will yourself out of a bias you cannot feel. These countermeasures work because they change the process, not the manager.

1. Rate each competency separately, against its own evidence

Before scoring a competency, write the evidence first, then the rating. If you cannot point to two or three specific, dated examples for "collaboration," you do not have a collaboration rating yet. You have an impression. Forcing evidence-before-score per competency is the single most effective halo break, because it stops one trait from silently filling in the blanks on the others.

2. Separate observations from impressions

Keep two columns: what happened (the rep closed the deal on March 12, the analyst caught the config error before deploy) and what you concluded. Impressions are fine as long as they are labeled as impressions and checked against the observation column. Most halo errors are an impression that got promoted to a fact when nobody was looking.

3. Use a structured rubric with behavioral anchors

Vague scales ("rate leadership 1 to 5") invite the halo effect because they have nothing to push back with. A rubric that defines what each score looks like in observable behavior gives every rating a standard to meet, so charisma alone cannot clear the bar. This is one of the core moves in any program to reduce bias in performance reviews.

4. Pull the whole period's artifacts before drafting

The halo effect feeds on missing data: when you cannot recall the analyst's outage saves, their charisma deficit fills the gap. Reviewing tickets, deals, docs, peer feedback, and shipped work across the full period gives the quiet performers their evidence back, which is also how you counter recency bias in performance reviews at the same time.

5. Run a bias screen before you submit

A quick screen catches the pattern: are this person's scores suspiciously flat across very different competencies? Is your most reserved report rated lowest on "impact" despite strong output? Flat profiles and visibility-tracking scores are the fingerprints of halo and horns. Flag them, then re-check each against evidence.

Why per-competency evidence wins: the other fixes help, but a global "be fair" reminder cannot survive a charismatic candidate in a calibration room. Evidence attached to each separate competency can. It gives the bias something concrete to lose to.

Where software fits

Most of the work above is recall and discipline, which is exactly what busy managers run out of. This is the gap PerfCopilot was built to close: it drafts each review with per-claim evidence pulled from the tools your team already uses (tickets, deals, calls, threads, shipped work), so every competency rating arrives with specific examples instead of one global impression, and a built-in bias screen flags halo-style flat profiles before you submit. To be clear about scope, PerfCopilot is a review-writing layer, not a full performance platform: no OKRs, engagement surveys, or compensation. It writes cited, bias-checked drafts. You still own the judgment.

Halo effect vs other review biases

The halo effect rarely travels alone. It runs alongside recency bias (over-weighting recent work), leniency bias (everyone gets a high score), similar-to-me bias (rating people who remind you of yourself), and central-tendency bias (everyone gets a 3). They all share one root: a rating made from impression instead of evidence.

For the full taxonomy and a combined playbook, see types of performance review bias and our guide to reduce bias in performance reviews. Fixing the halo effect alone helps, but the durable win is a process that neutralizes the whole cluster at once.

Frequently asked questions

What is the halo effect in performance reviews in one sentence?

The halo effect is the tendency for one strong, salient trait (such as charisma, polish, or a single visible win) to inflate a person's ratings on every other competency, even unrelated ones, replacing per-competency judgment with a single overall impression of the person.

What is a simple halo effect example?

A charismatic salesperson closes one big deal and presents it well, so their manager rates them high on planning, teamwork, and process too, despite no separate evidence for those skills. The strong impression on one trait spreads a "glow" across ratings it should not touch.

What is the difference between the halo and horns effect?

They are the same bias in opposite directions. The halo effect lets one positive trait inflate every other rating; the horns effect lets one negative or off-putting trait drag every rating down. A quiet but excellent analyst under-rated on "impact" for being reserved is a classic horns effect.

Who discovered the halo effect?

Psychologist Edward Thorndike named the halo effect in his 1920 study of how army officers rated aviation cadets. He found ratings of separate qualities correlated far too closely, as if each person were judged "rather good" or "rather inferior" overall (Thorndike, 1920).

Can you eliminate the halo effect from appraisals?

Not fully, because it operates below awareness. The realistic goal is a process that contains it: rate each competency separately against specific dated evidence, separate observations from impressions, use behavioral-anchor rubrics, and run a bias screen before submitting. Structure beats willpower here.

The bottom line

The halo effect is not a sign of a careless manager. It is the brain doing what it always does: turning a person into a single impression and letting that impression answer questions it was never qualified to answer. The horns effect does the same in reverse, which is why your quietest strong performers are so often under-rated.

The structural fix is to make every competency stand on its own evidence. That is the bet behind PerfCopilot: per-claim evidence pulled from the work your team already does, plus a bias screen, so charisma stops voting on competencies it never earned. Free for teams of 5 or fewer; Pro is $4.99 per user per month, billed annually.

Sources