What Stops Working When Your Team Doubles
There is a point in a company's growth where something the team relied on quietly stops working.
The company is still moving. People are showing up. Work is getting done. But something that felt effortless at 15 people requires more effort now. Coordination that happened informally has to be scheduled. Context that used to travel on its own has to be actively distributed. Relationships that formed naturally now have to be built deliberately.
Founders often describe this as growing pains. It is more useful to understand it as a structural shift.
THE INVISIBLE SYSTEM THAT HELD YOUR SMALL TEAM TOGETHER
Early teams do not succeed because of their processes. They succeed because of proximity.
When a company is small, people share context automatically. They overhear conversations, work in adjacent spaces, and develop an informal understanding of what everyone else is working on and why. Trust builds through repeated interaction. Misalignment corrects quickly because people have enough shared context to notice it.
None of this is designed. It is a byproduct of smallness.
At some point, the company grows past the size where proximity can do that work. There is a threshold, typically somewhere between 50 and 150 people, where the informal systems that held a small team together begin to strain. Not because people changed, but because the organization outgrew the conditions those systems depended on.
WHAT BREAKS FIRST WHEN THE HEADCOUNT DOUBLES
When a company crosses this threshold, a few things happen simultaneously.
The number of relationships increases faster than any one person can maintain. Context becomes unevenly distributed. Some people have it, others do not, and the gap is not always visible. Decisions made at the top reach different parts of the organization in different forms. Coordination that once required a conversation now requires a process.
These changes are structural. They happen regardless of how strong the culture is or how capable the team is.
What determines how well a company navigates this threshold is not whether the informal systems break down. They will. It is whether the organization builds something to replace them before the gap becomes a problem.
THE SYMPTOMS LEADERS MISTAKE FOR PROCESS FAILURES
When the informal systems have broken down but nothing has replaced them, the symptoms are recognizable.
Meetings produce agreement that does not survive execution. People leave the same conversation with different assumptions about what was decided. Work that should move cleanly requires more coordination than expected. Tension accumulates in relationships that did not used to feel difficult.
Leaders often respond by adding process. They introduce clearer frameworks, more explicit documentation, or additional oversight. Those things can help. But they address the surface without addressing what is underneath.
The underlying issue is relational capacity. The organization's ability to coordinate, build trust, and resolve tension as it scales. When that capacity is underdeveloped, no amount of process fully compensates.
WHY THE THRESHOLD CATCHES FOUNDERS OFF GUARD
The shift does not feel sudden. It builds gradually.
At 30 people, things still largely work the way they always did. At 50, there are signs of strain but they are easy to attribute to something else. A difficult quarter, a new hire who is still getting up to speed, a process that needs refinement. By 80 or 100 people, what was manageable friction has become a pattern.
Founders are often surprised because the company that worked so well at 20 people appears to be the same company at 60. The product is the same. The mission is the same. Most of the people are the same.
What changed is the invisible infrastructure underneath. The web of relationships and shared context that made the small company function. That infrastructure has a carrying capacity. When the company grows past it without replacing it, the organization starts to carry more weight than the underlying structure can hold.
WHAT ACTUALLY REPLACES PROXIMITY
The work at this threshold is not primarily structural. It is relational.
That means building trust deliberately rather than assuming it will form on its own. It means creating conditions for context to travel through the organization rather than assuming proximity will carry it. It means paying attention to how relationships are functioning across teams and levels, not just whether the org chart is correctly drawn.
This work is often invisible until it is absent. Organizations that do it well feel coherent even as they scale. Organizations that skip it find themselves with processes that should work but do not, and relationships that look functional but do not have the underlying capacity to sustain the work.
THE INFLECTION POINT EVERY SCALING COMPANY HITS
The threshold between a small team and a mid-sized organization is not a moment of failure. It is a predictable inflection point.
Every organization that scales past it faces the same transition. What they do with it varies. Some build relational capacity alongside headcount and carry their culture through the growth. Others add process and structure while the underlying relationships remain underdeveloped, and find themselves managing symptoms that keep returning.
The companies that navigate this threshold well tend to recognize it early, before the symptoms become entrenched, and treat the relational work as infrastructure rather than as a response to a crisis.
