# Cross-Functional Communication: How to Work With Teams You Don't Manage Canonical URL: https://headwayskills.com/knowledge/communication/cross-functional-communication/ Markdown URL: https://headwayskills.com/knowledge/communication/cross-functional-communication.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving communication at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Cross-functional communication breaks down because no one has authority over anyone. Here's what actually gets other departments to respond, agree, and deliver. ## Key facts - Title: Cross-Functional Communication: How to Work With Teams You Don't Manage - Category: Communication - Primary skill: Communication - Related skills: Teamwork, Influence - Primary keyword: cross functional communication - Source page: https://headwayskills.com/knowledge/communication/cross-functional-communication/ ## What this page covers - Cross-functional communication breaks down because no one has authority over anyone. Here's what actually gets other departments to respond, agree, and deliver. - Practical guidance for cross functional communication - How this topic connects to Communication ## Detailed explanation You sent the request eight days ago. It was clear, it was polite, and it is [still sitting there unanswered](/knowledge/influence/follow-up-after-a-meeting/) while your own deadline keeps moving closer. Cross-functional communication is the exchange of information between people in different departments who do not share a manager, a set of priorities, or often even a vocabulary. It works when three things are in place: [the ask is explicit](/knowledge/communication/formal-how-to-write-email-for-requesting-something/), both sides agree what "done" means, and someone on each side is named as the owner. It stalls when any one of them is missing. Almost none of that is about how well you write an email — which is why, somewhere around day five, most people start quietly wondering whether the problem is them. ## Why cross-functional communication stalls so predictably Organizational communication research has a name for what you are doing when you message someone in another department: diagonal, or crosswise, communication — information moving between people who are neither on the same level of the hierarchy nor in the same chain of command. The definition is dry, but it contains the entire problem. Nobody in that exchange can instruct anybody. Your request is competing, on someone else's desk, against work their own manager assigned them, and there is no mechanism that makes yours win. This is not a rare situation, and you are not handling it unusually badly. A widely cited Harvard Business Review study found that 75% of cross-functional teams are dysfunctional, judged as failing on at least three of five criteria: staying on budget, staying on schedule, meeting specifications, meeting customer expectations, and staying aligned with company goals. Four of those five are coordination failures rather than capability failures — the work was doable, the alignment was not. And around 83% of companies say they use cross-functional teams, so this is the default way work is organized rather than a difficult assignment you drew by bad luck. Leadership is aware of it. Research from the American Management Association found that 83% of executives acknowledge silos exist in their organization, and 97% say those silos damage business outcomes. That gap is worth sitting with: the problem is recognized at the very top and it still lands in your inbox on a Tuesday. PMI's Pulse of the Profession research puts poor communication between teams at the root of more than half of project failures, which makes this the main way work goes wrong — not a soft extra you can get to later. The good news buried in all of it is that the causes are ordinary and specific, which means they can be worked on one at a time. ## The five channels cross-functional communication runs on Every request you make travels through one of a few distinct channels, and they do not behave the same way. Choosing badly is one of the most common reasons a reasonable ask goes nowhere, so it helps to see them separately. ### Horizontal communication This is the exchange between people at the same level in different functions — you and the designer, the analyst and the support lead. It is the everyday coordination channel: status, handovers, resolving overlaps. Because there is no authority gradient in either direction, it runs entirely on [reciprocity and goodwill](/knowledge/influence/influence-without-authority/). That makes it the friendliest channel and the easiest one to lose. Nothing forces anyone to prioritize you, so what you have built with that person over the previous months is effectively your leverage. ### Diagonal communication This is the one most people mean by cross-functional communication: reaching across both function and hierarchy at once, like a first-year employee putting a scoping question straight to another department's team lead. It bypasses the chain of command, which is exactly why it is the fastest route to an answer. It is also the channel most likely to create friction — not usually with the person you asked, but with your own manager, who hears about the conversation secondhand. Using it well means using it openly. ### Vertical communication This runs up and down your own reporting line: priorities coming down, blockers and status going up. In cross-functional work it is your fallback when a horizontal or diagonal channel has genuinely stalled. It is the only channel that carries real authority, and the only one where escalating is a legitimate move rather than a complaint about a peer. The judgment call is timing — too early and you have gone over someone's head over a delay they could have fixed; too late and the deadline is already gone. ### Formal channels These are the officially designated paths: project management systems, written briefs, scheduled reviews, documented decisions and specifications. Practitioner guides from Atlassian and Lucid converge on making communication explicit here — publishing a short brief that states what success is, what is out of scope, and who owns the decision. Formal channels are slow, and that is the trade: they are the only place where an agreement survives a change of personnel, a reorganization, or two people remembering the same meeting differently. ### Informal channels A direct message, a corridor conversation, a quick call to someone you already know. Sources consistently note that cross-functional communication tends to be less formal than the vertical or horizontal kind, and that familiarity removes obstacles readers otherwise assume are real. This is by far the fastest channel, and the only one you cannot create at the moment you need it. Every informal channel you have on the day of a crisis was built on an ordinary day months earlier. ## What makes cross-functional communication actually work The practical guidance across the field converges on a surprisingly narrow set of causes. Silos are described less as a structural problem than a definitional one: teams use different tools, chase different goals, and calculate the same metric in two different ways without either side noticing. That is why so much of the advice — from Synergita, Saviom, Atlassian and Lucid alike — starts with locking definitions before tracking anything, and with publishing a one-page brief naming the outcome, the timeframe, what is out of scope, and who decides. It sounds bureaucratic. In practice it is a single message you can send unilaterally, and it converts an implicit expectation into something the other person can agree or object to. The second recurring practice is dependency mapping, and the detail that distinguishes it from a normal task list is confirming a named owner on *both* sides of each dependency before work starts. An unconfirmed owner in another department is the standard point of failure: everyone assumes the request landed with someone, and it landed with nobody. The third is the one that has to happen before you need it. Sources note that unfamiliarity with people on other teams makes readers perceive obstacles that are not actually there — the silence you read as a snub is usually a queue. Getting to know [your counterparts](/knowledge/networking/company-networking/) outside the moment of asking is the only genuinely preventive move available, and it is the reason two people with identical requests get different response times. What almost none of the guidance covers is the end. Closing the loop — telling the other team what happened with the thing they delivered — gets a fraction of the coverage that tooling does, and it is what turns a one-time transaction into a relationship that answers you faster next quarter. Knowing all this is one thing; knowing which part is your own weak link is another, and it is worth getting an honest read on [where your own gaps sit](https://assessment.headwayskills.com/) rather than guessing. ## The skills behind getting other teams to move Look back at what actually decided each outcome above and very little of it was process. It was how clearly the ask was made, how much trust already existed, and whether anyone could persuade someone with no obligation to say yes. **Communication** is the most direct of these. Working across departments is where the fundamentals stop being optional: leading with the main point instead of burying it, being brief and explicit about what you need and by when, and adapting to how the other person actually takes in information rather than how you prefer to send it. It also means choosing the medium deliberately — a conversation when something is contested or complex, writing when the other side needs time or the decision must survive being remembered. **Teamwork** is what makes a temporary set of dependencies behave like a team. Trust here is built the unglamorous way: doing what you committed to, being straight about slippage early, and respecting that another function is optimizing for something legitimate that is not your deadline. It also means disagreeing constructively — engaging the real argument about scope or priority without making it personal, then committing to whatever gets decided. **Influence** is what is left when you have no authority, which across a department boundary is always. That means preparing properly by working out what is genuinely in it for the other side and how their function makes decisions, pitching simply and honestly enough to name the drawbacks too, and then persisting — following up on commitments and keeping momentum without becoming someone people avoid. A reputation for delivering is what makes your next request land faster than a stranger's. The framework these three come from counts twelve such skills in all, and the free Job Skills Test measures where you stand on every one of them — useful here because cross-functional problems rarely trace back to just one. If any of the three above felt uncomfortably familiar, [how your skills measure up](https://assessment.headwayskills.com/) is the fastest way to find out which one to start with. You may already recognize parts of this in how you work — perhaps you are the one who confirms in writing what was agreed, or who checks in with a counterpart before there is anything to ask for. The parts that do not come naturally yet are learnable behaviors rather than fixed traits, and building them does not require becoming a different person at work. They also tend to count for more as your responsibilities grow: the more of your results depend on people you do not manage, the more of your day runs on this. By reading this far instead of sending a fourth follow-up email, you have already done the part most people skip — treating the problem as something with causes rather than as someone else's fault. ## See which part is yours to work on You have the channels and the practices; the only thing left is finding out which of them you already handle well and which one is quietly costing you. The **free** Job Skills Test is a short self-assessment that shows where you stand across all twelve work skills — including the communication, teamwork, and influence habits that cross-functional work runs on — and points you to the ones that will make the biggest difference right now. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, and about 7 minutes from start to finish.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Cross-functional communication breaks down because no one has authority over anyone. Here's what actually gets other departments to respond, agree, and deliver. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Teamwork, Influence. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/teamwork.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/cross-functional-communication/ Preferred summary: "Cross-functional communication breaks down because no one has authority over anyone. Here's what actually gets other departments to respond, agree, and deliver." ## Change log - 2026-07-07: Content collection version published.