Brooks's Law

In the AI Story

The law's confirmation by the AI transition is stronger than its celebrators typically recognize. Brooks's Law was never refuted by the solo builder phenomenon. It was confirmed in its most extreme form. The solo builder has zero inter-human communication overhead. The entire communication burden consists of one person describing intention to one machine. There are no status meetings, no specification documents that lose fidelity at every handoff, no design reviews, no integration crises. The overhead that Brooks spent his career documenting has been eliminated — not by better management or better processes, but by removing the other humans from the loop entirely.

But the law's corollary is uncomfortable for both the triumphalists and the organizations that employed the teams the solo builder replaces. The roles that existed to manage communication overhead — project manager, technical lead, scrum master, program director — existed because of Brooks's Law. AI eliminated what they managed. The roles made necessary by the law are the roles made unnecessary by the tool that finally makes the law's optimal-size-of-one operationally feasible.

Communication overhead was always a cost. But it was also a mechanism for error correction. When multiple people worked on a problem, they brought multiple perspectives. The collision of perspectives produced understanding that no single viewpoint could generate. The solo builder, communicating only with an AI, loses this friction. The AI implements what she describes. It does not volunteer the specific, biographical, experience-based challenge that a human colleague provides. The gaps in the solo builder's understanding are, by definition, the things she does not know she does not understand — and they are revealed not by asking questions but by encountering someone who sees the problem from a different angle.

The law reformulated for the AI age might read: the communication overhead between a builder and an AI grows with the essential complexity of the project, and at some point the overhead of description, evaluation, and verification exceeds the capacity of a single person. At that point, the solo builder needs help — not implementation help, which the AI provides, but design help, specification help, the kind of help that comes from another mind that sees the problem differently.

Origin

Brooks formulated the law after OS/360, the operating system whose development taught him what no textbook could: that adding programmers to a late project did not rescue the schedule, it worsened it. He spent a decade distilling the lesson and named the pattern deliberately, because named things are harder to ignore. The industry proved remarkably resourceful at ignoring it anyway, repeating the error on project after project for fifty years.

Key Ideas

The arithmetic is quadratic. Channels grow as n(n−1)/2. Double the team, quadruple the communication burden.

The optimal size was always one. Brooks's Law predicts that zero communication overhead is the theoretical minimum, achievable only with a single person.

AI operationalizes the optimum. What was theoretically optimal and practically impossible in 1975 is now practically feasible for a growing class of work.

Overhead served functions beyond coordination. Team communication provided cognitive diversity, error correction, and temporal structure — all lost when the team is eliminated.

The law's corollary threatens management roles. The coordinators whose roles existed to manage overhead are made unnecessary by the tool that removes it.