Embedded Files
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 it's seldom a people problem. It's usually a system that was never properly designed for collaboration in the first place.
What actually 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 people could agree to rather than what would actually be best for the organization.
How setting context helps
Effective cross-functional collaboration doesn't start with the people doing the work. It starts at the cross-over point level — the most senior role that spans all the functions involved in the process, and that is therefore structurally accountable for how those functions work together.
That role is the cross-over point manager
The cross-over point manager's primary contribution to cross-functional collaboration is not to attend working meetings or make operational decisions. It is to set context — the framework that tells cross-functional team members what they are collectively trying to achieve, how their work connects to broader organizational strategy, what success looks like and how it will be measured, what criteria should guide trade-offs when functional priorities conflict, and how disagreements that can't be resolved at the team level should be escalated. Without that context, employees are left to negotiate all of those questions themselves, in real time, under pressure. Some will manage it through strong relationships or force of personality. Most won't — not consistently, and not at scale.
Here is where a legitimate objection arises. In many organizations, the cross-over point manager sits three to five levels above the people doing the actual work. When I ask managers who that person is, the response is often the same: "They have no idea what's happening at our level. They're never going to get involved." That objection is legitimate because that's usually what happens. However, the answer is that if the cross-over point manager is too distant to set meaningful context, that is itself a structural problem — either the process has grown beyond the governance design that was meant to support it, or the accountability for stewardship has never been formally assigned.
But it is also worth being precise about what setting context actually requires. The cross-over point manager's job is not to get involved in the operational details two to five levels down. It is to set clear context for their own direct reports — the strategic rationale, the shared goals, the criteria for trade-offs, the escalation process — and to hold those direct reports accountable for cascading that context to the level below them, and so on down the chain. Each level translates the context for the next. By the time it reaches the people doing the actual cross-functional work, it should be specific enough to guide their decisions without requiring them to escalate constantly upward.
This is how good governance works in complex organizations. The cross-over point manager doesn't need visibility into every operational detail. They need to set context clearly enough that each subsequent level can do the same for theirs. But this is harder than it sounds. As context travels down it gets interpreted, adapted, and filtered through the priorities and constraints of each level — which means what reaches the people doing the actual cross-functional work may be several degrees removed from the original intent. That is not a failure of goodwill. It is a structural feature of how decisions and context move through organizations, and it requires each level to do more than pass context down — it requires them to actively check whether what they are passing on still reflects the original strategic intent, and correct for the distortions that their own constraints and priorities may have introduced.
In sum, context is not something teams can set for themselves. It is a governance task, and it belongs to whoever is structurally accountable for the cross-functional process — whether that person is one level up or five.
And it is not a one-time act. Because context gets reframed at each level to fit local reality, what reaches the people doing the actual work may be accurate at every step and still be distant from the original intent. Maintaining the integrity of context across the cascade requires ongoing attention, not just a good kickoff meeting.
Context alone isn't enough
Even with good context, cross-functional collaboration has structural requirements that need to be addressed explicitly.
The work needs to matter 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 rewarded will always be deprioritized.
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 — which is usually their own function.
And 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 or get decided by whoever is most persistent — neither of which produces good outcomes.
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.
Report abuse