Have you ever had one mistake follow you into a review months later? Or rated someone higher across the board just because they’re easy to like?
That’s the halo and horn effect at work. The halo effect is a cognitive bias where one strong trait, like charm or a big recent win, makes a manager rate an employee higher on unrelated skills. The horn effect is the reverse, where one flaw or mistake drags down the whole evaluation. Both show up when managers lean on gut impressions instead of evidence. Neither one is a character flaw, and no process removes them completely, but a structured review can shrink their influence a lot.
Here’s why it matters. In a Journal of Applied Psychology study of 4,492 managers, each rated by two bosses, two peers, and two direct reports, 62% of the variation in ratings traced back to the rater’s own tendencies, while actual performance explained only 21%. That study looked at developmental 360 ratings, so it doesn’t describe every review format, but it shows how much a rating can say about the person giving it. This guide covers what the halo and horn effects are, how they show up in reviews, and nine fixes you can use this review cycle.
What is the Halo Effect?
The “halo effect” is a cognitive bias where our overall impression of someone influences how we perceive their specific traits. If a person excels in one area, we tend to assume they excel in others, even without evidence.
For instance, if John is well-liked because he is friendly, his manager might also rate him highly in areas like leadership or productivity, even if his performance in those areas is average.
The term was coined by psychologist Edward Thorndike in 1920 during studies on how military officers rated their subordinates.
The effect is well documented. In a classic experiment, Nisbett and Wilson (1977) showed students two videotaped interviews with the same instructor. In one he was warm and friendly, in the other cold and distant. Students who saw the warm version rated his appearance, mannerisms, and accent as appealing, and students who saw the cold version rated the same traits as irritating. Participants also said their feelings about him had not affected those ratings.
That last part is the real lesson for managers. Most of us don’t feel the bias happening, which is why awareness alone isn’t enough and structure matters so much.
What is the Horns Effect?
The “horns effect” is the opposite of the halo effect. It occurs when a negative impression of a person influences how we view their other traits or abilities. In this case, if someone displays a single unfavorable quality, we may unfairly assume they perform poorly in unrelated areas, leading to biased evaluations.
Like the halo effect, the horns effect is rooted in the cognitive biases first explored by Edward Thorndike.
Halo Effect vs. Horn Effect at a Glance
Halo effect
Horn effect
What triggers it
One strong positive trait or win
One flaw, mistake, or bad first impression
What it does to ratings
Inflates unrelated areas
Deflates unrelated areas
Common review example
“Great presenter, so they must be a great leader”
“Late to meetings, so they must be disorganized”
Typical result
Missed development needs, unearned promotions
Missed strengths, lower engagement, unfair pay and promotion decisions
Halo Effect vs. Recency Bias
These two often get mixed up, and they often overlap in annual reviews. The halo and horn effects are trait-based, meaning one quality colors your view of other qualities. Recency bias is time-based, meaning the last few weeks color your view of the whole year. A big win in November can create a halo, and a missed deadline in December can create horns, even when the other eleven months looked very different.
How Does the Halo/Horns Effect Happen in Performance Reviews?
The halo/horns effect is a type of bias that can occur in any relationship, but especially during performance reviews. The halo/horns effect occurs when a manager allows one positive or negative trait to ‘color’ their whole evaluation of an employee.
In other words, the manager becomes either too lenient or too critical of the employee based on a single trait. This can lead to inaccurate and unfair performance reviews.
For instance, in company ABC, John is the marketing manager and is in charge of Sally who has been tasked with finding cheap email marketing software for their company. Sally forgot about it and consequently missed the deadline for finding the tool they needed, causing a major headache for John as he ended up doing it himself.
Instead of coaching Sally and helping her get better so that it didn’t happen again, he wrote her off as a bad team member and stopped trying to help her grow.
It doesn’t take a dramatic event to trigger this. Here are a few ways it tends to show up in real review cycles.
A strong communicator gets rated high on technical skill because they explain things well in meetings.
A remote or hybrid employee gets lower scores on collaboration because they are less visible, even when their output is solid.
A top salesperson skips CRM updates for a quarter, and their manager rates them “meets expectations” on process because of their numbers.
An employee who pushed back on a decision once gets labeled “difficult” and loses points on teamwork for the rest of the year.
We can all see how unfair it is to treat someone like this. None of us would want to be treated this way for our mistakes. So, it is essential that we are aware of this cognitive bias, and take concrete steps to overcome it.
Signs the halo or horn effect is shaping your review
Ask yourself these before you submit any rating.
Did I give nearly the same score on every competency?
Can I name a specific example for each rating, or am I going on feel?
Am I thinking mostly about the last month or two?
Would I score this person the same if someone I liked less had done the same work?
A flat line of identical scores across unrelated skills is one of the clearest signs that one impression is doing the rating.
How Do You Avoid the Halo Horns Effect in Performance Reviews?
1. Be aware of your biases
We all have them! If you know that you tend to be too lenient or too critical of a type of person, make a conscious effort to counterbalance that tendency in your performance reviews. We can also be aware of our biases by being mindful of how we are feeling when we are rating someone’s performance.
For example, suppose we are feeling angry or frustrated with a member of our marketing team because they failed to properly audit our website causing our Google rankings to suffer, or feeling annoyed at our salesman who messed up a big presentation a while back costing us a large client. In that case, we will likely be more critical in our rating.
By taking a step back and objectively evaluating the situation, we can make sure that our biases do not affect our judgment.
2. Rate the work, not the type of person
Try to see each employee as an individual instead of fitting them into a category. That means no assumptions based on age, tenure, role, or whether someone works remotely or in the office. It also means not giving a whole team the same score because they sit in the same department.
A good test is to ask whether you’d write the same review if the same work came from someone you know less well. If your answer changes, the bias may be doing some of the talking.
3. Incorporate 360 Reviews
Incorporating 360-degree reviews helps mitigate the halo and horns effect by gathering feedback from multiple perspectives, leading to a more balanced and objective assessment of an employee’s performance.
However, feedback from Emily’s peers and subordinates could reveal issues such as missed deadlines or unclear communication. This well-rounded input helps create a more accurate and comprehensive evaluation, preventing any single perspective from dominating the review process.
To enhance your performance reviews with multi-rater feedback, explore Engagedly’s 360 Feedback tool, designed to offer in-depth insights from a diverse range of evaluators.
4. Use a performance review template
A performance review template can help you to ensure that you are evaluating each employee fairly. By using the same template for every performance review, you can avoid any potential biases that may come into play.
The critical thing to remember is that it’s still possible to let bias influence you as you fill out the templated review, however, it serves as a guide to help keep you fair and unbiased. A good performance review template is an essential tool in the review process.
5. Focus on behaviors, not traits
Trait labels like “unreliable” or “not a leader” feel like facts, but they’re really conclusions. Behaviors are what actually happened, and they are easier to discuss and easier to change.
Instead of “John is always late,” try “I noticed John arrived after the 9:00 start time on four of the last six Mondays.” Then tie it to the impact and ask what’s getting in the way.
When you’ve named the behavior, give the employee a clear way to improve. That might be a regular one-on-one, a coaching resource, or a clearer set of expectations. The goal is to support change, not just point at the problem.
6. Use objective data when possible
When you’re struggling to stay objective, go back to the numbers. Sales results, project completion rates, quality metrics, customer feedback, and attendance records can all ground a review in what happened, not how it felt. Pull the data before you write the rating, not after.
Performance review software like [Engagedly’s performance management platform](link to Engagedly performance review software page) can help here, because ratings sit next to goals and results in one place, so reviewers see the evidence while they write.
6. Seek input from others
Ask peers, direct reports, and, where it makes sense, customers for their view. Treat that input as a starting point and not as the final word. Look for patterns across several people instead of one strong opinion, since a single colleague can have their own halo or horns.
Can AI Help or Hurt in 2026?
Many teams now use AI tools to summarize feedback, draft review language, or flag rating patterns. Used well, these tools can help in two ways. They can surface a flat line of identical scores, and they can compare written feedback against the rating it supports.
There is a catch. An AI draft is only as balanced as the notes and data it’s given. If a manager’s notes are full of one big win or one big mistake, the draft will repeat it in cleaner language. So treat any AI-generated draft as a starting point and check each claim against real examples before you sign off. If you use AI in reviews, it’s also worth asking HR and legal counsel how it fits your company’s policies.
Why This Matters for US Employers
Reviews feed pay, promotion, and sometimes termination decisions. If ratings are shaped by bias and end up correlating with protected characteristics, that can create legal exposure on top of the fairness problem. This is general information and not legal advice, so check with your HR team or employment counsel about your own process. Documented evidence, consistent criteria, and calibration all help make decisions easier to explain and defend.
Conclusion
The halo and horn effect isn’t a sign that you’re a bad manager. It’s how people process incomplete information, and a review is full of incomplete information. The fix isn’t trying harder to be fair. It’s building a process that makes fairness easier.
Start small this cycle.
Rate one competency at a time.
Write down a specific example for every rating.
Pull the data before you pick the score.
Add a second set of eyes through 360 feedback or calibration.
If you want to build this into your review cycle, see how Engagedly’s 360 Feedback tool helps you gather input from multiple raters in one place.
Frequently Asked Questions (FAQs)
What is the halo effect in performance reviews?
It’s when a manager rates an employee higher on unrelated skills because of one strong trait or achievement. For example, someone who is great in meetings might be scored high on technical quality without strong evidence. Competency-based ratings and objective data help reduce it.
What is the horn effect in performance reviews?
It’s the opposite of the halo effect. One flaw, mistake, or bad first impression pulls down the manager’s view of everything else the employee does. A single missed deadline can end up lowering scores on communication, quality, and teamwork even when those areas were fine.
What is the difference between the halo effect and recency bias?
The halo effect is about one trait coloring your view of other traits. Recency bias is about recent events coloring your view of the whole review period. They often overlap, since a recent win or a recent mistake can create a halo or horns for the entire year.
Is the halo effect always bad?
Not always, because a good first impression can reflect real strengths. It becomes a problem when it replaces evidence, so a person gets high ratings for skills nobody has actually checked. The goal isn’t to remove positive impressions but to test them against specific examples and data.
Who came up with the halo effect?
Psychologist Edward Thorndike named it in 1920 after studying how military officers rated their subordinates. Later research, including the 1977 Nisbett and Wilson experiment, showed that people often don’t realize their overall impression is shaping their ratings.
Can performance review software remove the halo and horn effect?
No tool removes it completely, but software can reduce it. Using the same competencies for every employee, keeping goals and results next to ratings, collecting 360 feedback, and flagging flat rating patterns all make bias easier to spot. Managers still need to review the evidence and give specific examples.
Srikant Chellappa is the Co-Founder and CEO at Engagedly and is a passionate entrepreneur and people leader. He is an author, producer/director of 6 feature films, a music album with his band Manchester Underground, and is the host of The People Strategy Leaders Podcast.
Innovative
