Why Silos Emerge During Growth
- Amrita Mazumdar
- Jun 4
- 6 min read
Silos are not a failure of culture. They are a sign that an organisation's informal systems have been outrun by its own growth. The question that matters is not why did this happen — but what would it take to grow the connective tissue alongside the company itself?
Teams don't suddenly become silos. Something structural shifts first.
Picture this moment — and it will be recognisable if you've lived inside a growing organisation.
The sales team has just closed a significant deal. They're celebrating. Across the office — or across a few floors, if you've grown that far — the operations team has just received the same news and is quietly recalculating workloads, wondering who they're supposed to talk to, and whether anyone thought to ask if this was actually deliverable in the promised timeline.
Two teams. One event. Completely different realities.
Nobody planned it this way. Nobody decided that sales would stop thinking about delivery or that operations would stop understanding commercial pressure. It happened gradually, almost naturally, in the same months when the company was doing exactly what it was supposed to do — growing.
This is how silos actually form. Not through stubbornness. Not through politics. Through growth.

As organisations move through these stages, the causes of fragmentation are often misunderstood.
Why silos are usually misunderstood
The common reading of silos is behavioural. Teams are territorial. People are protecting their turf. Functions have become fiefdoms. The prescription that follows is usually cultural — better values, more collaboration workshops, a push for "one team" thinking.
Sometimes that's part of the story. But it is rarely the whole story — and treating it as the whole story means organisations keep trying to fix an attitude problem that is actually a structural one.
Silos are, in most cases, a rational response to increasing complexity. As organisations grow, different teams begin operating inside genuinely different realities. They face different pressures, different timelines, different definitions of what success looks like on a Tuesday.
When people optimise for their own reality — which is mostly what organisations ask them to do — the result, over time, is fragmentation. Not because they stopped caring about the whole. Because the whole became too large for any one of them to see.
The problem, therefore, isn't the people. The problem is that the organisation outgrew the informal systems that once held everyone together.

How growth changes the way context travels
Early-stage organisations run on shared visibility. Everyone is close enough to the work — and to each other — that context moves without effort. The founder's instincts are everyone's instincts. The company's priorities are visible to anyone who shows up. When the sales pipeline slips, the entire team feels it. When a key customer has a problem, the information moves through the room like a current.
This isn't a communication strategy. It's proximity. And it works remarkably well — until it doesn't.
Beyond a certain point — somewhere in the range of thirty to sixty people, though the number matters less than the dynamic — the organisation becomes too complex for shared visibility to do its work. Organisations that remain relatively small but grow increasingly specialised often arrive at the same place by a different route.
There are now too many conversations, too many functions, too many decisions happening simultaneously for any one person to be in all of them. The founder, who once served as the living connection between everything, finds themselves caught — wanting to step back, but unable to, because the organisation has not yet built anything to replace that role. The informal moments that once resolved issues quickly start to thin out.
Context, which once moved freely, now has to travel. And travel is slow. And lossy.
What reaches the sales about a product constraint is not the same thing the product team said. What reaches operations about a commercial commitment is not the same thing that was actually agreed. The gap between what was meant and what was received silently widens — and because nobody deliberately widened it, nobody thinks to fix it.
This is alignment drift. It doesn't announce itself. It accumulates.

The hidden role of translation inside organisations
What fills the gap, in organisations that manage growth well, is translation.
Not communication in the broadcast sense — more emails, more updates, more town halls. But the actual work of converting context across functions: understanding what the finance team means when they say exposure, understanding what the operations team hears when they receive the same word, and finding the formulation that lets both groups act on the same reality.
We've written elsewhere about organisational translators — the people who do this work quietly, without being asked, without making it about themselves. During early-stage growth, the founder is often the primary translator. They hold the full picture and carry context from one conversation into the next. Every team benefits from their fluency in the different dialects the organisation runs on.
As the organisation grows, that single point of translation becomes a bottleneck. There is too much to translate, and only one person who can see everything. Decisions slow. Communication increases in volume but decreases in clarity. The founder becomes, paradoxically, both more important and less effective — needed everywhere, genuinely available nowhere.
This is when silos begin to calcify. Not because translation stopped mattering, but because the organisation never built the capacity to do it at scale. It relied on informal integration — a person, a presence, a shared room — and the informal system quietly failed to grow with everything else.
What organisations often begin experiencing
The symptoms are recognisable. Meetings where two teams agree on a decision and leave with different understandings of what was decided. Cross-functional projects where handoffs feel like throwing things over a wall. Escalations that reach the founder not because they need a decision, but because nobody else has enough shared context to resolve the tension.
Underneath all of it is a quieter reality: teams are not resisting collaboration. They are operating inside different operational pressures, and nobody has built the structures that would let them share a common view.
The sales team is not wrong to focus on the deal. Operations is not wrong to focus on delivery. Neither is finance. Each function is doing what the organisation asked it to do. The problem is that nobody is doing — formally, deliberately, at scale — the work of stitching those realities together into one coherent whole.
Execution friction rises. Decisions get stuck at the points where functions meet, because those points lack shared language and shared context. The organisation starts spending more energy on internal coordination than it should — not because the people are inefficient, but because the architecture of how context moves has not kept pace with the architecture of how the work is done.
What helps organisations remain connected without over-controlling everything
The honest answer is that there is no light version of this. Organisations that navigate growth without fragmenting tend to do something deliberately unglamorous: they build the connective tissue.
Not more reporting. Not more oversight. But actual structures that allow context to move horizontally — across functions, across levels — without requiring the founder to be in the room.
This sometimes looks like cross-functional conversations designed to maintain shared situational awareness. It looks like mid-level managers who are explicitly valued for their ability to translate between functions, not just manage within them. It looks like clarity about how decisions get made at the points where functions meet — not to bureaucratise the process, but to reduce the friction that currently turns every handoff into a negotiation.
It also looks like founders who accept that the informal integration they once provided personally has to become systemic. That the company's coherence can no longer live inside one person's head — and that designing for coherence at scale is not a loss of something. It is the next form of the thing.

A closing observation
Silos are not a failure of culture. They are, in most cases, a sign that an organisation's informal systems have been outrun by its own growth. The company became more complex than the structures holding it together.
That is not a criticism. It is almost inevitable.
The question that matters — the one worth sitting with — is not why did this happen but what would it take to grow the connective tissue alongside the company itself?
Because the teams are not the problem. The distance between their realities is.
And distance, unlike attitude, can be designed for.
Related reading: Organisational Translators · Why Scaling Feels Lonely · Decision Bottlenecks · Why Scaling Becomes Complex




Comments