Bridging the Gap: Fostering Collaboration Across Departments and Organisations

Cross-departmental collaboration is one of those areas where I have found that confident theories about what ought to work and the actual experience of watching teams try to collaborate across boundaries have very little to do with each other. I have worked across a range of organisations, and have been on both sides of various functional divides, and the consistent pattern is not that people do not want to collaborate, but that the structures they are working in make genuine collaboration considerably harder than it appears from the outside.

Why the siloing is usually structural, not personal

The most visible symptom of poor cross-functional working, in my experience, is not conflict, it is invisible duplication and missed handoffs. Two teams working in parallel on overlapping problems without either being aware of the overlap; a decision made in one function that creates significant downstream work for another function that was never consulted; a requirement implemented correctly by the team that wrote it, which then breaks something the neighbouring team had been quietly depending on. None of these happen because the people involved are difficult or parochial. They happen because the organisation did not build a structure that made the dependency visible before it became a problem.

What I have noticed in the organisations where this is worst is that each function has developed, entirely sensibly, a set of metrics and incentives that measure its own performance in isolation. Engineering is measured on throughput and technical quality; operations on reliability and cost; product on feature delivery against roadmap. Each of those is a reasonable thing to measure. The dysfunction emerges when optimising one team’s metric comes at the cost of making somebody else’s situation harder, and when the structure does not make that tradeoff visible until well after the fact.

What actually helps

The interventions I have seen make a genuine difference are, without exception, cheaper and more structural than the elaborate cross-functional programmes organisations typically invest in. Regular cross-functional communication, even in a fairly lightweight form, a standing sync that happens consistently every week rather than an elaborate quarterly alignment that nobody quite finds time to prepare for properly, surfaces the dependencies and overlaps that would otherwise stay invisible until they cause a problem. The format matters less than the consistency; a brief weekly conversation between the right people tends to be worth considerably more than an annual off-site with detailed agendas and no follow-through.

Cross-departmental exposure, having people spend time actually working alongside another team, even briefly, builds a quality of mutual understanding that is very difficult to generate through process alone. In my experience, engineers who have spent time with the operations or customer-facing side of a business make materially different technical decisions afterwards, because they have a concrete mental model of what the problems actually look like in practice rather than an abstract description of what they are supposed to be solving. The informal relationships that form through this kind of exposure also tend to persist and improve communication long after the formal programme has ended, which gives the investment an unusually long tail relative to its cost.

Shared tooling helps when the tool genuinely reduces friction rather than adding a new coordination layer. The test I apply is roughly: does this make it easier to see what other people are working on and to contribute across boundaries, or does it create another inbox? Tools that surface shared work and allow asynchronous contribution tend to hold up; those that require everyone to be actively present simultaneously tend to quietly fall out of use as soon as the initial energy wears off.

Recognising cross-functional work explicitly, through how senior leaders talk about it, through visible acknowledgement of cross-team contributions, through making it count in whatever review or reward process the organisation has, matters more than it might seem. Most organisations’ recognition structures are designed around individual departments, which means they quietly reinforce exactly the boundaries they nominally want to reduce. If collaboration across teams is genuinely valued, that needs to show up in what gets noticed and rewarded, not just in what gets said in all-hands presentations.

The structural honest truth

The uncomfortable thing I keep coming back to is that most of the cross-functional problems I have seen are not really communication problems. They are incentive problems, and sometimes structural design problems, and a communication initiative will not fix an incentive problem. Organisations that invest heavily in collaboration tools and cross-functional workshops while leaving the underlying metrics and resourcing structures unchanged tend to find themselves in the same position eighteen months later, perhaps with better shared vocabulary and rather more cynicism about the next initiative.

The changes that actually stick are the ones where leadership is willing to redesign something structural, how teams are measured, how resources are allocated across boundaries, how decisions that affect multiple functions are actually made and by whom, rather than simply asking people to communicate more. That is a harder conversation to have, partly because it requires acknowledging that the problem is at least partly a design failure rather than a failure of individual goodwill. But in my experience it is the conversation that tends to lead somewhere, and the other one mostly does not.