Cross-Functional Collaboration: Working Across the Silos

Cross-functional collaboration is the work of getting people from different teams — engineering, sales, marketing, finance, legal — to pull together on a shared goal, even though they report to different bosses, speak different professional languages, and are measured on different things. Done well, it’s how the biggest, most valuable work gets done; done badly, it’s where projects quietly go to die. The difference comes down to a few things: a genuinely shared goal, translating across functions, influencing people you don’t manage, and building real relationships across the lines.

It’s worth getting right because the default is failure. In a well-known Harvard Business Review study, Behnam Tabrizi examined 95 cross-functional teams across 25 companies and found that 75 percent of them were dysfunctional — falling short on at least three of five measures like budget, schedule, specs, customer expectations, and alignment with company goals. The encouraging part of the same research: teams with strong, aligned leadership support succeeded 76 percent of the time, versus just 19 percent with weak support. Cross-functional work isn’t doomed; it just demands deliberate habits the default doesn’t supply. Here are the four that matter most.

Aligning on a genuinely shared goal

The first and biggest challenge is that each function arrives with its own objective: sales wants the deal closed, engineering wants it built right, legal wants the risk down, finance wants the cost controlled. Each is legitimate, and left unmanaged they pull the project apart. High-functioning cross-functional teams start by agreeing on one overarching goal that sits above any single function’s metrics — what success looks like for the whole effort, not for any one department. This is where leadership alignment matters so much in the research: when the executives over each function are visibly behind the shared objective, the teams beneath them stop optimizing their own slice at the project’s expense. Without that common north star, every decision becomes a turf negotiation.

Bridging different languages and priorities

The second challenge is that functions genuinely don’t speak the same language. The word “done” means something different to a designer, a developer, and a lawyer; “urgent” compresses or stretches depending on the function’s rhythm. Effective cross-functional collaborators act as translators — taking the time to understand what the other function actually cares about and why, and explaining their own constraints in terms the other side can grasp. Curiosity beats assuming bad faith: when marketing seems to be slowing things down, it’s usually optimizing for something real that engineering can’t see. Learning enough about each function’s world to anticipate its concerns is what turns a collision of priorities into a workable plan. A small habit pays off here: before a cross-functional meeting, spend a few minutes asking what the other functions will be worried about, and address it before they have to raise it. People relax considerably when they can tell you’ve actually thought about their side, not just your own.

Influencing without authority

The third challenge is structural: in cross-functional work, you usually can’t tell anyone what to do. The people whose help you need don’t report to you, so command doesn’t work — influence does. That means understanding what’s in it for the other person and their team, making it easy for them to say yes, building credibility through reliability, and bringing people along rather than steamrolling them. The currency is trust and reciprocity, not org-chart power. If you want a clearer sense of how you work across teams — whether you tend to build buy-in or push too hard — an honest outside read is a good place to start, because influence is something most of us misjudge in ourselves.

Building relationships and communication across silos

The fourth challenge is that silos perpetuate themselves — people default to their own team and let the cross-functional connections wither. The antidote is proactive relationship-building and over-communication. Strong cross-functional collaborators invest in relationships before they need them, so that when a project demands fast coordination, the trust is already there. They over-communicate across the boundary — keeping other functions informed of changes, decisions, and slips that affect them, rather than assuming the message traveled. And they create shared visibility: a single source of truth everyone can see, so no function is operating on stale information. Relationships and clear communication are the connective tissue that holds a cross-functional effort together when the formal structure won’t. The teams that struggle most are usually the ones that only talk when something has already gone wrong; the ones that thrive keep a steady, low-stakes flow of contact going so problems surface early and get solved before they harden.

The skills underneath working across functions

Step back and cross-functional collaboration draws on a few underlying, learnable skills that reach well beyond any single project.

Teamwork is the foundation, stretched across boundaries. Putting a shared purpose above your own team’s agenda, building trust, coordinating work, and managing the inevitable disagreement constructively are the same teamwork habits that make any group function — just applied to people who don’t share your manager or your metrics. The best cross-functional collaborators treat the whole effort as their team, not just their department’s corner of it.

Networking is what makes it possible at all. Building and maintaining relationships across the organization — connecting with people in other functions, including those quite different from you, before you need them — is exactly the skill cross-functional work runs on. A wide, well-tended network across departments means that when a project spans silos, you already know who to call and they already trust you enough to help.

Influence is the engine when authority is absent. Getting buy-in, understanding others’ interests, building credibility, and bringing people along through persuasion rather than position is how anything moves across functions. Leading peers without authority is one of the highest-leverage skills there is, and cross-functional work is where it’s most tested. These three are part of the wider set of work skills the free Work Skills Test measures, so you can see which one to strengthen if working across teams is where you tend to get stuck.

You may already do parts of this well — building bridges before you need them, translating between functions, winning people over rather than pulling rank. That’s worth recognizing, because working across silos isn’t a talent some people are simply born with; it’s a set of habits anyone can build while staying entirely themselves. And it matters more as you advance — the further you go, the more your impact depends on work that spans teams you don’t control. By thinking about how to do it well, you’re already ahead of the many who treat cross-functional friction as just the way things are.

See how you work across teams

You’ve got the four dimensions; what’s left is an honest read on which one is your strength and which holds you up when work crosses team lines, since it’s hard to judge from the inside. The free Work Skills Test is a short self-assessment that shows where you stand across all twelve work skills — including the teamwork, networking, and influence habits that cross-functional collaboration draws on — and points you to the one worth working on first.

Take the skills test

Free, and it takes about 7 minutes.