Cross-functional team conflict becomes easier to examine when leaders stop treating every disagreement as a personality problem. Two departments can each follow their own instructions and still make incompatible decisions. Start with the shared work, the information each team receives and the trade-off nobody has clearly authorized.
This guide addresses ordinary coordination disagreements. Threats, harassment, discrimination or other serious conduct concerns require the organization's appropriate reporting and response procedures, not an informal facilitation exercise. Do not pressure employees to negotiate away required protections or disclose private personnel information.
Describe one disputed handoff
Choose a recent example both teams can examine. State what was requested, what the receiving team needed, when it was needed and what actually arrived. Separate the record from assumptions about motivation. 'The receiving team did not have the approved specification' is a different claim from 'They never cooperate.'
Invite each team to explain its constraints before choosing the response. A disagreement over whether a document was supplied needs evidence. A disagreement over which customer receives limited capacity needs an authorized priority decision. A disagreement over who approves an exception needs an authority clarification. These are not interchangeable problems.
Find the shared outcome and the competing measures
Ask what the business needs across the complete flow of work. Then examine what each team is being asked to optimize. If one function is rewarded for accepting every urgent request while another is expected to protect a stable plan, their local success measures may generate the repeated argument.
The Center for Creative Leadership's boundary-spanning guidance emphasizes working across organizational boundaries. Our practical application is to put the affected leaders around the same work example and make the incompatible expectations explicit. A friendly conversation alone does not authorize a trade-off.
Name who can resolve the decision
Identify the role authorized to decide the priority, acceptance rule or exception. Collect the required input without turning every contributor into a joint approver. If the decision exceeds either department's authority, state what must be escalated and who will carry the question.
Use the decision-rights example to separate authority, consultation and escalation. A facilitator can help the group understand a disagreement without having the authority to settle it. Record a recommendation as a recommendation until the proper owner accepts it.
Worked example: urgent work versus a stable plan
In a fictional business, a customer-facing team promises a changed delivery date while operations believes the existing plan remains approved. Customer service sees responsiveness; operations sees an unauthorized disruption. Telling both teams to communicate better leaves the approval question untouched.
The responsible leader first clarifies who can authorize a changed commitment and what evidence is needed. The teams then agree how a proposed change reaches that owner, how a decision is communicated and what happens while approval is pending. The example does not prescribe a specific delivery or safety rule; those remain governed by the organization's approved requirements.
Record the agreement in usable terms
Capture the shared outcome, required input, sender, receiving owner, acceptance condition, decision boundary and escalation route. State what happens when input is missing or the owner is absent. Keep the agreement short enough that the people doing the work can explain it without interpreting a long policy document.
Test it against a second suitable example before introducing it broadly. Ask each team what it would do next. Different answers reveal ambiguity while it can still be corrected. The alignment-workshop agenda provides a discussion structure when several leaders need to agree the underlying priority.
Review whether the conflict changed
Inspect subsequent handoffs for missing inputs, reopened decisions and unresolved exceptions. Fewer complaints do not automatically mean improvement; people may have stopped raising concerns. Ask whether the next owner received usable information and whether legitimate questions reached the decision-maker in time.
For a published client example, read Liz's conflict-to-alignment story. It is one reported engagement, not evidence that every disagreement follows the same pattern. If the same conflict recurs across departments despite local fixes, discuss the leadership conditions with Shannon.
About this resource: Prepared with AI-assisted drafting and editorial review. The worked example is hypothetical, not a reported client result. Cover illustration: AI-generated.