Breaking Down Silos: A Leader's Guide to Cross-Functional Collaboration

Short answer: Breaking down silos means changing what each function is accountable for so the whole company wins, not just each department. Silos are not caused by bad people who refuse to collaborate. They are caused by smart people rationally optimising the local scorecard they are measured and rewarded on. Leaders break them down by setting a shared goal, building metrics every function holds in common, and making cross-functional trade-offs visible, not by ordering people to "communicate more."

Key takeaways

What "breaking down silos" actually means

A silo is a function that has become a closed system. It has its own goals, its own budget, its own tools, its own definition of a good quarter. Information goes in, decisions come out, and the rest of the organisation sees only the surface. Breaking down silos is the work of reconnecting those closed systems so that decisions made inside one function account for their effect on the others and on the whole.

Note what this is not. It is not getting departments to like each other more. Two functions can be on excellent personal terms and still make decisions that quietly sabotage each other, because liking someone does not change what you are paid to deliver. Cross-functional collaboration is a structural outcome, not a mood. You get it by changing accountability, not by improving the catering at the offsite.

Why silos form (the part most leaders skip)

Organisations are split into functions for a good reason: specialisation is efficient. Sales should be expert at selling, operations at delivery, finance at capital. So you give each function its own objectives and a metric that captures whether it is doing its job. This is sensible, and it is exactly where the silo is born.

Once a function has its own metric, the people inside it do the rational thing: they optimise that metric. Add separate budgets they have to defend, separate reporting lines they answer to, and separate tools that do not talk to each other, and you have built a machine that manufactures silos as a byproduct of doing everything else correctly. The people are not the problem. The wiring is.

This matters because most silo-busting initiatives target the people. They run a workshop on "collaboration," put up a values poster, and ask everyone to be more open. Then everyone goes back to a desk where they are still measured, paid, and promoted on the local number. Nothing changes, and leadership concludes the team has a culture problem. It does not. It has an incentive problem, and incentives beat intentions every single time.

Local optimisation vs global optimisation

Here is the engine underneath every silo. Local optimisation is each function maximising its own metric. Global optimisation is the whole organisation maximising the outcome that actually matters: profit, customer outcome, mission. The brutal fact, well known in systems thinking and operations research, is that the sum of locally optimal decisions is almost never globally optimal.

An example. Sales is measured on bookings, so it closes every deal it can, including heavily customised ones. Operations is measured on utilisation and on-time delivery, so those custom deals wreck its schedule and it pushes back. Finance is measured on margin, so it kills the discounting that would have made the custom deals viable. Each function is hitting its own target. Each is behaving correctly by its own scorecard. And the company as a whole delivers late, at thin margin, to an unhappy customer. Nobody did anything wrong locally. The whole still lost.

That is the signature of a silo: every department can show a green dashboard while the company underperforms. The cost is real but invisible, because it lives in the gaps between functions, and no single scorecard measures the gap. This is why you cannot fix silos from inside a function. The information you need to see the problem only exists at the level above the silos. Breaking them down is structurally a leadership job.

Why each function optimising its own scorecard hurts the whole

When every function optimises locally, three things happen, and all three are expensive.

• Decisions get pushed onto the function with the weakest voice. Trade-offs do not disappear, they relocate. Whoever has the least power in the room absorbs the cost, whether or not that is where the cost should sit.
• Hoarding becomes rational. If sharing a resource, a forecast, or a heads-up helps another function hit its number but not yours, the locally smart move is to sit on it. Multiply that across the org and information flow seizes up.
• The handoffs rot. The places where one function's output becomes another's input are nobody's metric, so nobody owns them. Quality, speed, and trust all leak out at exactly these seams.

The deeper trap is that the skills that earned someone their leadership seat are usually the skills of winning locally. You got promoted to run operations by being relentless about operational excellence. Now that exact instinct, optimise my function, is the one quietly sinking the company when it goes unchecked. The behaviour is not malicious. It is a competence pointed at the wrong level.

How leaders break down silos

Breaking silos is a sequence, and the order matters. Change incentives first, then behaviour follows. Do it the other way and you get a nice afternoon that evaporates.

1. Set one shared goal the whole leadership team owns. Not five functional goals stapled together. One outcome that no single function can deliver alone and all of them are accountable for. If a department head can hit their personal targets while the shared goal fails, you do not have a shared goal.
2. Build at least one common metric. Give every function a number they share, so a win for one cannot be a loss for another without it showing up on both scorecards. A shared metric is the cheapest silo-breaker there is, because it changes the daily maths of every decision.
3. Make interdependence visible. Map where each function's decisions land on the others. People hoard and dump costs because the downstream effect is invisible to them. Put the dependency on a wall and a lot of bad behaviour becomes socially impossible.
4. Model the trade-off in public. When you, the leader, openly accept a hit to one function to win for the whole, you license everyone below to do the same. If leadership protects its own turf, every layer beneath will too. Silos are fractal. They copy whatever the top does.
5. Reward the global win, visibly. Promote and praise the manager who gave up a local point to win the company a goal. One public example of that is worth a hundred posters about teamwork.

Incentives and shared goals: the actual lever

If you take one thing from this guide, take this: you cannot ask people to collaborate against their own incentives and expect it to hold. Goodwill is real but it is a small budget, and it runs out the moment the quarter gets tight. The durable fix is to align the incentives so collaboration is the locally smart move, not the noble sacrifice.

Concretely, that means auditing what each function is actually measured and paid on, finding where those metrics push against each other, and either adding a shared metric on top or rebalancing the local ones. It is unglamorous work and it is the work. A leadership team that does this and skips the workshop will beat a leadership team that does the workshop and skips this, every time.

Why silos only become visible under real interdependence

Here is the practical problem with everything above: in a meeting, every leader agrees that silos are bad and collaboration is good. Of course they do. Silo behaviour is not something people choose on purpose and announce. It is something they do automatically, under pressure, when their own number is on the line. You cannot see it in a discussion, because a discussion has no stakes. It only shows up when leaders are put under genuine interdependence, where one person's local win is visibly another's loss, and they have to decide in real time.

This is the core idea behind Put The Player First, the framework we use to design these experiences. You do not lecture people about local versus global optimisation. You build a situation where they live it, feel the cost of optimising their own corner, and watch the whole lose while every individual scoreboard looks fine. Then the debrief connects what just happened in the room to what happens at their actual desks. Insight you arrive at by losing is the kind that survives contact with Monday.

Frequently asked questions

Basics

What does breaking down silos mean?
It means removing the structural and incentive barriers that stop departments from sharing information and coordinating decisions, so the whole company wins rather than each department separately. A silo is a function optimising its own scorecard because that is what it is measured on. You break it down by changing accountability, not attitude.

Why do organisational silos form?
Because organisations split into functions, give each its own goals and metrics, and people rationally optimise the goal they are measured on. Separate budgets, reporting lines, and tools turn each function into a closed system with its own definition of winning. Silos are a predictable byproduct of structure, not a character flaw.

The mechanics

What is the difference between local and global optimisation?
Local optimisation is each function maximising its own metric. Global optimisation is the whole organisation maximising the outcome that matters. The trap: the sum of locally optimal decisions is almost never globally optimal. Every department can show green while the company misses, because the cost lives in the gaps no single scorecard measures.

Why does optimising each function hurt the whole?
Because trade-offs relocate to the weakest voice, hoarding information becomes the locally smart move, and the handoffs between functions become nobody's metric and quietly rot. The instinct to win locally is often the exact skill that earned the leader their seat, now pointed at the wrong level.

Fixing it

How do leaders break down silos?
Change incentives before behaviour. Set one shared goal the whole leadership team owns, build at least one metric every function shares, make cross-functional dependencies visible, model the trade-off in public, and reward the global win out loud. Workshops help only if they change what people are measured on back at their desks.

Can team building activities fix silos?
Rapport-building reduces friction but leaves the incentives untouched, so the effect fades. What shifts silo behaviour is a high-interdependence experience that forces leaders to feel the cost of local optimisation, followed by a real change to shared goals and metrics. Connection without changed incentives is just a friendlier silo.

Related reading

• Serious games for leadership development: the complete guide
• Ripple Effect: the local-vs-global optimisation simulation
• The Put The Player First framework

See Ripple Effect Talk to us about a session