Two departments spend a quarter solving the same problem, each unaware the other is doing it too. By the time anyone notices, both pieces of work are half finished, and neither team wants to be the one that stops.
This is not a story about lazy or difficult people. It is what organisational silos look like once they have settled into the way a company works. Nobody designs a silo on purpose. It builds up slowly, through structures and incentives that made sense on their own, until departments end up protecting their own patch rather than the outcome the whole business is meant to deliver.
Most conversations about silos jump straight to the fix, usually a reorganisation, a new collaboration tool or a cross-functional workshop. Few pause to ask why silos formed in the first place, yet that question matters. A Harvard Business Review article, citing a Harvard Business Review Analytic Services survey, reported that 67 percent of collaboration failures were attributed to silos rather than a lack of skill or effort. When an organisation treats only the visible symptoms without addressing the structures, incentives and behaviours underneath them, the same patterns are likely to reappear.
That is why silo-breaking sits so close to the wider question of how an organisation is built. It is one of the recurring problems addressed through organisational design work, because silos are rarely a people problem in isolation. They are usually a structural one wearing a people problem's clothes.
What an Organisational Silo Actually Is
An organisational silo is a pattern of behaviour, not a line on an org chart. It describes what happens when information, decisions and goals stop moving across departments, even though the departments themselves are functioning perfectly well on their own.
This distinction matters because most companies already have departments, and departments are not the problem. Specialisation, clear ownership and focused teams are genuine strengths. A finance function needs its own expertise. A product team needs the freedom to make fast calls without consulting every other function first. The trouble starts at the edges, at the points where one team's work depends on another's, and that handoff quietly stops happening.
You can spot the difference easily enough. A well-run department with strong boundaries still shares information freely, escalates problems early, and treats another team's target as connected to its own. A siloed department does the opposite. It optimises for its own numbers, guards its own information, and treats requests from other functions as an interruption rather than part of the job.
Why Organisational Silos Form in the First Place
Silos form because the structure around people rewards local success more reliably than shared success, and people respond to incentives whether or not anyone intended them to. This is the part most silo-breaking initiatives skip, which is also why so many of them fail to hold.
Department-level targets. When a sales team is measured purely on revenue and a delivery team purely on cost, both are behaving rationally when they optimise for their own number, even if it damages the outcome the customer actually experiences. Nobody set out to create conflict. The targets did it for them.
Physical and hybrid distance. Teams that sit together, in person or on the same calls every day, build trust faster than teams that only interact occasionally. Remote and hybrid working has made this more common, not less, because it is easy to prioritise the people you see most and quietly deprioritise everyone else.
Leadership behaviour. A silo mentality at the top travels downward fast. If a leader speaks about another department with suspicion or competitiveness, their team absorbs that attitude within weeks. People rarely question the tone their manager sets, they simply repeat it.
Natural in-group identity. People who share a discipline, a set of tools and a common language naturally form a tighter bond with each other than with departments that speak a different professional language. This is not dysfunction. It is a normal human tendency that becomes a problem only when it hardens into an us-versus-them mindset.
Success itself. This is the one most leaders miss. A high-performing team has the least reason to open its walls, because collaborating with a slower or less capable department can feel like a downgrade. The best teams are often the most siloed, not the worst ones, simply because they have less obvious incentive to change.
None of these causes require anyone to be uncooperative by nature. They are the predictable result of specialisation, growth and reasonable-looking incentives, left unmanaged for long enough.
The Real Cost of Working in Silos
Silos cost an organisation speed, quality and trust, usually all three at once, and the damage tends to be invisible until it shows up somewhere expensive. Nobody logs a "silo incident." What gets logged is a missed deadline, a duplicated project, or a customer who received two different answers from two different teams.
The first cost is duplicated work. Two functions solve the same problem in parallel because neither had visibility into what the other was doing. This is rarely discovered until both pieces of work collide, at which point someone has to decide which version survives, and the other becomes wasted effort.
The second cost is slower decisions. When information does not flow across departments, every cross-functional decision has to start from a lower base of shared understanding. What could be a five-minute conversation becomes a week of meetings simply to get everyone to the same starting point.
The third cost is inconsistent customer experience. When marketing, sales and product hold different versions of the truth, the customer is the one who notices the gap. They hear one story from a salesperson and a different one from the product they actually receive, and the mismatch erodes confidence in the whole organisation, not just the team that got it wrong.
The final cost is the hardest to reverse: trust between departments. Once one team has been burned by a silo, whether through a missed handoff or a decision made without consultation, they start protecting themselves the next time. That defensiveness looks exactly like a silo forming, except now it is being built deliberately rather than by accident. This is not a fringe problem either. The same HBR analysis that produced the 67 percent figure also points to a longstanding American Management Association survey, which found that 83 percent of executives openly recognise silos inside their own organisation, and 97 percent say those silos have a negative effect on the business. Most leaders are not in denial about silos. They simply have not been given a practical way to dismantle them.
Signs Your Organisation Is Running in Silos
You can usually tell an organisation is working in silos before anyone uses the word, because the same handful of patterns show up across unrelated teams. The pattern is more reliable than any single incident.
Meetings between departments feel more like negotiation than collaboration, with each side arriving to protect their position rather than solve the shared problem. Requests from other teams get treated as favours rather than part of the job, and get deprioritised whenever the requesting team's own workload builds up. Information that would help another department gets shared late, or only after it is specifically asked for. People describe colleagues in other functions using generalisations, "sales never think about delivery," "engineering never explains anything," rather than specifics.
Perhaps the clearest sign is what happens when something goes wrong between two departments. In a healthy organisation, the response is to fix the process that let the gap appear. In a siloed one, the response is to establish whose fault it was, which teaches everyone involved to protect themselves a little more carefully next time.
How to Break Down Organisational Silos
Breaking down silos means changing what teams are measured on and what they are required to achieve together, not simply asking them to collaborate more. Communication problems are often downstream of structural ones, which is why initiatives focused only on improving communication rarely create lasting change. McKinsey Global Institute estimated that improved communication and collaboration enabled by social technologies could increase the productivity of knowledge workers by 20 to 25 percent. Although the research focused specifically on technology-enabled collaboration, it illustrates the potential operational value of helping information and expertise move more effectively across organisational boundaries.
Start with a shared outcome that no single department can reach alone. This has to be specific: a number, a customer outcome, a delivery date that genuinely requires two or more functions to succeed together. When one team's win depends on another team's cooperation, the incentive to hoard information disappears on its own.
Redesign the metrics that currently reward local optimisation. If a support team is measured only on ticket closure time and a product team only on release velocity, both can hit their targets while the customer experience gets worse. Metrics that ignore the connection between teams will always outcompete good intentions.
Create structured points of overlap, not just open channels. A shared Slack space rarely changes behaviour on its own. A joint planning session, a rotating liaison role, or a regular cross-functional review where both teams are accountable for the same result does far more, because it forces contact rather than hoping for it.
Address leadership behaviour directly. If a senior leader still speaks about another function with suspicion, no framework will outweigh that signal. Leaders need to model the cross-functional respect they are asking their teams to show, and be willing to be corrected publicly when they slip.
Give people direct exposure to the teams they depend on. A short rotation, a shadowing arrangement, or simply sitting in on another team's planning meeting does more to break down assumptions than any amount of written communication, because it replaces a caricature of the other department with an actual working relationship.
Common Mistakes When Trying to Break Silos
Most attempts to break down silos fail for a small number of predictable reasons, usually because they address the visible symptom rather than the structural cause underneath it.
The most common mistake is treating a reorg as the fix. Moving boxes around an org chart can dissolve one silo and create two new ones almost immediately, because the underlying incentives and reporting relationships that produced the original silo often move with the people. Structure matters, but it is rarely the whole story.
A second mistake is running a one-off collaboration event and expecting it to hold. An away day can genuinely improve how two teams feel about each other for a few weeks. Without a structural reason to keep collaborating once people are back at their desks, the old patterns reassert themselves quickly.
A third mistake is buying a tool to solve a behavioural problem. Shared dashboards and unified platforms help once people are already motivated to use them together. They do very little on their own if the underlying incentives still reward departments for guarding their own information.
Finally, many organisations underestimate how much a strong, high-performing team resists integration precisely because it is strong. The instinct is to leave the best teams alone and focus energy on the struggling ones. That instinct is usually backwards, since the highest performing teams are often the ones with the most valuable knowledge to share and the least reason to share it voluntarily.
Keeping Departments Open Over Time
Silos do not stay broken on their own. They reform quietly whenever a shared goal ends, a leader changes, or growth adds new layers between teams that used to talk directly. Keeping departments open is an ongoing habit, not a project with a finish line.
The organisations that manage this well tend to check in on cross-functional relationships the same way they check in on performance, treating a strained handoff between two departments as seriously as a missed target. They also resist the temptation to declare victory after one successful collaboration and move on, because the conditions that produced the original silo are usually still present even after the symptom has cleared.
Silos are not a sign that people have stopped caring about the organisation as a whole. They are a sign that the structure around them has, for a while, made caring about their own patch the more sensible choice. Change what the structure rewards, and the walls tend to come down on their own, long before anyone needs to ask people to collaborate more.
Reading about it is one thing. Designing it is another.
If this one is live in your organisation right now, it’s probably worth a conversation rather than another article.