By Fatskills Exam Guides Team — the exam nerds behind 28,500+ quizzes and 2.1M practice questions across 500+ global exams.
Conflict management styles describe how individuals respond to disagreements in organizations. The Thomas-Kilmann Conflict Mode Instrument (TKI) identifies five styles—Competing, Collaborating, Compromising, Avoiding, and Accommodating—each with trade-offs in assertiveness (pursuing one’s own goals) and cooperativeness (addressing others’ concerns). Effective managers adapt their style to the situation, balancing short-term resolution with long-term relationships. Example: Netflix’s culture of "radical candor" encourages collaborating (high assertiveness + high cooperation) to resolve creative disputes, while avoiding is used for low-stakes issues to preserve psychological safety.
Accommodating (Teddy Bear): Low assertiveness, high cooperation (e.g., a manager yielding to a star employee’s demands to retain talent). Implication: No style is universally "best"—match to context (e.g., competing for quick decisions, collaborating for complex problems).
Dual Concern Theory (Pruitt & Rubin): Conflict behavior reflects two concerns: self-interest and other’s outcomes. High self/low other = competing; high both = collaborating. Implication: Assess stakeholders’ power and relationship importance before choosing a style.
Conflict Escalation Model (Glasl): Conflicts escalate through 9 stages (e.g., from "hardening" to "together into the abyss"). Early intervention prevents destructive outcomes. Implication: Use collaborating or compromising early; competing only when necessary (e.g., Amazon’s "disagree and commit" rule for high-stakes decisions).
Interest-Based Relational (IBR) Approach: Focus on underlying interests (needs) vs. positions (demands). Example: Two teams arguing over budget (position) may share an interest in project success. Implication: Collaborating works best when interests are uncovered (e.g., Patagonia’s environmental disputes resolved by aligning on sustainability goals).
Social Exchange Theory (Blau): Conflict styles reflect perceived costs/benefits of outcomes. Example: A manager accommodates a high-performer to avoid turnover costs. Implication: Adjust style based on power dynamics (e.g., competing with a weak opponent, accommodating with a powerful ally).
Example: A deadline-driven project dispute (high stakes) vs. a personality clash (low stakes).
Assess Stakeholder Needs
Example: A merger negotiation (high stakes + high relationship) calls for collaborating.
Choose the Style
Moderate stakes + time pressure-Compromise (e.g., splitting a bonus pool).
Implement & Monitor
For avoiding: Set a follow-up (e.g., "Let’s revisit this next week when emotions cool").
Evaluate Outcomes
Misconception: "Collaborating is always the best style." Correction: Collaborating is time-consuming and ineffective for trivial issues (e.g., arguing over office thermostat settings). Use it for high-stakes, complex problems (e.g., Netflix’s content strategy debates).
Misconception: "Avoiding conflict means you’re weak." Correction: Avoiding is strategic when the issue is minor, emotions are high, or the other party is more powerful (e.g., a junior employee avoiding a dispute with their CEO over a small policy).
Misconception: "Compromising means everyone wins." Correction: Compromising often leaves both parties unsatisfied (e.g., splitting a budget 50/50 when one team needs 70%). It’s a short-term fix, not a solution.
Misconception: "Accommodating is passive." Correction: Accommodating can be proactive (e.g., a manager yielding to a team’s preferred work-from-home policy to boost morale). It’s about prioritizing relationships over outcomes.
Misconception: "Competing is aggressive and unprofessional." Correction: Competing is necessary for urgent, high-stakes decisions (e.g., a hospital administrator overriding a doctor’s preference to save a patient’s life).
Answer Framework:
Tricky Distinction: Collaborating vs. Compromising
Compromising = lose-lose (e.g., both teams giving up something to meet in the middle).
Case Interview Trap: "The manager should always mediate conflicts."
Correction: Sometimes avoiding or accommodating is better (e.g., a manager letting two peers resolve a minor dispute to build autonomy).
OB Exam Tip: Look for keywords in questions:
Scenario: A senior engineer and a product manager at a tech startup are clashing over a feature’s launch timeline. The engineer insists on delaying for quality, while the PM argues the market can’t wait. The CEO asks you to intervene. Question: Which conflict style should you recommend, and why?
Answer: Collaborating (high assertiveness + high cooperation). Explanation: The stakes are high (product success), and the relationship is critical (cross-functional trust). Use IBR to uncover interests (e.g., "What’s the worst-case scenario if we launch late?").
Join 4M+ learners. Unlock unlimited quizzes, wrong-answer tracking, flashcards + reminders, study guides, and 1-on-1 challenges.