The Myth of Cross-Functional Collaboration

Why Cross-Functional Structures Rarely Deliver the Collaboration They Promise

Issue 255, March 12, 2026

There is a particular optimism that appears in organizations whenever someone proposes the creation of a cross-functional team. The assumption is almost immediate: if we can just bring the right functions together, many of the problems slowing progress will begin to disappear. Silos will break down. Collaboration will improve. Alignment will follow.

It is an appealing idea. It is also one of the most persistent myths in modern organizational design.

The language surrounding cross-functional work is almost always the same: break down silos, increase collaboration, bring diverse perspectives together. In many conference rooms, the decision to create a cross-functional structure is treated as though it were the solution itself rather than the beginning of a far more complicated problem.

It almost never is, of course.

I have spent years working with organizations navigating complex operational and strategic challenges, and a persistent pattern I encounter is the gap between what cross-functional structures promise and what they actually deliver. The matrix looks elegant on a slide. In practice, it introduces a set of tensions that most organizations are not prepared to manage. Why? Because most leaders are not trained to recognize those tensions until they have already calcified into near or complete dysfunction.

This observation is not without evidence. Gartner research has found that 78% of leaders report experiencing what they call “collaboration drag,” where the overhead of coordinating across boundaries actually slows decision-making rather than improving it. And, Harvard Business Review has published research showing that employees who routinely work across organizational boundaries often experience higher levels of burnout and role overload.

So, the promise of cross-functional work is collaboration. The reality, in too many cases, is exhaustion, inertia, and confusion.

The Appeal of the Matrix

The idea behind matrix and cross-functional structures is sound in theory. Like so many things are. Jay Galbraith, the notable organizational theorist, consultant, and professor, articulated it well decades ago: as the complexity of work increases, organizations need lateral connections that allow information to flow across traditional reporting lines. When work requires input from multiple domains of expertise, putting those experts in a shared structure should, logically, produce better outcomes.

The problem is that organizations tend to treat the structure as a framework and structure for the collaboration itself. Like waving a wand and assuming the rabbit jumps out of the hat. Naming a group “cross-functional” does not make it collaborative any more than labeling a meeting “strategic” makes it productive. The structure is only a container. What matters then is what happens inside it, and that is where most organizations stop paying attention.

In a 2024 analysis published in Harvard Business Review, researchers identified that cross-functional collaboration stalls most frequently not because of technical or resource constraints, but because of misaligned incentives, unclear authority, and what the authors describe as coordination neglect, the tendency for teams to underestimate the effort required to actually work together. The structure creates the appearance of alignment. The underlying organizational systems continue to reward something else entirely. The human factor plays strongly here in that the structure does not take into account the myriad of personalities, internal fiefdoms, and highly influential organizational politics.

The Invisible Organization

Every organization has two structures. There is the one on the chart, with its clean lines and defined reporting relationships. The one that serves as the basis for developing the cross-functional or matrix structure.

And there is the one that actually governs how work gets done: the informal network of relationships, favors, influence, and trust that determines who gets heard, who gets resources, and whose priorities take precedence when conflicts arise.

Rosabeth Moss Kanter, a professor at Harvard Business School, identified this dynamic decades ago, noting that formal authority is only one of several power sources in organizations, and often not the most consequential. When a cross-functional team is assembled, each member brings not just their expertise but their allegiance to a functional home. Their performance review, their promotion, and their career trajectory are all still governed by their functional manager. The cross-functional assignment is, in most cases, an addition to their existing responsibilities rather than a replacement.

This creates a structural double bind. The team member is expected to prioritize the cross-functional work, but their career incentives point them back toward their functional home. When those two sets of expectations conflict, and they will, the functional loyalty almost always wins. Not because people are disloyal or uncooperative, but because the system has made the rational choice clear.

Research from Harvard Business Review in March 2025 identified three distinct types of organizational silos that stifle collaboration: structural silos based on departmental boundaries, knowledge silos where expertise remains trapped within teams, and identity silos where professional identification with a function overrides identification with a shared mission. Cross-functional structures typically address only the first type while leaving the other two completely intact. I have covered many of these silo types directly or framed as a foundational basis of understanding in the episodes of The Human Factor Podcast.

Coordination Is Harder Than We Admit

Ronald Coase, one of the most influential economists of the twentieth century, won a Nobel Prize in part for articulating what should be obvious: coordination has costs. Every handoff, every alignment meeting, every shared decision introduces friction. In a well-functioning organizational hierarchy, those costs are managed through clear authority and established routines. In a cross-functional organizational structure, those costs multiply because the authority is distributed and the routines have not yet been established. Most likely because clear authority, role clarity and reporting structures are so strongly ingrained in the organizational structure.

I am not arguing against collaboration. I am arguing for honesty about what collaboration actually requires. We often do not take the time or apply thought to understanding what is really needed.

When an organization launches a cross-functional initiative without investing in the coordination infrastructure to support it, they are essentially asking people to absorb those costs personally; change their professional identity, redefine their self-concept of their role as well as how they contribute value. The result, due to the very human factors and influences at play, is exactly what the research predicts: longer decision cycles, more meetings, more confusion, and a pervasive sense among team members that they are working harder without producing the optimistically expected better results. The additional burden often leads to overload.

I wrote about a related dynamic in Issue 228 of this newsletter, The Mental Overload of Modern Leadership, where I explored how the cumulative weight of context-switching, competing priorities, and decision density erodes a leader’s capacity over time. Cross-functional structures amplify every one of those pressures. They ask people to hold multiple contexts simultaneously, to navigate competing authority structures, and to make judgment calls in the absence of clear decision rights. The cognitive load is substantial, and it is almost never acknowledged due to ignorance or fear.

The Incentive Problem

Steven Kerr, best known for identifying common but often invisible organizational failures, published one of the most widely cited management papers of all time with “On the Folly of Rewarding A, While Hoping for B.” The insight is really simple: organizations consistently create incentive structures that reward behavior contrary to their stated goals. Cross-functional work is one of the clearest examples of this pattern in action.

Consider a product development team composed of members from engineering, marketing, and operations. The organization says it wants them to collaborate on a shared outcome. But engineering is measured on technical milestones. Marketing is measured on campaign performance. Operations is measured on cost efficiency. When the team needs to make a trade-off between speed, market impact, and cost, each member faces a choice between what the cross-functional team needs and what their performance evaluation rewards. The structure says collaborate. The incentive system says optimize for your function.

This is not a design flaw in any individual team. It is a systemic failure. When organizations launch cross-functional initiatives without changing incentives, they are asking people to ignore the signals embedded in compensation decisions, performance reviews, and promotion criteria.

That is not a strategy. It is wishful thinking.

When incentives are misaligned and authority is unclear, organizations rarely remain neutral. Power reorganizes itself informally.

Informal Authority Always Fills the Vacuum

When formal authority is unclear, informal authority fills the vacuum. This is one of the most predictable dynamics in organizational life, and cross-functional structures create the conditions for it to flourish. Without a clear decision-maker, the person with the most political capital, the loudest voice, or the closest relationship to senior leadership will steer the group, regardless of whether their perspective is the most informed or most relevant.

Research from the Project Management Institute examining matrix organizations has documented how functional managers often redirect resources or delay approvals in ways that quietly undermine cross-functional work. The behavior is rarely malicious. It is simply the natural response of people operating within a system that rewards functional performance while asking for cross-functional cooperation.

This is the invisible friction I explored in a previous issue of this newsletter, The Invisible Friction Slowing Your Strategy, where I examined how culture, capacity, and behavior create drag that no amount of strategic clarity can overcome. Cross-functional structures sit squarely at the intersection of all three. They require cultural norms that support shared accountability, organizational capacity to manage additional coordination complexity, and behavioral patterns that prioritize collective outcomes over individual metrics. When any one of those elements is missing, friction accumulates. When all three are absent, the structure becomes a liability.

The New Complication: Technology That Reinforces Boundaries

There is an emerging element to this challenge that deserves some attention. As organizations increasingly deploy AI and automation tools, there is a risk that these technologies will reinforce existing silos rather than dissolve them. Harvard Business Review has also explored how AI implementations often reinforce existing organizational silos when models are trained on function-specific data.

When marketing deploys AI tools trained on marketing data, and operations deploys tools trained on operational data, and finance deploys tools trained on financial data, each function builds a technology infrastructure that speaks its own language and optimizes for its own metrics. The result is a new kind of silo, one encoded in algorithms and data architectures rather than reporting lines, and one that is potentially even harder to dismantle because the boundaries are invisible to most of the people working within them.

This is not an argument against technology adoption. It is a reminder that every tool amplifies the organizational dynamics already in place and technology is not a solution to organizational issues in itself; it often creates challenges that go unaddressed.

If those dynamics are already producing collaboration, technology accelerates the existing collaboration. If those dynamics are siloed, technology accelerates separation. Cross-functional structures that do not address the underlying incentive and authority issues will find that technology makes the problem worse, not better.

What Real Collaboration Actually Requires

None of this means cross-functional work is impossible or undesirable. Research consistently shows that organizations with high levels of genuine cross-functional collaboration are up to five times more likely to be high-performing than those operating in functional isolation. The structure can work, but only when it is supported by deliberate investment in several areas that most organizations treat as afterthoughts.

Shared accountability that is real, not rhetorical. If team members are still evaluated primarily on functional metrics, the cross-functional work will always be secondary. This means redesigning performance evaluation systems, not just adding a line about “teamwork” to an existing review template. The metrics need to reflect the actual outcomes the team was assembled to produce, and those metrics need to carry real weight in compensation and advancement decisions.

Clear decision rights. One of the most damaging ambiguities in cross-functional work is who gets to make the call when disagreements arise. Without explicit decision-making authority, teams default to consensus, which in practice means either endless deliberation or deference to whoever has the most political power. I wrote about this last week. I defined it as Decision Theatre. Every cross-functional team should have a clearly defined decision-making framework that specifies who decides what, under what conditions, and through what process.

Investment in coordination infrastructure. Collaboration is not free. It requires time, tools, and dedicated attention. Organizations that expect cross-functional teams to self-organize without any additional investment in coordination, whether that means dedicated project management, shared communication platforms, or simply protected time for collaborative work, are setting those teams up for the kind of coordination failure the research predicts.

Psychological safety. Amy Edmondson’s research, which I cite often, has demonstrated that psychological safety, the belief that one can speak up without risk of punishment or humiliation, is essential for effective team performance. In cross-functional settings, where members come from different professional cultures, use different technical languages, and carry different assumptions about what constitutes good work, psychological safety becomes even more critical. Without it, the diversity of perspective that is supposed to be the team’s greatest asset becomes a source of misunderstanding and conflict instead.

Leadership that models the behavior. If senior leaders continue to operate in functional silos while asking their teams to work cross-functionally, the message is clear, regardless of the stated intention. Cross-functional collaboration requires leaders who are willing to share resources, cede control, and measure success in terms of shared outcomes rather than functional dominance.

Structure Cannot Replace Leadership

The fundamental error in most cross-functional initiatives is the belief that structure can substitute for leadership. Drawing new lines on an organizational chart is infinitely easier than doing the sustained, difficult work of aligning incentives, building trust, clarifying authority, and investing in the coordination infrastructure that real collaboration demands.

William Bridges captured this dynamic precisely when he distinguished between change and transition. Change is the external event: the reorganization, the new team charter, the cross-functional mandate. Transition is the internal process by which people actually let go of old patterns and adopt new ones. Organizations are very good at implementing change. They are far less skilled at supporting transition. And without transition, the change remains cosmetic.

I have seen this play out dozens of times. An organization announces a cross-functional initiative with great fanfare. Six months later, the same decisions are being made by the same people through the same informal channels, just with an additional layer of meetings and reporting that everyone quietly resents. The structure changed. The behavior did not.

The Real Work

If your organization is considering a cross-functional structure, or struggling with one already in place, the question is not whether the concept is valid. It is whether you are willing to do the work the concept demands. That means honest conversation about where power actually resides, where incentives genuinely point, and whether the organization’s culture can support the kind of vulnerability and shared accountability that real collaboration requires.

Cross-functional work is not a structural problem with a structural solution. It is a leadership challenge that requires sustained attention to the human systems and human dynamics operating beneath the surface of every organizational chart. The structure provides the container. Leadership, and only leadership, provides the conditions under which genuine collaboration becomes possible.

The myth of cross-functional work persists because structural change is easy to announce and difficult to challenge. Drawing new reporting lines feels like progress.

The harder work is confronting the incentives, authority structures, and informal power networks that actually govern how decisions get made.

Until organizations address those forces, cross-functional teams will continue to promise collaboration while quietly reproducing the very silos they were created to eliminate.