Why Cross-Functional Collaboration Breaks Down at the Manager Level

Ask a leadership team where execution slows down and the answers tend to point sideways. Sales says delivery is too slow. Delivery says sales promises what does not exist yet. Finance waits on numbers operations sends late, and operations waits on approvals finance has not prioritized. Viewed one at a time, every team is working hard and doing reasonably well.
The trouble sits in the space between them. Cross-functional collaboration in a growing company depends less on process maps than on a handful of manager relationships at the points where work changes hands. I spend a lot of time in those spaces with my clients, and the same patterns keep showing up.
Where cross-functional work actually gets stuck
Work moves well until it changes hands
Inside a single team, most problems get solved quickly. People sit in the same meetings, share the same priorities, and report to the same person. When something goes wrong, someone notices and someone decides. The moment work crosses into another function, all three of those advantages disappear at once. Priorities differ, meetings are separate, and nobody below the executive team shares a boss.
Three places the delays collect
When I map where execution slows down with a leadership team, the delays cluster in the same few places:
The handoff from making a promise to delivering it
The request that needs another team's time or budget
The decision two functions both believe they own
None of these appear on a project plan as risks. They show up later as rework, slipped dates, and customers who hear two different answers from the same company.
Why it lands on the managers
Senior leaders set direction and frontline employees do the work. Managers sit at the junction, translating one team's needs into another team's priorities several times a day. When two counterpart managers have a strong working relationship, most friction gets resolved in a five-minute conversation. When the relationship is weak, the same friction gets escalated, documented, and argued over for weeks.
The process is identical in both cases. The relationship decides how it runs.
How team loyalty turns into us versus them
Good managers protect their people
The managers caught up in cross-functional friction are rarely the weak ones. More often they are strong, caring leaders doing exactly what we ask of them: shielding their teams from unreasonable demands, defending their priorities, and pushing back when another group asks for too much. That loyalty is a big part of why their teams trust them.
When protection hardens into a story
Loyalty turns into friction gradually. A missed handoff becomes a story. The story gets retold in a team meeting, with a little less generosity each time. Before long, people stop picturing colleagues with competing pressures and start picturing an obstacle. The other department becomes "them," and every new delay confirms what everyone already believed.
What you hear when a team starts keeping score
You can usually hear the shift months before you see it in results. Listen for:
Jokes about the other department that everyone understands
Requests sent in writing so there is a record
Problems explained by who caused them
Wins celebrated only inside the team
Each of these feels harmless on its own. Together they tell you a team has started protecting itself from the colleagues it depends on.
The audience every manager forgets
A team learns how to treat other departments by listening to how its manager talks about them. An offhand comment after a frustrating call carries more weight than the manager intends, because the team takes it as permission. Few managers realize how closely they are being listened to on this subject.
Decision rights at the handoff points
Most arguments are about who decides
Underneath many cross-functional disputes sits a simple question nobody has answered: who gets to make this call? Can sales commit to a delivery date, or does operations? Can product change a specification after engineering has started, and if so, until when? When nobody has said, both managers assume the answer is them, and both feel undermined when the other acts.
Settle the calls on a calm Tuesday
The fix is unglamorous, and it works. For each handoff that keeps failing, the two managers on either side sit down and agree on a few things in writing:
Who makes the final decision
Who has to be consulted first
Who simply needs to be told
How quickly each side will respond
This is far easier to settle on a calm Tuesday than in the middle of a customer escalation. Most counterpart managers find they agree on more than they expected once someone asks the question directly.
Keep the answers somewhere both teams can see them, and revisit them when the business changes. A decision rule agreed for a smaller company can quietly become the next source of friction once the company has doubled.
Escalate side by side
Some decisions will still need to go up. When they do, the two managers should take them up together, with one shared description of the problem and the options. Separate escalations invite senior leaders to pick a side, and whichever side loses remembers it at the next handoff.
The counterpart relationship every manager should build
Meet before there is a problem
The most useful habit I see in strong cross-functional managers is also the simplest. They know their counterparts in other functions before anything goes wrong. A short conversation every couple of weeks covers what each team is working on, what is coming, and where the pressure sits. When a problem does arrive, it lands on a relationship that already exists. Two managers who have spent time together give each other the benefit of the doubt. Two strangers rarely do.
Learn the other team's scoreboard
Most friction makes sense once you know what the other team is measured on. Operations is judged on reliability, so it resists last-minute changes. Sales is judged on closed deals, so it pushes for flexibility. Both are doing their jobs well against different scoreboards. Managers who understand the other team's pressures stop reading every pushback as personal.
Raise it early, directly, and in private
When friction shows up, the strongest move is often the most uncomfortable one: calling the counterpart manager and naming the problem before complaining to your own team or escalating it. That takes what I call Emotional Courage. Operational Courage, the bold decisions and visible risks, gets celebrated. Emotional Courage is quieter: telling the truth, starting the hard conversation while it still feels awkward, and repairing what was damaged. Most managers wait until frustration gives them the push, and by then the conversation is harder than it needed to be.
Speak about them the way you want to be spoken about
A useful standard is to talk about the other team in front of your own people the way you would want its manager to talk about yours. When something goes wrong, describe the problem without assigning blame. When the other team helps, say so out loud. Your people will follow your lead faster than you expect.
What senior leaders do that makes the friction worse
Disagreements at the top travel down
Friction between two managers often mirrors friction between their leaders. When two executives are quietly at odds, their teams pick it up quickly and take sides on their behalf. A leadership team can list cross-functional collaboration among its values. That is Stated Culture. What people absorb is Lived Culture: what they actually experience, including every time two leaders disagree in front of them. Lived Culture is the only one that counts.
Scorecards that set teams against each other
Senior leaders also create friction through how they set goals. If one function is rewarded for speed and another for caution, their managers will collide at every handoff while doing exactly what they were asked. Before blaming the managers, check whether the scorecards force the conflict.
Settling every dispute personally
When an executive resolves every cross-functional dispute personally, managers learn that escalation is the fastest route to a decision. It feels efficient in the moment. Over time it trains counterparts to argue their case upward, and it fills senior calendars with problems that belong two levels down.
Habits worth modeling from the top
A few habits from senior leaders make a noticeable difference:
Resolving executive disagreements in private
Sharing goals across functions wherever possible
Asking managers to bring disputes up jointly
Praising good handoffs in public
Next week I will look at a different kind of distance: the one between a manager and the people on their own team who work remotely.
If execution in your company keeps slowing at the same handoffs, the fix usually sits with the managers on either side. I work with leadership teams to find the handoffs costing the most time, clarify who decides at each one, and build the counterpart relationships that keep friction away from the customer. Book a handoff review and we will start with the one that breaks most often.

Comments