Why Hiring More People Can Slow Your Business Down

Short answer: When a team is behind, the instinct is to add people. But past a point, each new hire can make the team slower, not faster — because the cost of coordinating people grows faster than the people themselves. In a team of n people, the number of one-to-one communication links is n × (n − 1) ÷ 2. Go from 6 people to 12 and you don’t double the coordination — you multiply the connections from 15 to 66. That’s why “just throw more bodies at it” so often backfires, and why the smarter move is usually more capacity, not more headcount.

This is one of the most durable ideas in management, it’s mathematically exact, and almost no one applies it to running a small business. Here’s the counterintuitive math — and what to do with it.

The rare fact: adding people can make things slower

In 1975, computer scientist Frederick P. Brooks Jr. published The Mythical Man-Month and stated what’s now called Brooks’s Law: “Adding manpower to a late software project makes it later.” (The Mythical Man-Month, Wikipedia).

It sounds like a paradox. More hands should mean more done. Brooks’s point was that people aren’t interchangeable units of work, because two costs rise the moment you add someone:

1. Ramp-up. A new person isn’t productive on day one — and getting them there pulls your best existing people off their work to train them. You lose output before you gain any.
2. Communication overhead. Every new person has to stay in sync with everyone else. And that cost doesn’t grow in a straight line.

Brooks was writing about software teams, but the second cost is just arithmetic — it applies to any team that has to coordinate.

The math nobody runs: communication channels

The number of one-to-one communication links in a team of n people is n(n − 1) ÷ 2. Watch how fast it climbs:

Team size	Communication links
3 people	3
5 people	10
6 people	15
10 people	45
12 people	66
15 people	105
50 people	1,225

Double a team from 6 to 12 and the links you have to keep in sync go from 15 to 66 — more than a 4× jump in coordination for a 2× jump in people (corroborated by multiple summaries of Brooks’s work). Every one of those links is a chance for a dropped handoff, a duplicated effort, a “wait, who’s doing that?” This is why a five-person team can feel effortless and a fifteen-person team can feel like it’s constantly tripping over itself — the work didn’t get 3× harder, the coordination got 7× heavier.

Why this matters for a business, not just software

Swap “programmers” for “people you hire to fix a stretched back office” and the logic holds exactly. An overwhelmed founder’s reflex is to hire: a bookkeeper, then an office manager, then someone for payroll, then a marketing coordinator. Each hire is meant to relieve load. But each one also adds:

• A person to recruit, onboard, train, and manage
• A new set of communication links to every other person
• A fixed cost you carry whether this month is busy or slow
• One more thing the founder now has to supervise

So the founder who hired five people to “get time back” often has less time than before — because they’ve become the hub that all those new communication links route through. The team got bigger; the founder became the bottleneck. (It’s the same trap that makes profitable businesses run low on cash — the fix creates a cost that’s invisible until it hurts.)

The way out: capacity without the coordination tax

Brooks’s Law isn’t an argument against ever hiring. It’s an argument for being deliberate about when a new node in the network is worth its coordination cost. Three principles fall out of it:

• Add capability, not just headcount. One senior person who owns a whole function end-to-end adds far fewer communication links than three juniors who each own a slice and have to coordinate constantly.
• Bundle related work under one point of contact. If bookkeeping, tax, and financial reporting all route through one accountable team instead of three separate hires, you collapse a web of links into a single relationship.
• Buy outcomes, not seats. An outsourced function scales up and down without you onboarding, managing, or coordinating each person inside it. You get the output; you don’t inherit the internal communication tax.

This is the quiet advantage of an outsourced back office run as one team: your bookkeeping, tax, finance, HR, and operations sit behind a single accountable relationship, not five separate hires you personally have to keep in sync. The coordination happens on their side of the line, not yours. It’s also why a fractional COO often beats a stack of new managers — one senior operator building the system adds one link; five coordinators building nothing add fifteen.

The reframe

More people is not the same as more done. Every hire you add is also a coordination cost you pay forever, and that cost grows faster than the headcount does. Before the next “we just need another person” hire, ask the Brooks’s Law question: am I adding capacity, or am I adding links to a network I already can’t keep in sync?

Sometimes the answer really is “hire.” Often it’s “consolidate” — get the function done by one accountable team instead of assembling it person by person. If you want an honest read on which back-office work is worth a hire and which is worth handing off, book a discovery call or see plans and pricing.

---

DaxHive runs the back office — bookkeeping, tax (through licensed CPA/EA partners), and a fractional CFO & COO — for growing service businesses, so you add capacity without adding headcount. Educational only; not financial or tax advice.