Why growth creates organizational complexity

Growth doesn't wear a company down through its size. It wears it down because it adds complexity faster than the organization learns to absorb it. That gap, not complexity itself, is what produces the delays, the misunderstandings, and the fatigue you start to see as a team grows.

This mechanism is worth understanding in its own right, because it explains a lot of the difficulties we wrongly blame on a lack of rigor or goodwill. The wider picture is laid out in Structuring your company to stay agile; this page zooms in on a narrower question: why growing produces complexity almost mechanically.

From proximity to distance

While a company is small, most of what holds it together comes down to proximity. People see each other, talk, adjust continuously. A priority is understood without being spelled out, a decision gets made by turning to the right person, a problem is solved before it is ever documented. This implicit coordination is fast and cheap, and it creates the misleading impression that the organization needs no structure at all to function.

But that fluidity rests on a condition that rarely gets named: everyone sees roughly the same thing at the same time. As headcount rises, that condition stops being true. Distance, in the organizational sense, sets in. It isn't a matter of geography but of field of view: no one sees the whole of the work anymore, and the coordination that used to happen through sheer presence now has to be organized.

Where complexity really comes from

Complexity doesn't come first from the number of people, but from the number of relationships between them. When you add team members, what you mainly add are interfaces: points where one person's work depends on another's, where information has to pass, where a decision has to be coordinated. These interfaces grow far faster than headcount, and they are what carries the real cost of coordination. The computer scientist Frederick Brooks formalized this back in 1975 in The Mythical Man-Month: the number of possible links within a group follows the formula n(n-1)/2. A team of 10 already has 45 potential links, against 435 at 30 people and 1,225 at 50. Between 10 and 50, headcount is multiplied by five, but the number of links by more than twenty-five.

On top of this comes specialization. As a company grows, roles narrow, areas of expertise diverge, functions split apart. This specialization is healthy, because it makes everyone more competent in their own domain. But it multiplies dependencies: what one person used to do alone becomes a chain of contributions that have to fit together. The longer the chain, the more each link has to be explicit for the whole to hold.

The hidden cost: coordination, information, decisions

Organizational complexity is paid first in coordination. What used to be settled in a word now takes a sync, an alignment, sometimes a meeting. The real work doesn't change that much; it's the work of articulating the work that swells.

It is also paid in the flow of information. In a small team, information spreads on its own, through contact. In a larger organization it has to be relayed, and every relay is an opportunity for loss, distortion, or delay. A decision made at the top no longer reaches the ground on its own, and a signal from the ground no longer travels back up by itself.

And it is paid, finally, in decisions. When responsibilities don't keep pace with complexity, trade-offs flow up to a small number of people, often the founder. This single point of passage creates a sense of control, but it slows everything down and concentrates fragility in the wrong place.

Why the informal way doesn't scale

A common mistake is to believe that what made the early days work, the responsiveness, the versatility, the absence of process, should be preserved as-is for as long as possible. It's understandable, because those qualities have real value. But the informal way of working isn't a stable property of the company. It is a mode of coordination that works within a certain size range and stops working beyond it. The anthropologist Robin Dunbar popularized the idea of a cognitive ceiling on the number of stable relationships a person can maintain, often estimated at around 150. Well before approaching such a threshold, coordinating by word of mouth shows its limits, and the organization has to make up for what each person's memory and attention can no longer hold.

The fuzziness that was negligible when everyone could see everyone else's work becomes costly once that visibility disappears. The very absence of rules that made a team of ten nimble produces, at forty, duplication, oversights, and tension. It isn't that the informal way went wrong; it's that the context changed and no longer supports it.

The barriers to growth

Verne Harnish describes three classic barriers that scaling companies run into: leadership, systems, and market dynamics. Leadership, because founders have to learn to delegate and to grow other decision-makers rather than absorbing everything themselves. Systems, because the processes and tools built for a small outfit no longer hold as volume rises. Market, because external complexity (customers, competition, expectations) adds to the internal kind.

These three barriers share one thing: you don't clear them with more effort, but with a change in how you operate. Working harder inside a system that has become too implicit only pushes back the moment it gives way. It is the very nature of coordination that has to evolve.

The implication: making explicit what was implicit

Understanding where complexity comes from changes how you respond to it. The aim is not to eliminate it, which is impossible, nor to endure it, which is costly, but to make it absorbable. That comes down to something simple to state and demanding to do: progressively making explicit what used to hold together through proximity. The responsibilities, priorities, decisions, and rhythms that were once understood without being said now have to be set out clearly.

This shift from implicit to explicit is in no way bureaucratic in the bad sense of the word. It isn't about adding weight, but about giving the organization back the legibility that proximity once offered for free and no longer provides. That is exactly the point where complexity stops being a threat and becomes a manageable stage.

Complexity is never seen directly; it shows up through signals you have to learn to read before they turn into blockages.

And the first lever for absorbing this complexity is almost always the same: restoring clarity where fuzziness has crept in, starting with responsibilities.