CONCEPT
The Surgical Team Model
Brooks's 1975 organizational proposal for software development — a small team built around a chief programmer (the surgeon) supported by specialists — preserving the conceptual integrity of the single mind while providing the support that mind needs.
Borrowed from Harlan
Mills's 1971 proposal at IBM, the
surgical team model reorganizes software development around the recognition that one programmer should design and build the system while others handle the surrounding functions. The surgeon does the work that requires the unified vision; the copilot acts as deputy; the administrator handles organizational concerns; the editor refines communication; the secretary manages records; the toolsmith builds the supporting infrastructure; the tester challenges the work; the language lawyer resolves questions about the
programming language. The model preserves
conceptual integrity by keeping design authority concentrated, while providing the support that keeps the surgeon operating at peak productivity. The AI transition has reproduced this structure in a new form:
the solo builder is the surgeon, and the AI system plays every supporting role simultaneously.
In The You On AI Field Guide
Brooks advocated the model because it resolved a tension in the man-month analysis. Large teams