Brooks’s Law

Brooks’s Law appears in We almost had a smartphone in the 90s. Why did it fail? as a warning that adding people to a late project can make it later. The episode uses it to interpret General Magic’s large partner and talent base: more people, companies, and ideas increased coordination needs while the product remained unclear.

The concept’s role in this wiki is project-management discipline. Extra capacity can help only when the work is decomposable, priorities are stable, and communication overhead does not outrun the added labor.

Key Claims

• Adding people adds communication paths, onboarding load, and alignment work.
• The risk is larger when goals, customers, and interfaces are unresolved.
• Brooks’s Law connects staffing decisions to Clear Customer Definition and Constraint-Driven Product Discipline, not only to calendar math.

Connections

• General Magic - source case where talent and partner scale did not create speed.
• Feature Creep and Premature Ecosystem Build - related complexity patterns.
• Product Launch Under Constraint and Parkinson’s Law - adjacent management and deadline concepts.