Why cross-functional collaboration is hard

Many organizations treat cross-functional collaboration solely as a people problem. The solution, predictably, is also a people solution: team-building, communication training, workshops on working styles, appeals to shared values. These interventions can help but they don't solve the underlying problem. Like resilience training offered to overwhelmed employees, they make the situation more bearable without addressing the structural conditions that created it.

That's because the structural conditions were never properly designed for collaboration in the first place.

What makes cross-functional collaboration hard

When people from different functions need to work together, they bring with them different goals, different priorities, different definitions of success, and different pressures from their respective managers.

None of that is surprising. What is surprising is how rarely organizations address it structurally.

Instead, employees are expected to figure it out — to find common ground through goodwill, informal relationships, and the kind of influence-without-authority that sounds collaborative but puts enormous pressure on individuals to succeed at something the system hasn't set them up to do.

The result is predictable: people work hard, relationships get strained, and the collaboration produces outcomes that reflect what they could agree to rather than what would actually be best for the organization.

Solving this problem requires a more systemic approach

Because the gap is structural, it cannot be closed by better communication or more shared information

Two managers, each accountable to their own function, can negotiate in good faith and still not produce the best outcome for the business. Not because they lack context — though that is often also true — but because what's best for the business sometimes requires one function to absorb a real cost on behalf of the whole. No manager can reasonably be expected to voluntarily accept that cost for an outcome they are not accountable for, especially if they don't understand what the "whole" is. That is not a failure of goodwill. It is a rational response to their structural position.

Peer agreement has a ceiling. It stops where one side's losses become unacceptable. What's best for the business often lies outside that ceiling. And crucially, determining what's best for the business is not a calculation. It is a judgment call — an educated guess made under uncertainty, with incomplete information, about what will serve the organization as a whole. The question is not whether that guess will be made, but who is best positioned to make it well. The answer is the person who holds accountability for both functions, not because they have more information, but because their vantage point is structurally broader.

The cross-over point manager needs to set good context

Effective cross-functional collaboration doesn’t start with the teams doing the work. It starts at the cross-over point — the most senior manager who structurally spans all the functions involved and is accountable for how they work together.

The cross-over point manager’s primary contribution is not to make operational decisions, but to set context. This means providing a clear framework that defines:

• What the teams are collectively trying to achieve and how it connects to strategy.
• What success looks like and how it will be measured.
• The criteria for making trade-offs when functional priorities conflict.
• How unresolved disagreements should be escalated.

Without this guardrail, employees are left to negotiate these massive strategic questions themselves, under pressure. While a few will manage through sheer force of personality, most won’t, at least not consistently or at scale.

A common objection here is that this cross-over manager often sits three to five levels above the actual work, making them too distant to get involved. The good news is that setting context does not require diving into operational details. The cross-over manager’s job is to set clear context for their own direct reports, and hold them accountable for cascading and translating that context down the chain until it reaches the implementation level.

However, cascading correctly is challenging. As context travels down, it gets interpreted and filtered through the priorities of each layer. What reaches the frontline can easily be several degrees removed from the original intent. Preventing this distortion requires active stewardship. Each level must actively check, on a continuous basis, that the information they are passing down still reflects the original strategic intent.

The work needs to benefit to the people doing it — not just to the organization.

If contributing to a cross-functional project has no bearing on an employee's performance evaluation or recognition, they will rationally prioritize their functional work instead. Collaboration that is expected but not recognized and rewarded will always be deprioritized, especially if it comes at a cost. Expecting otherwise is not a high standard — it is a design failure dressed up as a values statement.

Employees need visible support from their own managers.

Cross-functional work takes time and attention away from functional goals. Without explicit backing from the leadership chain, employees will feel pulled in two directions and will default to wherever the accountability is clearest and has consequences — which is usually their own function.

There needs to be a clear, agreed-upon process for escalating conflicts that the team can't resolve on its own.

Without it, unresolved tensions either fester, get decided by whoever is most persistent, or are pushed under the rug by making compromises that satisfy no one.

The structural question worth asking

If cross-functional collaboration is a persistent problem in your organization, the question worth examining is not "how do we get people to collaborate better?" It is "have we actually designed the conditions in which collaboration can succeed?".

That means assigned accountability at the cross-over point, clear context cascaded to the people doing the work, incentives that reward collaboration rather than just functional performance, and a process for resolving conflicts that doesn't depend on goodwill alone.

Goodwill is not a system. And no amount of it will compensate for the structural conditions that make cross-functional collaboration harder than it needs to be.