Lesson 5 · Organization
Team size & communication
People add capacity in a line and coordination in a curve.
Every person added to a team adds a communication path to everyone already on it. A team of n has n(n − 1) ÷ 2 possible pairs: five people have 10, ten people have 45. Coordination cost grows roughly with the square of team size while capacity grows in a straight line.
That is the mechanism behind Brooks's law: adding people to a late software project makes it later. New people need ramp-up time from the very people who are busiest, and the work has to be re-partitioned. Adding people helps most when the work divides cleanly and the deadline is far away.
Span of control — direct reports per manager — has the same tension. With too few you add layers and hover; with too many, one-on-ones, feedback and growth suffer. Once a team passes eight to ten people, splitting it along a clean boundary usually beats growing it. And by Conway's law, systems mirror the communication structure of the organization that builds them, so team boundaries are architecture decisions.
Picture it
A six-person team (15 paths) is behind. Leadership offers four more engineers. At ten people there are 45 paths — three times the coordination for 67% more hands, and the newcomers need onboarding from the busiest people. The manager takes two engineers instead, gives them a separable piece (the data import tool), and cuts scope on the rest.
Key formulas & frameworks
- Communication paths
- n × (n − 1) ÷ 2
- Brooks's law
- Adding people to a late software project makes it later
- Span of control
- ≈ 5–8 direct reports for a hands-on engineering manager
- Conway's law
- System design mirrors the organization's communication structure
Try it — Communication paths
Communication paths
15
Paths per person
2.5
Paths follow n(n − 1) ÷ 2. Going from 6 people to 12 doubles the hands and more than quadruples the paths (15 → 66).
Practice
Score: 0 / 5
Up nextPerformance management
Next lesson