Book 1:1 Discovery Call

+973 3541 1661 · coachrulahusseini@gmail.com

How to Break Down Silos Between Departments

To break down silos between departments, stop treating them as an attitude problem and fix what produces them: separate goals, separate scorecards and no shared place to make trade-offs. Give department heads one outcome they own together, map the handoffs where work stalls, agree who decides at each boundary, and change what gets recognised. Silos shrink when collaboration becomes the easier path, not just the virtuous one.

By Rula Husseini, ICF PCC · Reviewed 3 November 2026

Employees from different teams mingling and talking in a large open office space

Most leaders notice silos through their symptoms: duplicated work, emails copied to everyone for protection, monthly meetings where each department defends its own numbers. The instinct is to run a collaboration workshop or ask people to think as one team. That rarely lasts, because the people inside a silo are usually behaving sensibly given what they are measured on.

This guide is for the leader who can influence more than one department: a general manager, a director with peers to work alongside, or a head of function who is tired of fighting the same handoff every month.

Silos come from how departments are measured, not from who works in them

A department becomes a silo when its targets, budget and recognition all point inward. If sales is rewarded for volume and operations for cost, each will protect its own measure, and every handoff between them turns into a negotiation. Nobody needs to be difficult for this to happen.

So the first question to ask is not 'who is being uncooperative?' but 'what does each department gain by holding back?' Answer that honestly and the fix often becomes obvious. Systems thinking calls this looking at the structure beneath the events, and the glossary entry on systems thinking explains the idea in a few minutes.

A six-step method for breaking down silos between departments

  1. 01

    Name one shared outcome

    Pick a result neither department can deliver alone, such as order-to-delivery time or the customer onboarding experience. Put it on both scorecards, with both heads accountable. One shared outcome does more than ten shared values.

  2. 02

    Map the handoffs

    Walk one piece of work from start to finish across the departments. Note every point where it waits, gets reworked or needs escalation. A handful of handoffs usually cause most of the friction.

  3. 03

    Put the department heads in one room on a fixed rhythm

    A monthly cross-functional review of the shared outcome, chaired by the leader above both departments or rotated between the heads, gives trade-offs a place to be made openly instead of in escalation emails.

  4. 04

    Agree decision rights at the seams

    For each problem handoff, decide who decides, who must be consulted and who simply needs to know. Ambiguity at a boundary is exactly where silos protect themselves.

  5. 05

    Move people, not only information

    Short secondments, joint project teams and shadowing days build the personal relationships that make a phone call possible before an email war starts.

  6. 06

    Change what gets recognised

    Publicly credit the department that gave something up to help another hit the shared outcome. People watch what senior leaders celebrate far more closely than what they say in town halls.

Read the symptom to find the cause

Different silo symptoms point to different root causes. Use this table to pick a first move instead of applying the same remedy everywhere.

SymptomWhat usually sits underneathFirst move
Work is duplicated in two departmentsUnclear ownership, or low trust in the other team's outputAgree one owner and a quality standard both sides accept
Every handoff needs escalationDecision rights at the boundary are undefinedWrite a simple decision-rights grid for the three worst handoffs
Departments hoard dataInformation is treated as protection or leverageOpen the shared-outcome dashboard to both teams
Heads agree in meetings and nothing changesTargets still reward the old behaviourAdjust one scorecard measure before asking for new behaviour
Teams blame each other to senior leadersNo forum to settle tension directlyCreate a regular cross-department review with a clear agenda

Openers for the first conversation between department heads

The first conversation between two department heads sets the tone for everything after it. Keep it about the work and the customer rather than the history. These openers tend to lower defences:

  • 'Where does work from my team land badly on yours, and what does that cost you?'
  • 'What would you need from us to hit your number more easily?'
  • 'If a customer watched this handoff, what would they think of us?'
  • 'Which decisions between our teams keep going upwards that we could settle ourselves?'
  • 'What is one thing we could try for a month and then review together?'

Five mistakes that keep departments apart

  • Treating silos as a culture problem only. Away days build goodwill, but goodwill fades if scorecards still pull people in opposite directions.
  • Restructuring as the first answer. A new organisation chart moves the boundary; it does not remove it. Fix the handoffs before redrawing the boxes.
  • Asking junior staff to collaborate across a line their bosses still defend. Cooperation has to be visible at the top before it is credible lower down.
  • Measuring collaboration by the number of joint meetings. Count outcomes delivered across the boundary, not hours spent together.
  • Letting one head carry the shared goal alone. A shared outcome with a single owner quickly turns back into one department's problem.

Why silos can run deeper in Gulf organisations, and how to work with it

Respect for seniority is a real strength in many Gulf workplaces, but it can send cross-department issues upwards instead of sideways. A specialist may not feel it is their place to call a peer's manager, so a small issue climbs two levels before anyone resolves it. Saying clearly, from the top, that problems should be solved at the working level speeds this up considerably.

In family-owned groups, divisions are sometimes led by different family members or long-serving executives with their own loyalties. In multinationals, a local department may answer to a regional head in another country. Either way, the shared outcome needs a sponsor senior enough to hold every party to it. If you report into more than one line yourself, the guide to leading in a matrix organisation covers that side of the problem.

Example: sales and operations in a growing distribution business

Imagine a distribution company in Bahrain where sales keeps promising delivery dates that operations cannot meet. Every monthly meeting becomes a debate about whose fault the late orders were. The general manager has already tried a team-building day, and relations improved for about two weeks.

This time the general manager makes on-time delivery a shared measure for both heads, maps the order handoff, and finds that sales commits dates before checking stock. The two heads agree that any order above a set size gets a five-minute stock check before a date is promised. Within a quarter the arguments shift from blame to which orders to prioritise.

The scenario is hypothetical, but the sequence is a common one: shared outcome, mapped handoff, agreed decision rule, regular review.

When coaching helps department heads act as one team

Silos are often held in place by the relationships between the people at the top of each department: old disagreements, quiet competition, or a sense that conceding a point means losing face. Those are hard to raise in a normal management meeting because everyone is still performing for their own team.

Team coaching gives a leadership group a structured, confidential space to surface what is really in the way and agree how they will work together. Executive team alignment coaching is designed for this: helping department heads see the organisation as one system and make trade-offs together rather than through escalation.

About the author

Rula Husseini is an Executive Leadership & Mindset Coach (ICF PCC) based in Manama, Bahrain, with 26+ years in leadership, HR and talent development and 4,500+ coaching hours. She coaches executives, emerging leaders and teams in Arabic and English, in person and online.

Credentials and training →

Frequently asked questions

How long does it take to break down silos between departments?

Specific handoffs can improve within a quarter once decision rights and measures are fixed. The wider habit of thinking 'my department first' takes longer, often a year or more, because it depends on what leaders reward consistently over time.

Should I restructure to get rid of silos?

Usually not as a first step. Every structure creates boundaries, so a restructure tends to create new silos in new places. Fix shared goals, handoffs and forums first, and restructure only if the design itself is clearly the problem.

Can a middle manager break down silos without senior support?

You can improve the handoffs you personally touch by building relationships with your counterparts and agreeing simple working rules. Changing measures and recognition needs someone with authority over both departments, so bring them evidence of what the silo is costing.

Are departmental silos always a bad thing?

No. Specialist teams need focus and some protection from constant interruption. The problem is not the boundary itself but a boundary that work cannot cross without friction, delay or escalation.

Department heads pulling in different directions?

Book a free 30-minute discovery call to talk through what is keeping your teams apart.