The Great Competition Myth
Why Your Organisation Competes With Itself and Why That’s a Design Choice, Not a Mindset Problem
From the first graded test to the first performance review, we’re taught that competition is the engine of progress, that to get ahead, you must outperform the person beside you. Most organisations are built on that belief. They rank, they grade on a curve, they reward relative standing. And then they’re puzzled when their people hoard information, hide mistakes, and optimise for looking better than their colleagues rather than for the result the organisation actually needs.
That behaviour isn’t a culture problem to be fixed with a values campaign about collaboration. It’s a structural output. People compete with each other because the architecture pays them to, and they’ll keep competing no matter how many times leadership preaches teamwork, because they’re reading the incentives correctly.
Competition and collaboration are behaviours, not mindsets
The common framing treats these as character traits – some people are competitive, some collaborative, and the job is to cultivate the better attitude. That framing is why so much effort fails. Put a naturally collaborative person on individual commission against their teammates and watch them start guarding their pipeline. Put a fierce competitor in a structure where the only reward is the team’s collective outcome and watch them start coaching the people around them. Neither one had a change of heart. The architecture changed what behaviour paid off, and the behaviour followed.
So the question is never “How do we make our people more collaborative?” It’s “What is our structure actually rewarding?” And in a surprising number of organisations, the honest answer is: zero-sum behaviour, installed by accident.
How organisations engineer the destructive kind
Three structural choices reliably manufacture internal competition, and each carries a hidden cost.
The first is forced ranking, stack-ranking, curves, and “top performer” designations that are relative by construction. When standing is relative, the rational move isn’t to do excellent work; it’s to be marginally better than the person next to you, which caps ambition at incrementalism. Why attempt the breakthrough that might fail when you only need to clear the colleague beside you? The structure rewards beating a rival, so people optimise for the rival, not the problem.
The second is what you might call the secrecy tax. When pay, promotion, or status depends on relative standing, sharing what you know becomes a cost. Mistakes get hidden because admitting one lowers your rank. Hard-won knowledge gets guarded because handing it over helps a competitor.
The organisation ends up paying, again and again, for the same errors, because the architecture made honesty about failure personally expensive, so no one’s failure ever teaches anyone else anything.
The third is isolating individual accountability from collective outcome. When a person’s reward is tied purely to their individual number and disconnected from whether the whole effort succeeded, collaboration becomes a tax on personal reward; time spent helping a colleague is time not spent on your own metric. The structure has made the cooperative act irrational, and then the leadership wonders why people won’t cooperate.
Why this is the expensive choice
None of this is an argument that competition is bad and collaboration is virtuous because that’s just swapping one mindset slogan for another.
It’s that internal zero-sum competition is usually a structural mistake, because it pits the organisation against itself. Complex problems need different perspectives in genuine contact with each other; an architecture that makes people guard their thinking starves itself of exactly the friction that produces breakthroughs.
Progress depends on errors becoming shared knowledge; an architecture that makes failure career-lowering guarantees errors stay private and get repeated.
The organisation built to make its people compete with each other is, in effect, taxing its own intelligence and calling it performance management.
Note what this doesn’t say. It doesn’t say competition has no place. Competition with the external environment: The market, the problem, and the standard of excellence, is often exactly what an organisation should structure for.
The error is pointing the competitive pressure inward, at colleagues, where it converts what should be a shared effort into a set of rivals optimising against each other.
Well-designed systems compete hard outward and collaborate hard inward.
Badly-designed ones do the reverse, and exhaust themselves.
The accountability question, answered structurally
The usual objection to all this is that collaboration dissolves individual accountability: If everyone shares, who’s responsible? But that gets the architecture backwards. In a relative-ranking system, accountability is actually easy to dodge: hide the mistake, shift the blame, protect your standing. It’s the structure itself that rewards evasion.
In a system where reward is tied to collective outcome, and individual contribution is visible within it, accountability sharpens rather than dissolves.
Think of a surgical team or an orchestra: Every individual has to perform at the height of their personal mastery, and there’s nowhere to hide, precisely because the collective result depends on each visible part. That’s not the absence of individual excellence. It’s individual excellence made structurally legible, with the incentive pointed at the shared outcome rather than at outscoring the person next to you. Collaboration done well doesn’t erase the individual; it gives individual mastery a structure in which it actually compounds instead of cancelling out.
The redesign
So the move isn’t to run a campaign telling people to be less competitive and more collaborative because that’s exhortation against the grain of the incentive, and it always fails the way all such campaigns fail.
The move is to look at what the architecture rewards and ask whether it’s pointing competition inward or outward.
Does standing depend on beating colleagues or on meeting the problem?
Does sharing a mistake cost the person who shares it, or does the system make failure a source of collective learning?
Is individual reward severed from collective outcome, or connected to it?
Change those, and the behaviour changes on its own without a single workshop about teamwork. Leave them, and no amount of values-talk will produce collaboration, because you’ll be asking people to act against what your own structure pays them to do. The person who wins the internal race is still just outrunning a colleague.
The organisation that stops staging the internal race and points all that competitive energy at the actual problem is the one that moves.