In 1975, Fred Brooks published The Mythical Man-Month. Fifty years later, it remains the most consistently ignored book in software engineering.
Brooks’ Law: “Adding manpower to a late software project makes it later.”
It seems impossible. More people, more capacity, faster delivery. Brooks says the opposite. He was right fifty years ago. He is right now.
Why It Happens
New people don’t arrive productive. They arrive disoriented. Someone has to onboard them, explain the codebase, answer their questions, review their early output. That someone is already on the critical path. While they are onboarding the new hire, they are not doing the work the project depends on.
Communication overhead compounds this. Two people share one relationship. Five people manage ten. Ten people carry forty-five. Every new connection in the network is a coordination cost — another channel where misunderstandings can propagate, another meeting that needs to happen, another context that needs to be shared before a decision can be made.
Tasks that were simple when two people shared deep context become genuinely complex when eight people who don’t share it try to coordinate on the same problem.
What Leaders Do Instead
The instinctive response to a late project is to add resources. It feels decisive. It signals urgency to stakeholders. It is almost always wrong.
I have watched teams sit on a backlog item for eighteen months — tagged “four to six months if we ever get to it” — while the org debated priorities and resource allocation. When four focused people were finally freed to work on it, they shipped it in three weeks. The constraint was never capacity. It was priority and the coordination overhead that accumulated while the team was half-attending to a dozen other things simultaneously.
Adding more people to that situation would not have helped. It would have added more relationships to manage, more competing contexts to reconcile, and more dependencies to coordinate — on top of an already overloaded team.
What This Means for How You Staff
The answer is not larger teams. It is smaller, more focused ones.
Three things Brooks’ Law actually demands of you:
-
When a project is late, cut scope before you add people. Define the minimum that must ship and protect it from interruption. Adding people to a late project accelerates the coordination overhead before it adds any productive capacity.
-
Reduce the number of people who need to coordinate on each decision. Brooks called this the surgical team model: one person makes the cuts; everyone else keeps the field clear. The goal is to minimise, not maximise, the number of people with a stake in each decision.
-
Diagnose the constraint before reaching for headcount. Late projects are almost never short of people. They are short of focus, priority, or scope clarity. Headcount is a solution to an entirely different problem — and adding it to the wrong problem makes both problems worse.
The instinct to add resources is a response to anxiety, not a diagnosis of the problem. That distinction is worth holding onto the next time a deadline slips.
Think about the last project that slipped. Was the problem too few people, or too much noise?
The Laws They Don’t Teach series:
Leave a Reply