Why the worse technology won
The better standard doesn’t always win. A tiny early lead, compounded, can starve a superior rival to death.
The keyboard you’re typing on was designed to slow people down. It beat faster layouts anyway. Half the famous standards wars — tape formats, disk drives, programming runtimes — ended with the technically weaker option owning the market for decades.
That keeps surprising people because we assume markets reward merit. They don’t reward merit; they reward momentum. And momentum has a structure: Success to the Successful, the engine of path dependence.
Two reinforcing loops, racing
Each standard sits inside its own reinforcing loop (R). The more people adopt Tech A, the stronger its network effects, which attract more adopters. Separately, more A adoption pulls in more developer support — complements, integrations, tooling — which again drives adoption.
Either loop alone produces runaway growth. Together they compound. The same two loops exist for Tech B. On their own, the two engines would each just grow. What makes this a battle is that they’re wired into the same scarce resource.
The figure-eight and the finite pool
Developers, users, and investment aren’t unlimited. The two reinforcing loops cross in the middle — a figure-eight — competing for one pool. Notice the edge from developer support to Tech B adoption is negative: every builder who commits to A is one B will never get.
That coupling is what turns two growth stories into a winner-take-all race. The pool that feeds A is drained from B. Each turn of A’s loop doesn’t just help A — it actively starves the rival.
Why a tiny early lead decides everything
Set the two technologies nearly equal — A merely a hair ahead — and run the simulation above. A’s small lead lets it capture slightly more developers and investment, which widens the lead, which captures still more. B, equally good, gets squeezed out of the shared pool before its own loops can spin up.
This is why timing and early wins matter more than quality in standards markets, and why lock-in is the closer: as switching costs accumulate (with a delay), even users who’d prefer B can’t justify leaving. The outcome gets frozen — not because A is better, but because A got there first and the structure did the rest.
The leverage point
Success to the Successful is only inevitable if allocation stays tied to the current lead. Break that link and merit gets a chance.
- Decouple allocation from standing. If developers, funding, or procurement chose on quality rather than on who’s already winning, the negative edge starving B weakens.
- Protected niches. A reserved beachhead lets the rival’s own reinforcing loops spin up out of reach of the dominant pool — many comebacks start in a segment the leader ignored.
- Interoperability and antitrust. Standards that interoperate turn the finite pool into a shared one, so adopting A no longer means abandoning B — which is precisely why incumbents resist it and regulators sometimes mandate it.
The lesson for a strategist: in a path-dependent market, racing for an early lead beats polishing a better product, and the policy fight over interoperability is the real battlefield.
This system is an instance of Success to the Successful — read the full pattern.
Hebel is launching soon. Join the early list and lock in 30% off — plus 10% more per friend you bring.