Brooks’s Law, Feat. Felipe Engineer

The Brooks’s Law Problem: Why Adding More People and Overtime to Late Projects Makes Them Later

Your project is slipping. The critical path is extending. The owner is asking questions. So you do what every superintendent does when they’re behind. You add more people. You authorize overtime. You push harder. You tell yourself that more hands and more hours equal more speed. And then you watch the project duration extend instead of shrink. You’ve just violated Brooks’s Law. And now you’re paying the price.

Brooks’s Law comes from software development. Fred Brooks at IBM studied thousands of projects and found something that contradicted everything project managers believed. When projects were deemed behind schedule, adding more people or spending overtime didn’t make them finish earlier. The data was clear. More people late in the project increases duration. More overtime beyond two weeks kills productivity. The go-to project management reaction, throw resources at the problem, was exactly wrong. And construction follows the same pattern.

The projects that recover successfully aren’t led by superintendents who add more people. They’re led by people who understand that communication channels multiply exponentially as crew size increases. Who recognize that context switching destroys productivity every time someone gets interrupted. Who know that overtime beyond nine weeks drops capacity from one hundred percent to sixty percent or lower. Who’ve learned that the answer to being behind is stabilizing the project so you can optimize it, not throwing manpower and materials at problems hoping speed increases.

The Problem Every Superintendent Creates

Walk onto any project that’s behind schedule and you’ll find the same pattern. Leadership panicked. They added crews. They authorized overtime. They pushed harder. And the project got worse instead of better. More coordination problems. More communication breakdowns. More rework. More delays. The solution they implemented was the exact thing extending their duration. They violated Brooks’s Law thinking they were solving their problem.

Most superintendents don’t recognize they’re making it worse. They think adding people is practical. Authoritative. Decisive leadership responding to crisis. They frame throwing resources at problems as taking action instead of recognizing it as violation of production laws. They don’t see that more people means exponentially more communication channels, that more overtime means dramatically lower productivity, that the thing they’re doing to speed up is exactly what’s slowing down.

The pattern shows up everywhere in construction. The project falls behind, so leadership brings in another concrete crew, never analyzing how many communication channels that creates. The schedule slips, so they authorize sixty-hour weeks, never recognizing that sustained overtime drops productivity to sixty percent. The punch list grows, so they throw more people at it, never acknowledging that fixing defects after the fact takes four to twenty-five times longer than fixing them when noticed. The superintendent pushes harder instead of stabilizing smarter.

Think about what this creates. You’ve got ten people on your crew. That’s forty-five communication channels. Every time someone needs information, there are forty-five potential paths it could travel. Every time there’s a change, forty-five channels need updating. Every coordination meeting requires managing forty-five relationships. Now double the crew to twenty people. You don’t have ninety channels. You have one hundred ninety. The complexity doesn’t scale linearly. It explodes exponentially. And you wonder why coordination is breaking down.

Meanwhile, you’re authorizing overtime thinking more hours equals more production. Week one, maybe you see gains. Week two, productivity starts dropping. Week three, people are exhausted. By week nine, you’re operating at sixty percent capacity. That five-day task now takes eight-point-three days. Add in the variation created by tired crews making mistakes, communication breaking down, and coordination failing, and that five-day task is now taking ten days or more. You threw overtime at the problem and extended duration instead of shortening it.

The Failure Pattern Nobody Recognizes

This isn’t about never adding people or avoiding all overtime. This is about recognizing that Brooks’s Law governs how projects actually flow. That adding manpower late in a project increases duration. That sustained overtime kills productivity. That the complexity of communication grows exponentially, not linearly. That most “solutions” to being behind make the problem worse.

Construction culture sometimes treats adding resources as the only response to problems. The superintendent who sees red on the schedule and immediately authorizes more crews. The project manager who demands overtime when tasks slip. The leadership team that thinks throwing people and hours at problems demonstrates decisive action. These patterns look like strength, like taking control, like solving problems. And they’re dangerous because they violate production laws that can’t be broken without consequences.

So superintendents add crews thinking it increases capacity. They authorize overtime thinking it buys time. They push harder thinking effort equals results. They never recognize that communication channels are multiplying exponentially, that context switching is destroying productivity that overtime is killing capacity, that the thing they’re doing to recover is extending their duration. They don’t see that Brooks’s Law applies to construction just like it applies to software.

The story always goes the same way. Project falls behind. Leadership adds more people. Communication breaks down because now there are exponentially more channels. Coordination fails because nobody can track all the handoffs. Onboarding consumes existing crew productivity teaching new people the project. Context switching destroys focus as interruptions multiply. Overtime extends from two weeks to two months. Productivity drops from one hundred percent to sixty percent. The five-day task becomes ten days. The project duration extends. Leadership adds more people and more overtime thinking that’ll fix it. The problem compounds. And nobody connects the extended duration to their violation of Brooks’s Law.

Nobody teaches superintendents that communication channels follow the formula n times n-minus-one divided by two. That three people create three channels but ten people create forty-five channels and two hundred people create nineteen thousand nine hundred channels. That context switching costs twenty percent productivity every time someone gets interrupted. That multitasking temporarily decreases IQ. That sustained overtime beyond nine weeks kills capacity. That the answer to being behind isn’t throwing more resources at problems.

A Story From the Field About Communication Channels

Felipe Engineer was discussing Brooks’s Law with Jason. Someone had made a mean comment on LinkedIn, and Felipe, demonstrating the character he’s known for, called the person and spent two and a half hours on a Friday night mending bridges. That’s Felipe. Always building relationships instead of burning them. And that dedication to communication makes him the perfect person to explain why adding people destroys projects.

Here’s the math. Jason and Felipe talking creates one communication channel. Add one more person and you’ve got three people with three channels. Not a big jump. But add more people and watch what happens. Four people creates six channels. Five people creates ten channels. Eight people creates twenty-eight channels. Ten people creates forty-five channels. The formula is n times n-minus-one divided by two. And it grows exponentially, not linearly.

Think about a regular project site. Even a twenty-million-dollar job can easily have two hundred construction workers and management staff. That’s nineteen thousand nine hundred communication channels for just two hundred people on a single project. Every time information needs to move, there are nineteen thousand nine hundred potential paths. Every coordination meeting requires managing exponential complexity. Every change requires updating thousands of relationships. And superintendents wonder why communication breaks down when they add more crews.

The communication problem creates the context switching problem. You’re focused on a task. Operating at one hundred percent productivity. Then someone interrupts you. A text message. A question. A coordination issue. You stop. You address the interruption. Then you try to go back to your task. You lose twenty percent of your time just switching back. The longer the interruption, the worse it gets. Interrupt someone writing an email and watch how long it takes them to start typing again after you finish talking. The delay is real. The productivity loss is measurable.

The more you multitask, the slower you get. And multitasking temporarily decreases your IQ. Yet construction runs on interruptions. The foreman coordinating five trades. The superintendent managing ten foremen. The project manager juggling twenty issues simultaneously. Everyone’s multitasking. Everyone’s context switching. Everyone’s operating at reduced capacity. And then leadership wonders why adding more people makes things worse instead of better.

Here’s another pattern Brooks’s Law predicts. The end of projects is when duration extends most dramatically. Construction typically adds manpower at the end trying to finish. All that does is extend overall project duration. Look at the gap between substantial completion and the last worker leaving the site. It’s huge. Because crews are doing shoddy work just to get signed off, then having to come back and fix it properly. Rework takes four to twenty-five times longer than fixing defects when noticed. That punch list item that would have taken fifteen minutes to fix during construction now requires remobilization, coordination, and hours of work.

The answer isn’t adding more people to do more rework faster. The answer is Takt planning with smaller batch sizes, limiting work in process, finishing as you go, and quality at the source. If your project needs superintendent coaching, project support, or leadership development to stabilize systems instead of throwing resources at problems, Elevate Construction can help your field teams stabilize, schedule, and flow.

Why This Matters More Than Looking Busy

When you add people and overtime to late projects, you’re not recovering. You’re extending duration. Brooks’s Law isn’t a suggestion. It’s a production law that governs how projects actually flow. You can’t violate it and expect success any more than you can violate gravity and expect to fly.

Kingman’s formula proves Brooks’s Law mathematically. The cycle time of any process multiplied by capacity utilization multiplied by the effects of variation equals overall duration. Take electricians doing overhead in a three-thousand-square-foot area in five days. That’s only if they’re at one hundred percent capacity with no variation. Add overtime and capacity drops to sixty percent. Now that five-day task takes eight-point-three days. Add in variation from communication breakdowns, context switching, coordination failures, and exhausted crews making mistakes, and you’ve probably gone from eight-point-three to ten days or more. You threw overtime at a five-day task and turned it into a ten-day task.

Communication channels multiply the problem. You started with a crew that had established rhythms and clear handoffs. You added people thinking more hands equal more speed. But now coordination requires managing exponentially more communication channels. Information that flowed smoothly through established relationships now gets lost in the complexity. Handoffs that were clear become confused. The productivity you had drops as everyone spends time coordinating instead of producing.

Context switching destroys what’s left. Your existing crew was focused. Operating efficiently. Then you brought in new people who need onboarding. Teaching them the project pulls your productive crew away from work to transfer knowledge. Every interruption costs twenty percent productivity. Every context switch compounds the loss. The capacity you thought you were adding actually consumed the capacity you had.

Watch for These Signals Brooks’s Law Is Destroying Your Project

Your project is vulnerable when you see these patterns:

• Leadership response to being behind is immediately adding crews without analyzing communication channel multiplication
• Overtime extending beyond two weeks with no end date, showing that temporary measures have become permanent dysfunction
• Punch lists growing exponentially as crews do shoddy work just to get signed off then have to remobilize to fix it properly
• Coordination meetings consuming more time than production as exponentially multiplying communication channels overwhelm the team

The Framework: Stabilize Then Optimize Instead of Throwing Resources

The goal isn’t avoiding all overtime or never adding people. It’s understanding Brooks’s Law so you know when adding resources helps versus when it hurts. Recognizing that adding manpower late in projects extends duration. Building systems that don’t require heroic effort and violation of production laws to succeed.

Short-term overtime can create gains if kept under two weeks. Beyond that, productivity drops dramatically. By nine weeks, you’re operating at sixty percent capacity or lower. The task that should take five days now takes eight-point-three days or more when you factor in variation. The overtime you’re paying for is extending duration instead of shortening it. If you need overtime beyond two weeks, your problem isn’t hours—it’s systems.

Communication channels grow exponentially with crew size. Three people create three channels. Ten people create forty-five channels. Two hundred people create nineteen thousand nine hundred channels. Every time you add people, you’re not just adding hands, you’re adding exponential coordination complexity. Sometimes that’s necessary. But recognize the cost. Build systems to manage it. Don’t assume that doubling crew size doubles productivity. It doesn’t. It multiplies communication complexity and often reduces productivity.

Context switching costs twenty percent productivity every interruption. Multitasking decreases IQ temporarily. Focus enables flow. Interruptions destroy it. When you add people to late projects, you’re adding interruptions. Onboarding requires pulling productive people away from work. Coordination requires constant communication. The capacity you thought you were adding gets consumed by context switching before it produces anything.

Quality at the source prevents rework multiplication. Fixing defects when noticed takes minutes. Fixing them on punch lists takes four to twenty-five times longer because now you need remobilization, coordination, and reinstallation. Finish as you go. Do it right the first time. Build quality in instead of inspecting it in later. The time saved on rework exceeds any gains from rushing through shoddy work.

Stabilize before you optimize. When your project is behind, the answer isn’t throwing more people and more hours at it. The answer is stabilizing the systems so you can optimize flow. Smaller batch sizes. Limited work in process. Finishing as you go. Takt planning to create rhythm. Once systems are stable, then you can optimize. But optimization on unstable systems just creates more chaos.

The Practical Path Forward

Here’s how this works in practice. Your project is behind. You’re tempted to add crews and authorize overtime. You need to decide whether that helps or hurts.

First question: how long will the overtime last? If less than two weeks and you have a specific recovery plan, maybe it helps. If indefinite or longer than two weeks, you’re killing productivity instead of increasing it. By nine weeks you’ll be operating at sixty percent capacity. Find a different solution.

Second question: how many communication channels are you creating? Use the formula. Current crew size times current crew size minus one divided by two. That’s your current channels. Now calculate what happens when you add people. If you’re going from ten people (forty-five channels) to twenty people (one hundred ninety channels), you’re not doubling capacity, you’re quadrupling complexity. Build coordination systems before adding people or accept that productivity will drop.

Third question: what’s driving the problem? If you’re behind because systems are broken, adding people makes it worse. Stabilize first. Fix the workflow. Establish rhythm. Then optimize. Throwing resources at systemic problems just multiplies the dysfunction across more people.

Execute based on production laws instead of panic. Brooks’s Law says adding people to late projects makes them later. Kingman’s formula says capacity utilization and variation determine duration. Context switching costs twenty percent productivity per interruption. These aren’t suggestions. They’re laws. Build your recovery strategy around them or watch your recovery fail.

Why This Protects Projects and People

We’re not just building projects. We’re protecting jobs, families, and futures from the burnout that Brooks’s Law violations create. And whether we stabilize systems or throw resources at problems determines whether we build sustainable success or temporary chaos.

When you add overtime beyond two weeks, you’re not protecting jobs. You’re burning people out. Productivity drops to sixty percent. Quality suffers. Mistakes multiply. People go home exhausted instead of fulfilled. Their families suffer because they’re working sixty-hour weeks producing less than they would in forty hours with stable systems. The overtime you’re requiring is destroying the people you’re claiming to protect.

When you add people to late projects without managing communication complexity, you’re not increasing capacity. You’re creating chaos. Coordination breaks down. Information gets lost. Handoffs fail. Everyone spends more time in meetings trying to coordinate than actually producing. The people you added to help are consuming the productivity of the people you had.

Respect for people means building systems that don’t require heroic effort to succeed. It means recognizing that Brooks’s Law applies to construction just like it applies to software. It means stabilizing before optimizing instead of throwing resources at problems. It means protecting people from the burnout that sustained overtime creates and the chaos that exponential communication channels produce.

The Challenge in Front of You

You can keep violating Brooks’s Law. You can keep adding people to late projects thinking more hands equal more speed. You can keep authorizing overtime beyond two weeks thinking more hours equal more productivity. You can keep pushing harder instead of stabilizing smarter. You can watch your duration extend and wonder why the solution isn’t working.

Or you can follow production laws. You can recognize that communication channels grow exponentially. You can understand that context switching costs twenty percent productivity. You can acknowledge that sustained overtime kills capacity. You can stabilize systems before throwing resources at them. You can build recovery strategies that work with Brooks’s Law instead of against it.

The projects that recover successfully aren’t led by superintendents who add more people. They’re led by people who understand production laws. Who recognize that the answer to being behind is stabilizing systems, not throwing resources. Who know that Brooks’s Law applies to construction just like every other domain. Who’ve learned that fret not if you’re getting behind, there are absolutely things you can do, and the answer is not just throw more people at it.

Your project is behind. You’re tempted to add crews and authorize overtime. Before you do, calculate the communication channels. Check how long the overtime will last. Analyze what’s driving the problem. Follow Brooks’s Law instead of violating it.

Stabilize. Then optimize.

On we go.

Frequently Asked Questions

What exactly is Brooks’s Law and why does it matter for construction?

Brooks’s Law states that adding people to late projects makes them later. It comes from Fred Brooks studying thousands of IBM software projects and finding that the go-to response, throw more people and overtime at problems—actually extended duration instead of shortening it. Construction follows the same pattern. Communication channels grow exponentially as crew size increases. Context switching destroys productivity. Sustained overtime kills capacity. The formula for communication channels is n times n-minus-one divided by two, meaning ten people create forty-five channels but twenty people create one hundred ninety channels. You’re not doubling capacity when you double crew size, you’re quadrupling coordination complexity.

How long can I run overtime before productivity drops significantly?

Short-term overtime under two weeks can create gains. Beyond that, productivity drops dramatically. The absolute maximum before exponential decline is nine weeks, and by that point you’re operating at sixty percent capacity or lower. A five-day task now takes eight-point-three days when you factor in reduced capacity, and closer to ten days when you add variation from exhausted crews making mistakes. The overtime you’re paying for is extending duration instead of shortening it. If you need overtime beyond two weeks, your problem isn’t hours, it’s systems that need stabilizing.

Why does context switching cost so much productivity?

When you’re focused on a task at one hundred percent productivity and get interrupted, you lose twenty percent of your time just switching back to the task. Your brain has to rebuild the context it had before the interruption. The longer the interruption and the more complex the mental work, the worse the loss. Interrupt someone writing an email and watch the delay before they start typing again, that’s context switching cost made visible. Multitasking makes it worse and temporarily decreases IQ. Construction runs on interruptions, which means everyone’s operating at reduced capacity all the time. Adding more people multiplies interruptions and compounds the productivity loss.

What should I do instead of adding people when my project falls behind?

Stabilize before you optimize. Identify what’s driving the problem, is it broken workflows, poor coordination, quality issues, or systemic dysfunction? Fix the systems first. Implement Takt planning to create rhythm. Use smaller batch sizes and limit work in process. Finish as you go with quality at the source. Once systems are stable, then you can optimize flow. Throwing people at unstable systems just multiplies the dysfunction across more crew members. The answer to being behind is building systems that don’t require heroic effort to succeed, not authorizing overtime and adding crews hoping harder work produces better results.

How do I manage communication channels when I do need to add people?

Calculate what you’re creating first using n times n-minus-one divided by two. If you’re going from ten people (forty-five channels) to twenty people (one hundred ninety channels), build coordination systems before adding people or accept that productivity will drop. Use scrum team structures to break large groups into smaller coordinated units. Establish clear communication protocols. Create standard work for handoffs. Limit who needs to coordinate with whom. Recognize that you’re not just adding hands, you’re adding exponential complexity. Plan for it instead of hoping it won’t matter.