Brooks's Law
Adding people to a late project makes it later, because coordination costs grow faster than the extra hands help.
Why PMs should care
The cost of coordinating a team grows faster than the team itself. Every new person needs onboarding — on the code, the product, the stakeholders — and a ramp-up period during which they're using more attention from senior engineers than they're producing in output. The team's short-term output drops before it climbs, often past the deadline you were trying to save.
Brooks's insight has survived fifty years because the underlying truth isn't about culture — it's about structure. Software is a communication problem wrapped around a technical one, and throwing more people at a communication problem makes it worse.
The right responses to 'we're behind' are almost always: cut scope, extend the deadline, or replace people who aren't productive. 'Add more people' is the response stakeholders prefer, because it's visible. It's also the response that most reliably fails.
Example in product work
A feature is four weeks behind on a ten-week plan. A concerned VP suggests 'throw two more engineers at it'. The team reluctantly complies.
— Week 1: the lead engineer spends three full days pair-programming the new hires through the codebase and stakeholder context.
— Week 2: the new hires are producing code, but in areas the lead doesn't fully trust yet and needs extra review.
— Week 3: the team catches up on the review backlog, but a merge conflict between two of the new hires costs a day.
— Week 4: actual forward progress resumes.
The feature ships six weeks late instead of the four it was originally tracking.
In the retro, someone will say 'imagine how late it would have been without the extra headcount' — and nobody will have the counter-evidence.
What to do when you see it
- Every new person needs onboarding, context, and ramp-up — they consume more time from senior engineers than they produce at first.
- The team's short-term output goes down before it goes up, often past the deadline you were trying to save.
- Software is a communication problem wrapped around a technical one. Throwing people at communication problems makes them worse.
- The real answers to 'we're behind' are: cut scope, extend the deadline, or replace under-performing people. Adding people is the answer stakeholders prefer and the one that most reliably fails.
Sources & further reading
- The Mythical Man-Month — Frederick P. Brooks, 1975The original book where Brooks articulated the law, based on his experience managing IBM's OS/360.
- No Silver Bullet — Brooks, 1986Brooks's follow-up essay that expands on why software complexity resists simple management fixes.