Conflict Management

Understanding the concept

Conflict is not one phenomenon. People may disagree about the task, the process for completing it or their relationship. A productive technical disagreement can become personal when motives are questioned or responsibilities remain unclear.

Not all conflict is harmful: task conflict about ideas can improve decisions, while relationship and process conflict tend to damage trust and coordination. Choosing among competing, avoiding, accommodating, compromising, and collaborating styles should depend on the stakes, time pressure, and relationship importance involved.

Competing, avoiding, accommodating, compromising and collaborating describe different ways of responding to conflict. Their usefulness depends on urgency, importance, power and the relationship. Collaboration seeks to understand interests and develop a workable joint solution, but requires time and good faith. Avoidance may create space for preparation or may allow an urgent issue to worsen. The mode should be chosen deliberately rather than treated as a permanent personality trait.

Core components and theoretical lenses

Use the following distinctions to unpack the chapter's central idea. Each identifies a different aspect of the problem; their relationships matter as much as the labels themselves.

1. 01

   Task conflict vs relationship conflict vs process conflict

2. 02

   Conflict escalation dynamics

3. 03

   Five conflict-handling styles (Thomas-Kilmann)

4. 04

   Interest-based vs position-based framing

5. 05

   Cross-functional interdependence

Conceptual constructs

A construct names an idea used to interpret behaviour. It is not directly interchangeable with a survey score or a single incident. In this chapter, the constructs below organize the diagnosis; examine how they could explain the observations before deciding what to change.

• Task/relationship/process conflict
• Conflict-handling styles
• Interdependence
• Trust (related)
• Distributive vs integrative framing (related)

Observable and measurable indicators

Indicators connect an abstract explanation to something that can be observed. Check the operational definition, reporting period and comparison group. A survey average can conceal differences between teams, and an administrative record can reflect willingness to report as well as underlying behaviour.

• Number of escalations to senior management per quarter
• On-time delivery rate for cross-functional commitments
• Employee survey items on cross-department collaboration quality
• Frequency of missed handoffs between production and marketing
• Time spent in dispute-resolution meetings vs productive planning

Reading the case evidence

Separate what the case reports from what you infer. A figure can establish the scale of a problem without establishing its cause. Note what information is absent and how that gap affects your confidence in a recommendation.

Decision alternatives and trade-offs

Alternatives represent different priorities and assumptions. The advantages and limitations below are the existing module's analytical prompts. Compare them against the same evidence rather than choosing first and finding a theory afterward.

Evidence-based discussion

In the production–marketing dispute, translate accusations into capacity, quality and customer commitments. Compare alternatives by whether they address the source of disagreement or only quiet the participants. Agree on the information needed for promises and the authority to accept exceptions. Follow outcomes across both departments; an apparent victory for one unit may simply transfer costs and conflict to another.

Theory-linked interpretation from the module

Distinguish task conflict (real capacity-demand mismatch, potentially productive if resolved with data) from relationship conflict (personal blame, corrosive to trust) and process conflict (disagreement over how sign-offs should work). Use the five conflict-handling styles to evaluate whether competing, compromising, or collaborating fits the time pressure and relationship stakes involved.

Your managerial judgement

Given the one-week deadline, should the COO prioritize a fast imposed compromise or invest time in collaborative problem-solving, and how should the underlying relationship conflict be addressed either way?

Write a recommendation that identifies a preferred alternative, uses the reported evidence, acknowledges uncertainty and specifies a review point. Another choice can be defensible when its assumptions and trade-offs are made explicit.

Possible consequences

The module offers the following projections for discussion. They depend on implementation and context; they are not guaranteed effects or verified forecasts.

• Short-term: an imposed compromise meets the deadline but may not resolve the trust breakdown
• Short-term: a collaborative workshop needs facilitation skill to avoid reigniting blame
• Long-term: unresolved relationship conflict between the two team leads will recur in future launches
• Long-term: a durable sign-off protocol can prevent repeat stockouts across future product launches
• Long-term: how this is resolved affects the COO's credibility as a fair, capable conflict arbiter

Reflection questions

1. How can you tell the difference between task conflict and relationship conflict in this dispute?
2. Why might resolving the immediate volume number not be enough to fix the relationship between Neha and Rakesh?
3. Which conflict-handling style would you personally default to under a one-week deadline, and what would it cost?
4. How does repeated stockout history change the trust dynamic between production and marketing?

Practice: Know → Analyse → Decide

These are the original module questions. Reading or printing this textbook does not change quiz scores, completion or certificate eligibility.