Skip to main content

Welcome to a Grasp lesson

Create a free account to keep studying and create your own study path.

Lesson 36

Brooks' Law: Why Adding Resources Can Delay Progress

Recommended resources

In our last lesson, we confronted the hard realities of Hofstadter's and Cheops' Laws, which tell us that complex projects will almost inevitably take longer and cost more than we plan. This naturally leads to a critical question: when a project is falling behind, what should we do? The most common, intuitive answer is to add more resources. Today, we will scrutinize this impulse through the lens of Brooks' Law.

Brooks' Law offers a stark and counterintuitive warning: "Adding manpower to a late software project makes it later." This principle, originating from software engineering, has profound implications for any complex, collaborative endeavor. Our goal is to apply this law to your specific areas of interest: explaining why adding more seamstresses to a late lingerie order can cause further delays, and why involving more people in a strained relationship discussion can postpone, rather than hasten, resolution.

The Anatomy of Brooks' Law

Before applying the law, we need to understand its underlying mechanisms. Why would adding capable people to a project be counterproductive? The answer lies in the hidden costs of scaling a team, which are often non-linear.

To begin, let's watch a short video that introduces the core idea and origins of Brooks' Law.

182. Lessons From "The Mythical Man-Month" | THUNK

The video "Lessons From 'The Mythical Man-Month'" provides a concise summary of Fred Brooks's key arguments.

Watch the segment from the introduction to Brooks's Law. Pay close attention to the distinction between tasks that are easily divisible (like folding laundry) and those that are not, and how communication overhead becomes the dominant factor.

The video identifies the two primary culprits: task partitioning and coordination overhead. The more a task requires communication and shared understanding among its participants, the less it benefits from adding more people. Let's break this down further.

The Quadratic Cost of Communication

As you know from your background in statistics, not all growth is linear. The number of communication pathways in a group doesn't grow in proportion to the number of people; it grows quadratically. The formula is simple but its implications are dramatic: for a team of people, the number of potential one-to-one communication channels is .

  • 2 people = 1 channel
  • 3 people = 3 channels
  • 5 people = 10 channels
  • 10 people = 45 channels
This graph and diagram illustrate the exponential increase in communication lines as the number of people in a group grows. Each new person adds not one, but n-1 new potential communication links.

This explosion of communication channels creates overhead. Time that could be spent on productive work is instead consumed by meetings, emails, and clarifications, increasing the chances of miscommunication and error.

Onboarding and Task Divisibility

Beyond communication, there are two other key factors:

  1. Onboarding Costs: New members are not instantly productive. They need to learn the project's history, its specific methods, and the team's culture. This "ramp-up" time consumes the valuable attention of your most experienced team members, temporarily reducing the team's overall productivity.
  2. Limited Task Divisibility: Some tasks cannot be neatly divided. The classic analogy, which you'll find in the following reading, is that "nine women can't make a baby in one month." Many complex tasks have a sequential component that no amount of extra manpower can accelerate.

To explore these concepts in more detail, let's turn to a clear and practical article.

Brooks' Law: Adding Manpower to a Late Project Makes It Later

This article from Effectiviology breaks down the rationale behind Brooks' Law and generalizes it beyond software development.

Please read two sections of this article: Start with the Examples of Brooks' Law. This section introduces the famous "nine women" analogy. Then, read the section on the Rationale behind Brooks’ law, which explicitly lists the key issues: teaching time, learning time, communication overhead, and limited divisibility.

These factors combine to create a point of diminishing, and eventually negative, returns. Adding people can help up to an "optimal team size," but beyond that point, the coordination costs outweigh the benefits of additional labor, and the project completion time actually increases.

This graph illustrates the core concept of Brooks' Law. As the number of people on a project increases, the time to completion initially decreases, but only up to an optimal point. Beyond this, the rising coordination costs lead to delays.

Now, let's apply this framework to our two scenarios.


Application 1: The Late Lingerie Order

Imagine you have a small bespoke lingerie business. A client has ordered an elaborate, custom-fit wedding bustier that is promised for a specific date. Due to an unforeseen delay in receiving the specialty French lace, the project is a week behind schedule. Your immediate thought is to bring in two freelance seamstresses to work with your primary seamstress to "catch up."

Brooks' Law predicts this will make the project even later. Here's why:

  • Onboarding Cost ("Teaching Time"): Your primary seamstress, the only one who fully understands the intricate pattern and the client's specific measurements, must stop sewing. She now spends her time teaching the freelancers. They need to learn the unique construction sequence, the delicate handling required for the lace, and the precise tension settings on the machines. For the first day or two, the team's net output is less than when the single seamstress was working alone.
  • Communication Overhead: With three people working, coordination becomes a problem.
    • Seamstress A to B: "Did you already cut the boning channels for the left side?"
    • Seamstress C to A: "Which thread are we using for the topstitching? The client's notes are ambiguous."
    • The single communication channel between you and your seamstress has now become three channels among the seamstresses, plus three more channels for you to manage them. The risk of one person sewing a panel with the wrong seam allowance because they weren't in the loop on a small adjustment has skyrocketed.
  • Limited Task Divisibility: A bustier is not like picking cotton; it's a sequentially constrained project. You cannot attach the busk closure until the front panels are complete. You cannot stitch the boning channels until the main body is assembled. Crucially, tasks requiring high consistency, like attaching the delicate lace appliqué across multiple panels, cannot be effectively partitioned. Having three people work on it at once would likely result in visible inconsistencies, requiring rework that pushes the schedule back further.

Instead of accelerating, the project grinds to a halt with questions, coordination meetings, and quality control checks. The original seamstress becomes a bottleneck, and the final delivery is even later than if she had been left to work diligently by herself.


Application 2: Resolving Tension in a Vee Relationship

Consider the vee relationship: a husband (H) supports his wife's (W) relationship with her partner, the metamour (M). Tensions have arisen around time management and emotional security. The "project" is to resolve these tensions and find a stable, happy equilibrium. The project is "late" because the tension has persisted longer than anyone is comfortable with.

A common impulse is to add more people to the "team" to help solve the problem. This could mean involving the metamour (M) in every discussion between H and W, bringing in a therapist (T), or confiding in a group of trusted friends (F).

Brooks' Law provides a powerful lens for why this often backfires:

  • Onboarding Cost ("Emotional Ramp-Up"): A therapist needs weeks or months to learn the relational history, communication patterns, and individual attachment styles. This is "ramp-up" time. Friends, with an incomplete picture, may offer advice based on their own normative assumptions (often monogamous), requiring H or W to spend emotional energy "onboarding" them to the nuances of polyamory, time that could be spent addressing the core issue.
  • Communication Overhead: This is where the model is most potent.
    • The core H-W dyad has 1 communication channel.
    • Adding M to all discussions creates a triangle: H-W, W-M, H-M. That's 3 channels. The risk of triangulation, where one person relays information (or feelings) between the other two, is now present.
    • Bringing in a therapist creates a 4-person system with 6 channels.
    • Confiding in two trusted friends creates a 5-person system with 10 channels.
      The "work" of resolving the issue is now buried under an avalanche of coordination: scheduling meetings, ensuring everyone has the same information, managing hurt feelings from misinterpretations, and processing the opinions of all involved. The original conflict between H and W can get lost in the noise.
  • Limited Task Divisibility & Team Dynamics: The "task" of, for instance, H processing his feelings of insecurity is not divisible. It is his internal work. While W's reassurance is a key input, adding more people to that specific process can feel intrusive and counterproductive. Furthermore, as your social research background suggests, adding new members can reset the group's developmental stage. A couple who has achieved a "performing" level of communication (using Tuckman's model) might be thrown back into a "storming" phase when a new person's perspective introduces conflict, or a "forming" phase as they struggle to establish new group norms.

To understand these dynamics on a deeper, more technical level, the following resource connects Brooks' Law directly to network theory and team psychology.

The Team Paradox Through the Network Lens: Brook's Law ...

This article by Miralem Mašić uses Organizational Network Analysis (ONA) to provide a quantitative and structural explanation for Brooks' Law.

This is a more advanced take that aligns well with your background. Please read the following sections: The first section gives a solid recap of the core reasons: onboarding cost, communication burden (with the formula), and management burden. Next, read "Cognitive Capacity of the Team". This connects team size to cognitive load and Dunbar's numbers, concepts relevant to your work in social research. Then, read the section on "Tuckman's Model", which explains how adding members can cause a team to regress to earlier, less productive stages of development. Finally, read the section "How Organizational Network Analysis (ONA) Explains Brooks' Law". This frames the problem in terms of network metrics like centrality and cohesion, which may resonate with your statistical training.

By involving more people in the relationship issue, the original couple inadvertently makes the "project" of finding resolution more complex and drawn-out. The solution becomes a problem in itself.


Conclusion

Brooks' Law teaches us a critical lesson in humility about managing complex systems. Our instinct to solve problems by adding resources often ignores the invisible, non-linear costs of coordination and integration. Whether in the tangible world of stitches and fabric or the intangible world of emotions and relationships, more is not always better.

Key Takeaways:

  • Brooks' Law: Adding people to a late, complex project often makes it later due to communication overhead, onboarding costs, and the limited divisibility of tasks.
  • Communication Overhead Grows Quadratically: The number of communication channels, and thus the potential for miscommunication and coordination effort, explodes as team size increases.
  • In Lingerie Production: Adding seamstresses to a late order can reduce net productivity as experienced members are diverted to training and management, and sequential tasks create bottlenecks.
  • In Relationship Dynamics: Involving more people to resolve a conflict can delay resolution by burying the core issue under an exponentially growing burden of communication and coordination, while also resetting established group dynamics.

In the previous lessons, we've seen that projects fail (Murphy), run late (Hofstadter), and that our knee-jerk reaction to lateness can make things worse (Brooks). So, what can we do? Our next lesson explores a more constructive path forward with Papert's Principle, which suggests that the biggest breakthroughs come not from acquiring new skills or resources, but from finding new ways to organize what we already know.