CONCEPT
The Coordination Bottleneck
The constraint that governed software development for fifty years — the quadratic communication overhead of multi-mind production — and which the language interface shattered in the winter of 2025.
The coordination bottleneck is the Goldratt simulation's name for the constraint that dominated knowledge-work systems from roughly 1970 through 2025: the overhead of coordinating multiple human minds to produce complex work. Fred Brooks formalized part of this insight in The Mythical Man-Month (1975), observing that adding people to a late software project makes it later. The mathematics are elementary and merciless: n people require n(n-1)/2 communication channels for full mutual awareness — a quadratic function that means a team of twenty requires one hundred ninety communication pathways, each a potential site of misalignment, delay, and information loss. This was the constraint. It was not widely recognized as a constraint because management frameworks were designed to treat it as overhead rather than bottleneck.
In The You On AI Field Guide
The anatomy of coordination overhead in a typical product development cycle reveals why the constraint was so binding. A product manager writes a specification — a lossy compression of her knowledge into a format engineers