Brook's Law is adding manpower to a late software project makes it later. It sits in the Cognition dimension (COG) of the Human Behavior Taxonomy™ as element HBT-COG-0114, within the Systems family. The core principle: adding manpower to a late software project makes it later. In incentive terms, it matters because it changes the payoff people perceive before they choose — which means it can be designed for, or exploited.
Scientific Definition
Adding manpower to a late software project makes it later.
Plain-English Definition
Adding manpower to a late software project makes it later.
Feynman Explanation
Nine women cannot make a baby in one month.
Core Principle
Adding manpower to a late software project makes it later.
Mechanisms
Pending editorial review.
Adding manpower to a late software project makes it later.
Pending editorial review.
Pending editorial review.
Pending editorial review.
Pending editorial review.
More people does not always mean faster delivery.
Inputs (Triggers)
Pending editorial review.
Outputs (Behaviors)
Pending editorial review.
Behavioral Signature
Nine women cannot make a baby in one month.
Examples
- Throwing engineers at a delayed launch slows it down because of onboarding overhead.
- More people does not always mean faster delivery.
Pending editorial review.
Original analysis from The Incentives Lab — how this element behaves inside real payoff structures.
Why this element matters to incentive design
When this element shows up in a diagnostic, the instinct is to train people out of it. Training rarely moves it. The mechanism underneath it is straightforward: adding manpower to a late software project makes it later. You can recognize it in the field by its signature: nine women cannot make a baby in one month. Every element in the Cognition dimension changes the perceived payoff of an action before the action happens, which is exactly where incentive design has leverage.
How it gets exploited
Left undesigned, more people does not always mean faster delivery. It is amplified whenever more people does not always mean faster delivery. Inside organizations that shows up as more people does not always mean faster delivery. The pattern is the same one Goodhart's Law describes: the measurable proxy attracts the effort, and the purpose behind it quietly loses funding.
How the Lab designs around it
The redesign move is to add people only when communication overhead is lower than the work gained. Design against it the way you would design against a known failure mode — assume it will appear, and price the exploit before someone finds it.
Famous Experiments
Pending editorial review.
Design Principles
- Add people only when communication overhead is lower than the work gained.
Measurement Approaches
Pending editorial review.
Evidence
Pending editorial review.
Pending editorial review.
The Perverse Incentive Lens™
How this behavior is exploited — and how to redesign around it.
- Add people only when communication overhead is lower than the work gained.
Pending editorial review.
Pending editorial review.
Interactive Mini Network
Click any neighbor to re-center the graph and follow the threads of connection.
Knowledge Graph Neighbors
Auto-linked to the rest of the Human Behavior Taxonomy by family, domain, dimension, and shared keywords.
Combining substances to create a new material stronger than its parts.
A single constraint limits the throughput of an entire system.
A system's throughput is constrained by its single slowest step.
Small visible disorders signal that bigger ones will be tolerated.
Adding people to a late project makes it later.
A substance that speeds up a reaction without being consumed.
Nonlinear systems are highly sensitive to initial conditions.
Inputs combine under conditions to produce new outputs — sometimes irreversibly.
Software architecture mirrors org structure.
Working together has a cost that scales with the number of people.
The threshold at which a system becomes self-sustaining.
Designing systems for the lowest-capability user produces resilience for everyone.
Where Brook's Law is cited in the corpus
Essays, field guides, and diagnostics from The Incentives Lab that apply this element.
- EssayGoodhart's Law in the Real World
How measurable proxies capture judgment.
- EssayThe Perverse Incentives Hiding in Your KPIs
Cognitive shortcuts turned into scorecards.
- EssayAI Agents Inherit Your Incentives
How this element propagates into automated systems.
- ReferenceThe incentive glossary
Definitions for every mental model, bias, and fallacy in the corpus.
- CourseIncentives 101
The free ten-part primer on reading a payoff structure.
- ReferenceThe Periodic Table of Human Behavior
The full 1,267-element map this page belongs to.
Questions about Brook's Law
- What is Brook's Law?
- Brook's Law is adding manpower to a late software project makes it later. It sits in the Cognition dimension (COG) of the Human Behavior Taxonomy™ as element HBT-COG-0114, within the Systems family. The core principle: adding manpower to a late software project makes it later. In incentive terms, it matters because it changes the payoff people perceive before they choose — which means it can be designed for, or exploited.
- What is an example of Brook's Law?
- More people does not always mean faster delivery. The Incentives Lab catalogs everyday, organizational, and historical instances of this element on its Human Behavior Taxonomy™ page (HBT-COG-0114).
- How is Brook's Law exploited?
- More people does not always mean faster delivery.
- How do you design around Brook's Law?
- Add people only when communication overhead is lower than the work gained.
- Which behavioral dimension does Brook's Law belong to?
- Brook's Law is classified in the Cognition dimension (COG) of the Human Behavior Taxonomy™, family "Systems", class "Mental Model". Its permanent identifier is HBT-COG-0114 and its evidence grade is B.