You can spot a siloed organisation without opening a dashboard. The leadership team agrees the strategy in January, then by summer every function is busy, every roadmap looks sensible on its own, and delivery still feels stuck. Sales blames product, product blames marketing, operations says it was never asked, and the same dependencies keep slipping because nobody owns the whole chain.
That's why breaking down silos is rarely a communication fix. It's usually a work-design problem, a decision-rights problem, and an incentives problem dressed up as a culture problem. If remote and hybrid working changed how information moved across functions, as Harvard Business School's research suggests, then leaders need more than goodwill. They need an operating rhythm that forces alignment to survive contact with reality, not just a kickoff meeting that feels encouraging for a week. the gap between strategy and execution is where most silo stories begin.
Why Silos Quietly Break Even Good Strategies
A good strategy can still fail in a perfectly ordinary week. The executive team agrees three priorities, each function leaves with its own interpretation, and six months later everyone is still working hard, just not in the same direction. The problem isn't usually that people didn't hear the message. It's that the organisation rewarded them for protecting their own patch.
Local optimisation beats shared outcomes
PwC's global operations survey found that only 36% of companies prioritise a few cross-functional capabilities at company level, while 55% still let each function decide its own priorities, and 61% say faster cross-functional collaboration is needed to reach strategic goals (PwC survey). That pattern explains why so many leadership teams keep revisiting the same problem. The strategy is clear enough. The operating system isn't.
Leaders get misled by the language of collaboration. They assume they have a people issue, so they ask for more communication. But if each function is measured on its own output, people will do exactly what the system pays them to do. They'll optimise locally, defend their backlog, and treat cross-functional work as optional unless someone senior forces the issue.
Practical rule: if a department can win while the business loses, silos are built into the system.
Remote and hybrid work made the problem easier to see, not harder to explain. Harvard Business School's research found that many organisations became more siloed during 2020's emergency work-at-home measures, with employees “digitally splitting off into more isolated and well-defined communication networks” (HBS research). That matters because distributed work doesn't create silos on its own, it exposes the ones already sitting in the operating model.
The distinction is simple. A collaboration problem is when people don't talk enough. An operating model problem is when they talk, but priorities, measures, and decisions still pull them apart. Leaders who can tell the difference stop wasting time on generic culture fixes and start changing how work flows.
Diagnosing Silos Before You Try to Fix Them
Before anyone launches a reorg, buys another tool, or runs a morale-boosting offsite, they need a diagnosis. Not a survey with vague sentiment scores. A hard look at how decisions move, where work stalls, and who ends up carrying the informal load when the system gets messy.
A four-part diagnostic leaders can run fast
Start with meeting forensics. Look at the last few leadership and delivery forums and ask three blunt questions. What got decided? Who had authority to decide it? How often did cross-team items slip because the right person wasn't in the room or the room had no decision rights? If those meetings produce updates but no choices, the silo is probably sitting in your governance.
Next, audit the planning artefacts. Roadmaps, quarterly plans, portfolio sheets, whatever your organisation uses. Do they show dependencies plainly, or do they read like isolated function plans stitched together at the end? If dependencies are hidden, then the plan itself is encouraging teams to ignore one another until something breaks.
Then scan behaviour signals. Where do escalations pile up? Who keeps solving coordination issues informally? In most organisations, the same few people become the human glue because the structure never assigned the work properly. That's not a collaboration success. It's a sign the operating system is leaning on individuals to compensate for poor design.
Finally, review measurement. What does each function get rewarded for, and what gets ignored? A team that is praised for hitting its own targets will protect them. That's rational. It also means silos are being reinforced every performance cycle.
A simple scoring approach helps here. Rate each of the four areas, meeting forensics, planning artefacts, behaviour signals, and measurement, on a low, medium, or high silo risk basis. The point isn't perfect precision. It's creating a baseline you can compare against later, so progress doesn't depend on memory or optimism. For a structured way to pressure-test that baseline, the framework in performance diagnostics fits neatly beside this method.
What the signals usually point to
- Weak decision clarity usually points to decision-rights confusion.
- Hidden dependencies usually point to structure problems.
- Informal heroics usually point to bad work design.
- Function-only rewards usually point to incentives that are working exactly as designed.
If the same issue appears in all four places, don't call it a communication gap. Call it an operating problem and treat it that way.
Why Most Silo-Busting Initiatives Fail
Most leaders have already tried something. They've shuffled boxes on an org chart, rolled out a collaboration platform, or convened a townhall to reset behaviour. The energy rises, people nod, and then the backlog returns with the old habits intact. The failure isn't that these moves are useless. It's that they rarely change the conditions that created the silo in the first place.
The usual fixes look active but leave the system alone
A reorg changes reporting lines, but if decision rights stay vague and incentives stay local, people learn the new map and keep behaving the same way. Teams still optimise for what they can control. They just do it under new labels.
Tools can make this worse. Add a chat layer on top of siloed systems of record and you don't get alignment, you get more noise. People discuss work more often, but accountability doesn't move. The message is there. The ownership isn't.
Townhalls and offsites are even trickier. They can create a burst of shared intent, which is useful, but intent doesn't survive long if the weekly rhythm still rewards functional protection. Leaders leave inspired. Then the next cross-functional trade-off lands on someone's desk and the old habits return.
A silo-busting programme sticks only when it changes structure, measurement, or cadence. If it changes none of them, it's theatre.
The workplace research referenced earlier is useful here because it frames silos as structural, cultural, and technological barriers, not just a messaging problem. That matters in the UK context, where weak productivity growth means organisations can't afford sloppy cross-functional work. When delivery is already under pressure, a badly designed operating rhythm becomes a performance risk, not a soft issue.
The right intervention depends on the diagnosis. If the problem is unclear ownership, fix structure. If the problem is local incentives, fix measurement. If the problem is that dependencies keep arriving too late, fix cadence. Don't run every lever at once and hope the organisation absorbs it. That usually creates fatigue, not alignment.
Designing Cross-Functional Governance That Sticks
Governance is where most silo fixes go to die because leaders confuse activity with authority. More meetings don't help if nobody knows what decision the meeting is for. Better governance is smaller, sharper, and built around actual decision rights.
Three forums, three decisions
A weekly delivery review should exist to unblock dependencies and re-prioritise within the week. Keep it tight. The people in the room should be the ones who can move work, not just observe it. If an issue can't be resolved there, it needs a named escalation path.
A monthly portfolio review is for shifting capacity and re-scoping work. Leaders stop pretending every initiative can stay alive at once. If something more valuable has emerged, the portfolio needs to move. Otherwise the organisation is just carrying too much WIP and calling it ambition.
A quarterly business review resets priorities and strategic bets. Company-level choices get re-confirmed or changed. It should be the forum that answers, “What matters now?” not a long recap of what happened.
Each forum needs a named owner for every shared outcome. Not a sponsor in the ceremonial sense. An owner who is accountable for the cross-functional result, with enough authority to surface problems early and enough clarity to escalate when trade-offs can't be solved lower down.
Avoid the bureaucracy trap
The politics matter here. If you give cross-functional leaders responsibility but no real authority, you create frustration. If you create another layer of sign-off, you create drag. The point is not to centralise every decision. It's to make the decision boundary visible so people know where to act and where to escalate.
Rule of thumb: a governance forum is valuable only if someone leaves it with a changed priority, a cleared blocker, or a named owner.
The practical test is simple. If a meeting repeats the same cross-team issue three times, it's not a coordination forum. It's an expensive symptom. governance meetings only earn their place when they change the flow of work.
Using OKRs as the Alignment Layer Across Teams
OKRs are useful here, but only if they sit inside the operating rhythm rather than floating above it as a quarterly writing exercise. Treated properly, they give leaders a common language for shared outcomes, dependencies, and trade-offs. Treated badly, they become a list of tasks with a neat title.
A simple example from a growth launch
Take a scale-up launching a new product line into an existing market. The company objective might be to win traction in that segment without weakening the current customer base. That objective is broad on purpose. It creates a shared destination.
Product then writes key results tied to adoption and product readiness. Sales writes key results tied to qualified pipeline and conversion quality. Customer success writes key results tied to retention and onboarding experience. Each function still has its own work, but none of it should be framed as a local victory if the shared outcome is missed.
The point is not to force every team to share identical metrics. It's to make sure each team's key results connect to a company objective that depends on more than one function. That's where silos start to lose their power. People can still own distinct work, but they're no longer allowed to define success in isolation.
What goes wrong with OKRs
The biggest failure mode is turning OKRs into a task list. That gives people the language of alignment without the discipline. Another common mistake is writing goals that sound ambitious but can't be measured, which means no one can tell whether progress is real. The third is rewriting OKRs mid-quarter to look healthier than they are.
The alignment guide from The OKR Hub's OKR alignment approach is relevant because it keeps ownership clear and priorities narrow. That matters in siloed environments. Fewer priorities force real trade-offs, and clear ownership stops every team from assuming someone else will deal with the dependency.
The safest use of OKRs is as the language the governance rhythm runs on. The weekly review checks blockers. The monthly review reshapes capacity. The quarterly review resets the bets. OKRs become the thread that connects all three, which is exactly why they help break down silos when they're embedded properly.
Measuring Whether Silos Are Actually Breaking
If leaders can't see movement, they'll assume the programme is cosmetic. That's when support fades, usually just as the new rhythm starts to matter. Good measurement keeps this honest without creating a reporting burden nobody wants.
Four metric families worth tracking
Start with flow metrics. Track cross-team cycle time, dependency slippage, and the share of work blocked by another team. These tell you whether work is moving more cleanly across boundaries. If they don't improve, the friction is still there even if the meetings feel better.
Then add outcome metrics tied to shared OKRs. The question is simple. Are the cross-functional objectives moving on track, or are teams busy while the joint result stalls? Shared OKRs should become more visible in reviews, not more abstract.
Use health metrics as a pressure check. Engagement in high-friction roles, attrition where handoffs are painful, and voluntary cross-team moves can all show whether people experience the organisation as workable. If the work feels impossible, the system will eventually tell you through turnover and disengagement.
Finally, watch signal metrics. A rising volume of escalations or repeated surprise reprioritisations usually means the operating rhythm isn't catching issues early enough. Those are noisy signals, but they're useful because they show where the process is failing before the headline numbers move.
| Metric family | What it measures | Example metric | Where it lives |
|---|---|---|---|
| Flow metrics | Whether work moves across teams smoothly | Cross-team cycle time | Delivery reviews |
| Outcome metrics | Whether shared goals are landing | Shared OKRs on track | Quarterly business review |
| Health metrics | How the system feels to the people in it | Engagement in high-friction roles | People dashboards |
| Signal metrics | Early signs of coordination breakdown | Surprise reprioritisations | Weekly governance |
Baseline them once, then review them inside the governance cadence. Don't build a separate reporting ritual just to prove the first ritual exists. That creates another silo around measurement, which is exactly the opposite of what you want.
Sustaining Alignment Beyond the Launch
Most organisations can sustain a new discipline for a few weeks. The ultimate test is what happens when attention shifts, a senior leader gets busy, or a quarter ends badly. Silos come back fast when the rhythm turns optional.
A 30-60-90 day pattern that holds
In the first 30 days, stabilise the diagnosis and the governance cadence. Tighten the meeting agenda. Clarify owners. Make sure the weekly, monthly, and quarterly forums are making decisions, not just exchanging updates. If leaders still can't tell who owns what, don't move on yet.
From days 31 to 60, run the first full cycle of cross-functional OKRs through the new rhythm. The organisation learns whether the design works under pressure. Make at least one visible course correction. That tells people the system is live, not ceremonial.
From days 61 to 90, retire the old rituals that no longer add value. Keep the ones that produce decisions, unblock work, or improve shared outcomes. This is also where leaders need to stop treating alignment as a campaign and start treating it as how the business runs.
Leadership forums help here when they're used properly. A good external event, like elevating events through leadership, can sharpen the conversation, but only if the internal operating rhythm is ready to carry the change afterwards. Events can start momentum. They can't replace governance.
One more point matters. The habits that keep silos down are the same habits that build a capable community of practice across functions, especially when teams are distributed and under pressure. That's why a community of practice can be a useful support mechanism, not as a talking shop, but as a place where leaders compare notes on what is working.
Breaking down silos isn't a launch event. It's a discipline. If your team needs help diagnosing the blocker, designing a sharper operating rhythm, or wiring OKRs into cross-functional governance, The OKR Hub works with leadership teams on exactly that. Visit The OKR Hub to explore OKR consulting, implementation support, and a practical assessment of where alignment is breaking down.