Skip to main content
HR & People

Forced Ranking: Why Rank-and-Yank Performance Systems Fell Out of Favor After Widespread Early Adoption

A system requiring managers to rank every employee against each other, rather than against an absolute standard, produces predictable side effects that eventually outweighed its original appeal for many organizations.

Key Takeaways
  • Forced ranking systems require managers to rank employees against each other into predetermined performance categories, rather than evaluating each person against an absolute standard
  • This relative comparison structure creates specific incentives toward internal competition and reduced collaboration, since a colleague's strong performance can directly work against your own relative ranking
  • Several large organizations that adopted forced ranking prominently, sometimes with public results, later moved away from the practice after documenting these specific side effects internally
  • The core lesson generalizes beyond forced ranking specifically: any performance system's structure shapes real behavior, not just its stated evaluative intent

A forced ranking performance management system, requiring managers to sort every employee into predetermined performance tiers relative to their peers rather than evaluating each person against a fixed, absolute standard, was adopted prominently by a number of major corporations in the late twentieth and early twenty-first centuries, several of which later abandoned the practice after internal experience revealed specific, predictable side effects that outweighed the system's original intended benefits.

What forced ranking actually requires, structurally

Under a forced ranking system, a fixed percentage of employees within a given group must be placed in each performance tier regardless of the group's actual absolute performance distribution — meaning even a team where every member is performing at a genuinely high absolute level will still have some members placed in lower relative tiers, purely because the system requires a distribution rather than allowing every employee to be rated highly if they genuinely all deserve it.

Why this specific structure creates a predictable incentive problem

Because ranking is relative to peers rather than absolute, a colleague's strong performance can directly and mechanically work against an individual's own ranking outcome, in a way that a purely absolute performance standard doesn't create — this introduces a structural incentive toward internal competition, and in some documented cases, toward reduced collaboration or information sharing between colleagues who are effectively competing against each other for a limited number of favorable ranking slots, independent of how well the team collectively performs.

Why this played out publicly at several well-known organizations

A number of prominent companies that adopted forced ranking in a highly visible way later moved away from the practice, with internal and external commentary specifically citing reduced collaboration, unhealthy internal competition, and employee perception of unfairness as key factors in the reversal — the specific incentive problems forced ranking's relative structure creates weren't merely theoretical concerns raised by critics in advance, they were documented consequences these organizations experienced directly after sustained use of the system.

The broader lesson this pattern illustrates

The specific failure mode of forced ranking illustrates a more general principle relevant well beyond this one particular system: how a performance evaluation is structured shapes real employee behavior directly, independent of and sometimes at odds with its stated evaluative purpose — a system explicitly designed to differentiate performance can, through its relative rather than absolute comparison structure, actively discourage the collaborative behavior an organization needs in order to perform well collectively.

What this means for organizations designing performance evaluation systems

  • Consider whether a proposed evaluation structure creates incentives toward internal competition that could undermine collaboration, before adopting it
  • Prefer absolute performance standards over relative, forced-distribution ranking wherever team-based or collaborative outcomes matter significantly
  • Look specifically at the documented experience of organizations that adopted and later abandoned forced ranking as a source of concrete, practical evidence, not just theoretical critique
  • Evaluate any performance system explicitly for its likely behavioral incentives, not only for how cleanly it differentiates performance levels on paper

Forced ranking's rise and subsequent retreat is a genuinely instructive case study in how a performance system's structural mechanics — not just its stated evaluative goals — determine the actual behavior it produces inside an organization.

forced ranking performance managementstack ranking controversyrelative performance evaluationpeople analyticsperformance review systems