How to Manage Conflict Between Teams
Learn how to manage conflict between teams by clarifying the issue, listening to different perspectives, evaluating trade-offs, and confirming decisions.
Conflict between teams often develops when people with different responsibilities, priorities, constraints, and measures of success depend on one another to complete important work.
Marketing may depend on sales, operations may depend on technology, and project teams may require decisions, resources, or expertise from several functions. These dependencies create legitimate opportunities for disagreement about scope, timing, risk, resources, ownership, or implementation.
The objective is not to eliminate every disagreement. Leaders need to help teams identify the issue, understand the different perspectives, clarify decision authority, evaluate trade-offs, and agree appropriate actions or escalation.
What Is Conflict Between Teams?
Conflict between teams is a disagreement or recurring tension involving people from different functions, departments, locations, business units, or professional groups.
Interteam conflict may concern:
- Different organizational priorities
- Competing demands for resources or capacity
- Unclear responsibilities or decision rights
- Dependencies between functions
- Different interpretations of risk
- Conflicting deadlines or commitments
- Incomplete or unevenly distributed information
- Service, customer, compliance, or implementation requirements
- Missed commitments or unresolved previous issues
Conflict does not necessarily indicate poor behavior or damaged relationships. Different functions are accountable for different outcomes and may evaluate the same proposal through different professional criteria.
Conflict becomes more difficult when teams personalize the disagreement, conceal relevant information, avoid necessary discussion, make assumptions about intent, or continue without a clear decision process.
Why Conflict Between Teams Occurs
Competing Priorities
Teams may support the same broad organizational objective while assigning different priority to cost, speed, quality, risk, customer impact, compliance, capacity, or long-term value.
A project team may need immediate specialist support while the functional team is already committed to operational work. The disagreement may concern the allocation of limited capacity rather than opposition to the project itself.
Different Measures of Success
Functions may be evaluated using measures that encourage different choices.
Sales may emphasize revenue and customer commitments. Operations may focus on service continuity and capacity. Finance may prioritize cost and financial exposure. Technology may examine security, integration, architecture, and support.
Conflict can develop when teams optimize for their own measures without making the effect on other functions visible.
Unclear Decision Authority
Teams may continue debating an issue because no one has clarified who recommends, who provides specialist input, who controls resources, and who makes the final decision.
Participation should not obscure authority. If a leader or governance body is responsible for the decision, that responsibility should remain visible.
Unowned Dependencies
A dependency exists when one team cannot complete its responsibility until another team provides a decision, resource, action, system, approval, or piece of information.
Conflict becomes more likely when the required contribution has no accepted owner, deadline, escalation route, or review point.
Incomplete Information
One team may possess technical, operational, commercial, financial, or regulatory information that another team does not know is missing.
Participants may interpret a recommendation as unreasonable when the actual problem is that each group is evaluating the issue using different information.
Previous Experience and Relationship History
Past delays, missed commitments, unresolved disputes, or poor communication can affect how teams interpret a new request.
A technically sound proposal may receive additional scrutiny when previous commitments were not completed or important consequences were not communicated.
Assumptions About Intent
Teams may interpret challenge as obstruction, caution as lack of commitment, urgency as disrespect, or disagreement as an attempt to protect territory.
These interpretations should be tested rather than treated as established facts.
Distinguish the Issue From the Relationship
Conflict discussions become harder when criticism of a proposal turns into judgment of a person or team.
Compare these statements:
- “Operations never supports strategic projects.”
- “The current implementation plan requires operational capacity that has not yet been allocated.”
The first statement assigns a general motive and identity. The second identifies a specific implementation issue that can be examined.
Before a conflict conversation, separate:
- Observable information from interpretation
- The current issue from previous unrelated disputes
- The effect of a decision from assumptions about intent
- A functional responsibility from a personal preference
- A legitimate constraint from an unwillingness to cooperate
This does not require avoiding direct language. Leaders can state a serious concern clearly without turning the conversation into an accusation about character or motivation.
Positions, Interests, and Responsibilities
Teams often communicate through positions: the specific outcome or solution they are requesting.
For example:
- Position: “The project needs an additional specialist immediately.”
- Underlying responsibility: “The project team must resolve an integration dependency before the next milestone.”
Another team may hold a competing position:
- Position: “No specialist can be released this month.”
- Underlying responsibility: “The operational team must maintain support for a critical service period.”
Exploring the responsibilities, constraints, risks, and interests behind each position can reveal alternatives such as revised sequencing, partial support, additional resources, changed scope, or escalation to the person who holds priority authority.
Not every conflict has a mutually beneficial solution. Limited resources and incompatible obligations may require a difficult decision. Understanding the underlying interests helps prepare that decision without pretending the trade-off has disappeared.
A Practical Process for Managing Conflict Between Teams
1. Define the Conflict Clearly
Describe the issue in observable and specific terms.
Clarify:
- What decision, contribution, or dependency is unresolved
- Which teams or stakeholders are involved
- What commitments or responsibilities are affected
- What evidence is available
- What remains uncertain
- What happens if the issue is not resolved
Avoid broad descriptions such as “the teams do not collaborate” unless the specific behaviors and consequences can be identified.
2. Identify Decision Authority
Determine who can resolve the issue.
The relevant roles may include:
- The person recommending an option
- Specialists providing advice
- Leaders controlling resources
- Stakeholders affected by the decision
- The individual or governance body making the final decision
- The person responsible for escalation
A productive discussion cannot replace a formal decision when legitimate authority is required.
3. Prepare the Evidence
Collect information relevant to the issue without overwhelming participants with unnecessary detail.
Evidence may include:
- Resource availability
- Current commitments
- Customer or service implications
- Financial consequences
- Operational capacity
- Technical dependencies
- Risk and compliance requirements
- Deadlines and contractual obligations
- Previous decisions and documented commitments
Distinguish observed facts, estimates, assumptions, and interpretations.
4. Establish a Shared Decision Question
Teams may argue past one another because they are answering different questions.
Instead of debating whether one team is being cooperative, define the decision question:
- Which work should receive the limited specialist capacity?
- Which implementation sequence best balances service risk and delivery timing?
- Who is responsible for resolving the dependency?
- Which requirement is mandatory, and where is local adaptation possible?
A shared decision question gives the discussion a clearer purpose without requiring the teams to prefer the same option.
5. Invite Each Perspective
Give relevant participants an opportunity to explain their responsibilities, evidence, constraints, concerns, and proposed options.
Useful questions include:
- What outcome is your team responsible for protecting?
- Which consequence concerns you most?
- What evidence supports your position?
- What capacity or dependency affects your response?
- Which assumption do you think the other team is making?
- What information is missing?
- What would make an alternative workable?
Listening does not require agreement. It helps ensure that material information is understood before participants or leaders select a response.
Explore additional techniques in Active Listening at Work.
6. Make the Trade-Offs Visible
Interteam conflict often involves trade-offs among:
- Speed and operational stability
- Cost and capability
- Standardization and local requirements
- Short-term capacity and long-term value
- Customer commitments and delivery risk
- Innovation and regulatory obligations
For each realistic option, clarify:
- What the option achieves
- What the option gives up
- What evidence supports it
- What risks or assumptions remain
- Who would be affected
- What resources and actions it requires
Conflict management does not eliminate trade-offs. It makes them sufficiently clear for a responsible decision.
7. Select the Appropriate Influence Approach
Some conflict situations require clear direction, evidence, boundaries, or a formal decision. Others require stronger inquiry, listening, acknowledgment, consultation, or involvement.
The Positive Power & Influence® model provides a practical framework for balancing complementary Push and Pull behaviors:
- Push behaviors provide direction through expectations, recommendations, positions, evidence, and reasoning.
- Pull behaviors create understanding and participation through inquiry, listening, acknowledgment, and appropriate involvement.
Neither approach is inherently better. The appropriate balance depends on the issue, expertise, relationship, authority, urgency, and organizational context.
8. Make or Escalate the Decision
If the participants have the authority and information required, make and document the decision.
If the participants do not have the authority or information required, prepare the issue for escalation by summarizing:
- The decision required
- The options considered
- The evidence
- The trade-offs
- The areas of agreement and disagreement
- The recommendation
- The consequences of delay or inaction
Escalation is not automatically a failure of collaboration. Escalation can be the correct response when the issue exceeds the participants’ authority or involves an unresolved organizational priority.
9. Confirm Follow-Through
Close the discussion by documenting:
- The decision made
- Actions and owners
- Resources committed
- Dependencies
- Deadlines
- Communication responsibilities
- Unresolved issues
- Escalation routes
- Review points
Monitor whether commitments are completed and communicate promptly when conditions affect the agreement.
Emotional Intelligence During Interteam Conflict
Conflict can trigger frustration, defensiveness, urgency, or concern about status and credibility. Emotional intelligence can help leaders notice these reactions and prevent them from undermining a necessary discussion.
Self-Awareness
Recognize how assumptions, tone, frustration, or prior experiences may affect the way the issue is presented.
Self-Management
Pause before responding to challenge. Maintain clarity without allowing an immediate reaction to escalate the exchange.
Empathy
Make a genuine effort to understand the responsibilities, pressures, and concerns shaping another team’s position.
Empathy does not require agreement, concession, or avoidance of accountability.
Relationship Awareness
Consider how the current conversation and decision may affect continuing cooperation between the teams.
A productive relationship should support direct discussion of difficult issues rather than prevent it.
Read Emotional Intelligence in Difficult Conversations for a more detailed explanation.
Common Mistakes When Managing Conflict Between Teams
Assuming Bad Intent
Participants interpret a competing priority or constraint as evidence that another team is obstructive or unwilling to collaborate.
Beginning With Blame
The discussion opens with a judgment about what another team has done wrong instead of a clear description of the issue requiring resolution.
Using Only a Directive Approach
A leader communicates a solution without understanding relevant expertise, implementation conditions, or capacity constraints.
Using Only a Participative Approach
The leader invites extensive discussion but avoids stating a recommendation, clarifying authority, or making a necessary decision.
Focusing Only on the Relationship
Participants prioritize short-term harmony while leaving ownership, resources, performance, or decision issues unresolved.
Focusing Only on the Task
Participants pursue an immediate outcome without considering how the process may affect trust, information sharing, or future cooperation.
Seeking Consensus When a Decision Is Required
The discussion continues because participants expect universal agreement even though a responsible leader or governance body has authority to decide.
Ending Without Clear Ownership
The meeting ends with apparent agreement but no specific actions, owners, deadlines, or review points.
A Cross-Functional Conflict Example
A marketing team plans a product campaign tied to a fixed external date. Operations identifies supply constraints that could affect customer fulfillment. Finance is concerned about additional inventory exposure.
The initial discussion becomes positional:
- Marketing argues that the launch date cannot move.
- Operations argues that the required volume cannot be supported.
- Finance argues that additional inventory cannot be justified.
The leader reframes the issue as a shared decision question: which launch option offers an acceptable balance among customer commitments, operational capacity, financial exposure, and market timing?
The teams compare three options:
- A full launch on the original date
- A phased launch by customer segment
- A delayed full launch after additional supply is available
Each option is assessed using consistent criteria. The teams do not develop the same preference, but the relevant leader has sufficient information to make a documented decision.
The decision includes actions, owners, capacity assumptions, customer communication responsibilities, and review points.
The conflict was not solved by encouraging the teams to agree. The conflict was managed by clarifying the decision, making trade-offs visible, involving relevant expertise, and assigning follow-through.
When Conflict Requires More Than a Conversation
Communication and influence skills cannot resolve every interteam conflict.
Additional organizational action may be necessary when the conflict results from:
- Contradictory incentives or performance measures
- Persistent resource shortages
- Unclear or overlapping mandates
- Weak governance
- Incompatible policies or regulatory requirements
- Structural dependencies without ownership
- Repeated failure to honor commitments
- Harassment, discrimination, retaliation, or other misconduct
- Legal, safety, ethical, or compliance concerns
Issues involving misconduct, legal obligations, safety, or protected workplace rights require appropriate formal procedures and qualified support. These issues should not be treated only as communication problems.
Leaders should also avoid using facilitated dialogue to transfer responsibility for a systemic problem onto individual employees.
How to Evaluate Conflict Management
Conflict management should not be evaluated only by whether participants report feeling satisfied or whether disagreement becomes less visible.
Depending on the issue, useful indicators may include:
- Clarity of the decision question
- Accuracy of the evidence considered
- Visibility of trade-offs
- Clarity of authority and decision rights
- Completion of agreed actions
- Resolution of defined dependencies
- Closure of questions and feedback loops
- Appropriate escalation of unresolved issues
- Manager or stakeholder feedback on specific behaviors
- Continued ability of the teams to cooperate on relevant work
Less visible conflict is not automatically evidence of improvement. Participants may simply have stopped raising concerns. Measures should be interpreted in the context of the issue and the desired organizational outcome.
Develop Difficult Conversation Skills Through Practice
Managing conflict between teams requires more than understanding a framework. Leaders and professionals need opportunities to practice important conversations and receive feedback on observable behavior.
Effective development should help participants:
- Describe the issue without blame or assumptions about intent
- Clarify the decision or contribution required
- Present relevant evidence
- Ask purposeful questions
- Listen during disagreement or defensiveness
- Acknowledge concerns without making unintended commitments
- Make trade-offs and decision boundaries visible
- Balance direction with participation
- Confirm responsibilities and follow-through
- Recognize when formal escalation or another process is required
Organizations seeking structured, behavior-based development can explore APRENDA’s Influence Skills Training, which connects inquiry, listening, acknowledgment, reasoning, clear direction, and stakeholder influence with current workplace conversations and cross-functional challenges.
Frequently Asked Questions
What Causes Conflict Between Teams?
Interteam conflict may result from competing priorities, unclear decision rights, resource constraints, different success measures, unowned dependencies, incomplete information, or unresolved previous issues.
Is Conflict Between Teams Always Harmful?
No. Disagreement can reveal different evidence, risks, responsibilities, and implementation concerns. Conflict becomes more damaging when it is personalized, avoided, poorly governed, or left without a decision and follow-through.
How Should Leaders Start an Interteam Conflict Conversation?
Leaders should define the specific issue, clarify the decision or contribution required, identify relevant evidence and authority, and invite each team to explain its responsibilities, constraints, and concerns.
What If the Teams Cannot Agree?
Universal agreement may not be necessary. If the teams cannot resolve the issue within their authority, the teams should document the options, evidence, trade-offs, recommendation, and consequences for escalation to the appropriate decision-maker.
Can Influence Skills Resolve All Team Conflict?
No. Influence skills can support clearer communication and more responsible decisions, but structural conflict may also require changes to governance, incentives, resources, processes, roles, or formal authority.
Conclusion: Resolve the Issue Without Personalizing the Conflict
Conflict between teams is not always a sign of dysfunction. Different functions may hold legitimate responsibilities, evidence, constraints, and priorities.
Leaders can manage interteam conflict more responsibly by defining the issue clearly, identifying decision authority, listening to relevant perspectives, making trade-offs visible, and confirming explicit decisions and follow-through.
The goal is not to create universal agreement or eliminate organizational tension. The goal is to prevent legitimate differences from becoming personal, hidden, or operationally unresolved.




