Uny AI

There is a persistent belief that software problems can be solved by adding people. Behind schedule? Hire more engineers. Big feature? Assign a bigger team. It feels intuitive, and it is one of the most reliably wrong intuitions in the entire industry. Beyond a surprisingly small number, adding people makes teams slower, not faster.

The math of communication overhead

The reason is communication overhead, and the math is unforgiving. Two people have one line of communication between them. Five people have ten. Ten people have forty-five. Every person you add creates connections to everyone already there, and each connection needs syncing, aligning, and updating.

Team size	Communication lines	Coordination load
2	1	Trivial
5	10	Manageable
10	45	Heavy
20	190	Overwhelming

Adding manpower to a late software project makes it later.

– Brooks’s Law

Small teams also share context effortlessly. When three people build something, each one holds the whole thing in their head. There is no need for elaborate handoff documents or status meetings, because everyone already knows why every decision was made.

What clear ownership looks like

Accountability sharpens in a small team. When something breaks and there are three of you, it is obvious whose area it touched and who will fix it. The traits that make small teams effective are worth naming explicitly:

• Shared context – everyone holds the whole system in mind
• Clear ownership – there is nowhere for responsibility to hide
• Low coordination cost – fewer lines to keep in sync
• Fast decisions – alignment happens in conversation, not documents

You can even model the coordination cost in a couple of lines of code. The point is not the formula itself but how fast the number climbs:

function commLines(n) {
  return (n * (n - 1)) / 2;
}

commLines(3);  // 3
commLines(10); // 45
commLines(20); // 190

How big organizations actually scale

This does not mean big organizations cannot build big things. It means they build them as a network of small teams, each owning a clear piece, rather than as one giant team owning a blur. The organizations that scale well resist the urge to grow individual teams and instead multiply small ones with clear boundaries.

The lesson for anyone starting a project is counterintuitive but freeing: you probably need fewer people than you think. A small, focused, well-aligned team will out-ship a large, coordinating one more often than not. When you feel the urge to add someone, first ask whether the problem is really a shortage of hands, or a shortage of clarity.