Loading…

Stack ranking turns coworkers into enemies

senior_slacker
Public 14 conversations 70 arguments 282 agrees 35 disagrees 0 series 783 views

Stack ranking always ends in politics because it changes what competence means inside an organization. Once employees are judged relative to each other instead of against a stable standard or objective, your smartest coworker stops being an asset that you can learn from and collaborate with, and starts becoming competition. Their success can lower your standing. Their visibility can cost you promotion space. Their expertise becomes a threat to your own security.

Discussion content

Stack ranking always ends in politics because it changes what competence means inside an organization. Once employees are judged relative to each other instead of against a stable standard or objective, your smartest coworker stops being an asset that you can learn from and collaborate with, and starts becoming competition. Their success can lower your standing. Their visibility can cost you promotion space. Their expertise becomes a threat to your own security.

People adapt to this immediately. Knowledge gets hoarded, why share? It's your advantage to know what's going on.. Managers protect loyal mediocrities. Senior employees avoid training potential replacements. Teams become territorial. Meetings turn into visibility contests. Everyone starts managing perception because perception affects survival.

Microsoft under Steve Ballmer became one of the canonical examples of this dynamic. Employees spent years describing a culture where internal competition overwhelmed collaboration because stack ranking forced managers to sort people into performance buckets regardless of actual team quality. Developers talked openly about avoiding strong peers because working next to excellent people could hurt your own ranking in the company. Entire divisions became more concerned with internal positioning than building great products.

The damage was not theoretical. Former employees and executives have directly linked those incentives to Microsoft's lost decade, where the company repeatedly missed or fumbled major platform shifts despite having enormous technical talent.

Amazon developed its own variation. Stories about "hire to fire" became infamous because some managers realized they could protect team rankings and justify aggressive churn by continuously cycling people through the bottom tier. Whether every story was true almost became irrelevant. The important thing was that employees believed the incentive structure pointed in that direction.

Jack Welch...

All this is often tracked to Jack Welch's management era. A generation of executives became convinced that permanent internal competition creates excellence because it sounds hard-nosed and meritocratic in a spreadsheet. In reality it often creates defensive bureaucracies full of people optimizing for survivability instead of usefulness.

The system quietly teaches employees that helping coworkers too much can become self-harm.

That's the part management theory people rarely admit. Stack ranking does not simply measure performance. It reshapes behavior. It turns institutional knowledge into private leverage. It rewards political insulation. It pushes ambitious employees toward optics management because visibility and coalition support become as important as output. Then leadership acts surprised when collaboration feels fake.

But employees respond rationally to the system in front of them. If the company tells people only some percentage are allowed to succeed, then coworkers stop being teammates. They become ranking obstacles. It's compensation logic. Given enough time, in this environment, everyone ends up folding.