"Adding manpower to a late software project makes it later"
About this Quote
Brooks lands a tiny grenade in the middle of managerial common sense: the instinct to throw bodies at a problem doesn’t just fail in software, it backfires. The line works because it flips an industrial-era metaphor on its head. In factories, labor is often additive; in software, labor is entangled. A “late project” isn’t late because it lacks hands, it’s late because it has complexity, uncertainty, and mismatched understanding. Adding people increases the surface area where misunderstanding can breed.
The subtext is a critique of command-and-control thinking. Managers want a lever they can pull that looks decisive, measurable, morally satisfying: hire, reassign, “all hands.” Brooks, writing from the trenches of large systems work, points out the hidden tax: onboarding time, knowledge transfer, coordination overhead, rework from diverging assumptions, and the social friction of shifting ownership midstream. Communication paths don’t scale linearly; they explode. The new hires need context, and the people who have context are the very ones already trying to save the schedule.
Context matters: Brooks formulated this in the era of IBM’s massive, high-stakes software efforts and later crystallized it in The Mythical Man-Month, when “software engineering” was still trying to pretend it could be managed like civil engineering. The aphorism became canonical because it names a pattern everyone in tech has lived through: the panic-staffing spiral that converts urgency into chaos.
Its sting is also ethical. “Manpower” reduces people to interchangeable units; Brooks insists, quietly, that creativity and shared mental models are the real scarce resources. You can’t sprint your way out of a coordination problem.
The subtext is a critique of command-and-control thinking. Managers want a lever they can pull that looks decisive, measurable, morally satisfying: hire, reassign, “all hands.” Brooks, writing from the trenches of large systems work, points out the hidden tax: onboarding time, knowledge transfer, coordination overhead, rework from diverging assumptions, and the social friction of shifting ownership midstream. Communication paths don’t scale linearly; they explode. The new hires need context, and the people who have context are the very ones already trying to save the schedule.
Context matters: Brooks formulated this in the era of IBM’s massive, high-stakes software efforts and later crystallized it in The Mythical Man-Month, when “software engineering” was still trying to pretend it could be managed like civil engineering. The aphorism became canonical because it names a pattern everyone in tech has lived through: the panic-staffing spiral that converts urgency into chaos.
Its sting is also ethical. “Manpower” reduces people to interchangeable units; Brooks insists, quietly, that creativity and shared mental models are the real scarce resources. You can’t sprint your way out of a coordination problem.
Quote Details
| Topic | Management |
|---|---|
| Source | Frederick P. Brooks, Jr., The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley, 1975. Original source of the maxim later called "Brooks's Law": "Adding manpower to a late software project makes it later." |
More Quotes by Frederick
Add to List
