Adding people to a late project makes it later

The project is behind. The deadline is coming. You're stressed. So you do what feels obvious: you throw more people at it. Pull in the part-timer. Hire a contractor. Ask someone from another area to help out. It feels like progress. More hands, faster work.

Except it usually doesn't work that way. Sometimes it makes things worse.

The man who pulled the rope

More than a hundred years ago, a French agricultural engineer named Maximilien Ringelmann had people pull on a rope, both alone and in groups, and measured how hard they pulled.

You'd expect two people to pull twice as hard as one. They didn't. As the group got bigger, the average effort per person went down. Each additional person added less than the one before.

It became known as the Ringelmann effect. Later researchers found two causes behind it. Part of it is coordination: more people means more fumbling, more getting in each other's way. And part is motivation: when your individual effort gets lost in the crowd, you tend to ease off without realizing it. (If you read my post on team accountability, this is social loafing again.)

Brooks's Law

In 1975, a software manager named Fred Brooks wrote a book called The Mythical Man-Month, based on his experience managing a huge project at IBM. In it, he stated a rule that engineers still quote today: “Adding manpower to a late software project makes it later.”

His reasoning applies to far more than software:

1. New people need ramp-up time. Someone has to explain the project, the tools, and the history. Usually that someone is your most productive person, who now isn't doing the work.

2. Communication gets harder fast. Two people have one line of communication. Three have three. Five have ten. Every new person adds connections, and every connection is a chance for confusion.

3. Some work can't be split. Brooks's famous example: nine women can't make a baby in one month. Some tasks just take the time they take.

Why small business owners fall for this

When you're behind, adding people feels like taking action. It's visible. It shows you're serious. The real problem is often something else: an unclear goal, a bottleneck, a decision that hasn't been made, or too many projects running at once. Adding people doesn't fix any of those. It just adds more people to the confusion.

When a project is late, the answer is usually fewer moving parts, not more people.

What to do instead

1. Find the actual bottleneck. Before adding anyone, ask: What is this project waiting on? Very often, it's a decision, an approval, or an unclear requirement, and it's often waiting on you.

2. Cut scope before adding people. What's the minimum version that meets the deadline? Launch that, then improve it. Shrinking the work is almost always faster than growing the team.

3. Protect your best people's focus. If the project is behind, the most valuable thing you can do is clear distractions away from the people already doing the work.

4. If you must add help, give them something separate. New people are most useful on work that's well-defined and doesn't need constant coordination: a standalone task with clear instructions.

5. Add people early, not late. If you know a project will need more hands, bring them in at the start, when there's time to get them up to speed.

Smaller can be faster

There's a reason many successful companies love small teams. Everyone knows what everyone else is doing. Nobody's effort gets lost. Decisions happen fast. As a small business, that's your superpower. Don't give it up the moment a project slips.

Next time you're behind, resist the urge to add more people. Ask what's actually in the way. The answer is usually simpler, and cheaper, than a new hire.

If your projects keep running late and you can't figure out why, let's find the bottleneck together.

Sources: Ringelmann's rope-pulling studies (early 1900s) · Fred Brooks, The Mythical Man-Month (1975)