Organisational silos

Someone in your organisation has said it in the last month. Probably in a meeting. Probably with a sigh.

"We're working in silos."

It's one of those phrases that lands with instant recognition. Everyone nods. Everyone agrees it's a problem. And then, almost without exception, someone suggests a fix: more cross-functional meetings, a collaboration platform, an away day, a restructure. The silo gets treated as the thing that's broken, and effort goes into breaking it down.

But here's the curious part. Most organisations have tried some version of this before. They've restructured. They've launched collaboration initiatives. They've invested in shared platforms. And the silos come back - sometimes in the same places, sometimes in new ones.

That pattern is worth paying attention to. Because if silos keep forming despite everyone's best efforts to dismantle them, maybe the silo isn't the problem. Maybe it's a symptom. And symptoms, if you're willing to listen to them, tend to be remarkably informative about what's happening underneath.

Why 'breaking down silos' rarely works

There's no shortage of energy directed at silos. Forrester Research found that 54% of organisations rank departmental silos as the primary obstacle to improving customer experience - ahead of budget constraints and legacy technology. The Boston Consulting Group estimated that in siloed organisations, up to 15% of total workforce capacity gets consumed by redundant activities that exist solely because information doesn't flow across boundaries.

These are significant numbers. And yet, despite widespread awareness that silos are costly, they persist. Restructures move the lines on the org chart, but the behaviour reappears. Collaboration tools get adopted, then used within teams rather than between them. Cross-functional working groups meet for a while, then quietly fade.

The reason is straightforward, if uncomfortable: most silo-busting efforts target the visible symptom without addressing what's producing it. They're the organisational equivalent of treating a fever by removing the thermometer. The reading changes, but nothing underneath has shifted.

It's worth asking a different question. Instead of "how do we break down silos?", what if we asked "what made silos the rational thing for people to do?"

What silos are protecting

This is where the picture gets more interesting. Silos don't form because people are territorial by nature, or because departments are inherently selfish. They form because somewhere in the system, the conditions are making it sensible - even necessary - for people to turn inward.

Think about what a silo provides. It offers clarity when the wider picture is confusing. It gives people a sense of control when the organisation feels unpredictable. It protects a team's identity when there's no compelling shared narrative. It preserves working rhythms when every cross-team interaction creates friction or delay.

None of that is irrational. In fact, it's entirely logical. People in complex organisations are constantly, unconsciously reading the conditions around them and adapting their behaviour accordingly. When those conditions reward internal focus - when goals are set by department, when recognition flows vertically, when information is currency, when cross-team collaboration creates more work than it saves - silos aren't a failure of collaboration. They're a successful adaptation to the environment.

This is why the language of "breaking down" silos often misses the point. You can't dismantle something that's serving a function without understanding what that function is. And in most cases, the function is protection - from confusion, from overload, from being asked to collaborate in a system that doesn't support collaboration.

The conditions that create silos

If silos are a response to conditions rather than a character trait, then the question becomes: which conditions?

The patterns tend to be consistent. Look for competing priorities where team-level goals pull against organisation-wide outcomes. Look for information architectures that make it easier to know what's happening in your own team than across the organisation. Look for recognition systems that celebrate departmental achievement but have no mechanism for acknowledging cross-boundary work.

Look, too, at the informal signals. How decisions get made. Whose voice carries weight. What happens when a cross-team initiative goes wrong versus when a departmental project fails. These signals are read quickly and accurately by everyone in the organisation, even when they're never discussed openly.

The Cultural Web - a diagnostic framework for understanding organisational culture - maps exactly these kinds of conditions: the stories people tell, the power structures, the control systems, the rituals and routines that shape daily behaviour. When you use it to examine silos, something shifts. The silo stops being a problem to solve and starts being a lens through which to see the wider system.

This is what we explored in why culture change efforts don't last. The same principle applies here. Treating symptoms - whether it's a disengaged workforce, a culture that resists change, or teams that won't collaborate - without understanding the conditions that produce them leads to interventions that don't stick. The pattern breaks for a while, then reasserts itself. Because the conditions haven't changed.

What changes when you read the signal

When leaders start treating silos as diagnostic information rather than misbehaviour, the conversation shifts in a genuinely useful direction.

Instead of asking "why won't these teams collaborate?", the question becomes "what's making collaboration feel risky or unrewarding?" Instead of launching another integration initiative, the work becomes understanding what the organisation's structures, incentives, narratives, and daily practices are collectively encouraging.

This isn't about accepting silos as inevitable. It's about recognising that sustainable change means working with the system, not against it. A silo that formed because team goals are misaligned doesn't need an away day - it needs aligned goals. A silo that formed because information is hoarded as currency doesn't need a collaboration platform - it needs a different relationship with transparency.

The shift is subtle but significant. It moves from trying to change people's behaviour directly (which rarely lasts) to changing the conditions that shape behaviour (which tends to be more durable). One organisation we worked with in the charity sector had spent years trying to improve cross-departmental collaboration through workshops and team-building events. The silos would soften temporarily, then re-form. When the work shifted to examining the conditions shaping their culture - how decisions were made, what got recognised, how resources were allocated - the patterns began to change in ways that sustained themselves. Not because people were told to collaborate, but because the environment started making collaboration the natural path. You can see how that work unfolded in their case study.

Listening to what the organisation is telling you

There's a broader principle here that goes well beyond silos. Every organisation is constantly producing signals about its health, its coherence, and the alignment between what it says it values and what it rewards in practice. Silos are one signal. High turnover is another. Resistance to change is another. The question is whether those signals get treated as problems to fix or as information to learn from.

The leaders who tend to make the deepest impact are the ones who develop the habit of reading these signals with curiosity rather than frustration. They don't hear "we're working in silos" and immediately reach for a structural fix. They pause. They ask what the silo is telling them about the system. And then they work on the conditions - patiently, systemically, often in ways that don't look like a silo-busting initiative at all.

Because the silo was never the problem. It was always the organisation trying to tell you something. The only question is whether you're listening.