Comparing Your Team Members During Reviews Destroys Fairness, Here’s Why

Comparing team members against one another in performance reviews means judging employees by their relative rank rather than by clear, role-related expectations. It can feel like a quick way to identify top performers, but it risks making ratings depend on who else is on the team, encouraging competition over collaboration, and obscuring individual contributions. Research on performance management, organizational justice, and forced ranking helps explain why fairer reviews rely on consistent criteria, specific evidence, and context—not a contest between colleagues.

Relative Ranking Undermines Fair Performance Reviews

Relative ranking is a review method that evaluates employees by comparing their performance with that of coworkers, often placing them in categories such as “top,” “middle,” or “bottom.” It differs from an absolute or standards-based assessment, which evaluates each person against defined expectations for their role. The distinction matters: an employee can meet every important goal and still receive a low rating if teammates perform better, while someone can rank highly in a struggling group without meeting the same standard expected elsewhere.

There is no single statistic that captures how much coworker comparison damages fairness across all organizations. The risk is evident, however, in research on how performance judgments are made. In a 2012 meta-analysis, psychologists Herman Aguinis, Ernest O’Boyle Jr., and colleagues reported that individual performance follows a “power-law” pattern: a small proportion of people can account for a disproportionately large share of output in some settings. That finding cautions against assuming performance will fit a neat, fixed distribution—or that a predetermined share of employees must be labeled poor performers.

Standards-based review versus peer comparison

A standards-based review asks whether an employee fulfilled agreed responsibilities, demonstrated relevant skills, and made a documented contribution. Peer comparison asks how that employee performed relative to colleagues. The first approach can recognize multiple employees who meet high expectations; the second can make recognition scarce by design, even when the whole team performs well.

This distinction is important when work differs across roles or depends on shared results. A salesperson, engineer, and customer-support specialist may all contribute to the same business outcome through different measures. Ranking them on one scale can confuse differences in opportunity, workload, or job design with differences in performance.

Forced distribution and stack ranking

Forced distribution, sometimes called stack ranking, requires managers to place employees into predetermined performance categories or a relative order. It is a specific form of comparative evaluation, not a neutral measurement technique. If a system requires a certain percentage of low ratings, it can label someone as underperforming even when that person meets the role’s documented standard.

A 2013 study by researchers Samuel A. Culbert and colleagues, published in Organization Science, examined how performance rankings and employment outcomes can be shaped by organizational processes, rather than simply reflecting an objective measure of individual worth. The broader lesson is that a ranking is not self-validating: managers need to examine how goals, evidence, calibration, and workplace conditions produced it.

Coworker Comparisons Distort Rating Accuracy

A performance rating is useful only when it reflects relevant, reliable evidence. Comparing employees introduces additional influences, including who happens to be on the team, which projects were assigned, and what a manager remembers most vividly. These influences can make the same work look better or worse depending on the comparison group.

The comparison group changes the result

A comparison group is the set of coworkers used as a reference point for judging an employee. When teams differ in experience, resources, customer mix, or project difficulty, relative ratings can reflect those differences instead of individual contribution. An employee who handles a difficult account portfolio may appear less productive than a colleague with easier assignments, even if the first person creates greater value.

This is why review criteria should be role-specific and tied to factors employees can reasonably influence. The U.S. Office of Personnel Management’s performance-management guidance emphasizes establishing clear work expectations and assessing performance against them. Such standards make it easier to distinguish outcomes from circumstances that affected the work.

Recency, visibility, and halo effects

Recency bias occurs when recent events receive more weight than work completed earlier in the review period. Visibility bias favors contributions that are easy to notice, such as presenting in meetings, over less visible work such as mentoring, quality assurance, or preventing problems. A halo effect occurs when one positive trait influences judgments about unrelated areas; a similar spillover can occur when a manager’s overall impression shapes every rating.

Peer rankings can intensify these errors because managers are asked to make distinctions between people, even when the evidence does not support precise differences. A documented review record—with examples collected throughout the period—helps reduce reliance on memory and impressions. It should include both outcomes and relevant behaviors, such as collaboration, quality, and responsible decision-making.

Unequal opportunity and job context

Opportunity differences arise when employees have unequal access to high-profile projects, development, staffing, or customer exposure. If reviews reward visible wins without accounting for access, they may confuse opportunity with ability. Job context also matters: a person’s results may depend on team capacity, changing priorities, or external conditions beyond their control.

The U.S. Equal Employment Opportunity Commission advises employers to apply performance standards consistently and to ensure employment decisions are based on job-related criteria. A comparative process that relies on vague impressions or inconsistent opportunities can make it harder to explain why employees received different ratings. Reviewing the criteria and evidence for patterns across teams can help organizations identify where their process needs attention.

Comparative Reviews Can Weaken Collaboration and Trust

Performance reviews communicate what an organization values. If employees believe that helping a colleague could lower their own standing, they may protect information, avoid shared work, or compete for assignments that are easy to measure. Those reactions can undermine the very team outcomes that performance management is supposed to support.

Competition can discourage knowledge-sharing

Knowledge-sharing includes explaining processes, coaching coworkers, and passing along information that helps a team solve problems. In a highly competitive review system, employees may see these contributions as time spent improving someone else’s standing. That risk is especially relevant in work where outcomes depend on coordination, handoffs, or collective expertise.

A 2015 survey by the Society for Human Resource Management found that 72% of respondents identified teamwork and collaboration as an important workplace culture factor. The survey does not prove that ranking causes collaboration to fall, but it underscores a practical tension: organizations often say teamwork matters while using review systems that reward employees primarily for outperforming one another.

Perceived unfairness damages acceptance

Organizational justice is the perceived fairness of workplace decisions and the processes used to make them. In reviews, employees are more likely to understand a decision when expectations are clear, evidence is relevant, and they have a chance to discuss the outcome. A rank alone offers little explanation about what the person did well, what needs to change, or how the rating was reached.

Research by organizational psychologist Jerald Greenberg helped establish the importance of perceived fairness in workplace decisions. For practical review design, this points to three questions: Were the standards consistent? Was the evidence accurate and complete? Did the employee have a respectful opportunity to respond? Comparing colleagues without answering those questions can make a rating feel arbitrary, even if a manager intended to be objective.

Stress and short-term incentives

A competitive review system can encourage employees to prioritize measurable short-term wins over less visible, longer-term work. It may also increase anxiety when employees do not know whether their evaluation depends on meeting expectations or simply outranking peers. The impact will vary by organization, but unclear criteria and high-stakes rankings can make feedback feel like a threat rather than a tool for improvement.

Managers can reduce this risk by separating developmental feedback from pay or promotion decisions where practical, explaining how each decision is made, and setting goals before the review period begins. These steps do not eliminate difficult conversations; they make them more specific and less dependent on a colleague’s result.

Fairer Review Systems Measure People Against Clear Expectations

A fairer review system evaluates employees against role-relevant expectations while recognizing that no single metric captures every contribution. It can still use calibration to improve consistency across managers, but calibration should test whether standards are being applied similarly—not force employees into a predetermined order.

Set role-specific goals and evidence standards

Role-specific goals describe the outcomes and behaviors expected from a particular position. Good goals are clear enough to guide work, aligned with organizational priorities, and adjusted when responsibilities materially change. Evidence standards identify what documentation will support a rating, such as project results, quality measures, customer feedback, or observed behaviors.

For example, a review for a software engineer might consider reliability, maintainability, delivery against agreed scope, and collaboration—not just the number of features shipped. A customer-support review might include resolution quality and customer outcomes, while accounting for case complexity. The aim is not to make every role identical, but to make each role’s expectations understandable and defensible.

Use calibration to check consistency, not impose a curve

Calibration is a structured discussion in which managers review ratings and evidence to check whether comparable standards are being applied. It can reveal that one manager uses a rating more generously than another or that a team’s goals were unusually difficult. Calibration becomes problematic when it requires a fixed distribution regardless of the evidence.

A useful calibration meeting asks whether ratings are supported by examples, whether employees had comparable expectations, and whether relevant context has been considered. It should not ask which employee must be placed at the bottom simply because the system requires one. A written record of decisions and criteria also supports accountability and future process reviews.

Give continuous feedback and a right to respond

Continuous feedback means discussing progress throughout the performance period rather than saving concerns for an annual meeting. Regular check-ins allow goals to be adjusted, obstacles to be addressed, and positive contributions to be recognized while details are still fresh. Employees should also have a chance to add context, correct factual errors, and agree on next steps.

The annual review can then summarize a record of conversations instead of introducing surprising judgments. This approach supports development and makes it easier to identify whether a performance issue reflects a skill gap, unclear expectations, limited resources, or a mismatch between the role and the employee’s strengths.

Audit outcomes for patterns and unintended disparities

A review audit examines ratings, promotion outcomes, and access to opportunities across relevant groups and teams. It can help identify patterns that merit investigation, such as one department using substantially lower ratings or certain employees being less likely to receive stretch assignments. A pattern is a signal to examine the process, not by itself proof of discrimination or cause.

Organizations should protect confidential employee information and interpret results carefully, particularly when group sizes are small. The goal is to check whether criteria are applied consistently and whether the system creates avoidable barriers—not to replace individual evidence with another form of broad comparison.

Conclusion: Replace Ranking With Evidence-Based Review

Comparing team members during reviews can undermine fairness because ratings may shift with the comparison group, unequal opportunities, manager bias, and fixed ranking rules. It can also weaken collaboration when employees believe that helping coworkers threatens their own standing. Standards-based reviews, role-specific evidence, transparent calibration, ongoing feedback, and careful audits offer a more reliable path.

Organizations do not need to avoid meaningful distinctions in performance. They need to explain those distinctions with consistent expectations and evidence about each person’s work, rather than assuming that one employee’s success makes another employee’s contribution less valuable. Review your current criteria, remove any automatic ranking requirements, and train managers to document outcomes and context before the next review cycle.

Sources: Aguinis, Herman, Ernest O’Boyle Jr., and colleagues, “The Best and the Rest: Revisiting the Norm of Normality of Individual Performance,” Personnel Psychology, 2012, https://doi.org/10.1111/j.1744-6570.2011.01239.x; U.S. Office of Personnel Management, Performance Management, https://www.opm.gov/policy-data-oversight/performance-management/; U.S. Equal Employment Opportunity Commission, Employment Tests and Selection Procedures, https://www.eeoc.gov/laws/guidance/employment-tests-and-selection-procedures; Society for Human Resource Management, 2015 Employee Job Satisfaction and Engagement Survey, https://www.shrm.org/topics-tools/research/employee-job-satisfaction-engagement; Greenberg, Jerald, “Organizational Justice: Yesterday, Today, and Tomorrow,” Journal of Management, 1990, https://doi.org/10.1177/014920639001600208; Culbert, Samuel A., and colleagues, research on performance ranking and organizational outcomes, Organization Science, 2013.

Related Post