Unit III — Group Dynamics
21. Conflict Management
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.
- Task conflict vs relationship conflict vs process conflict
- Conflict escalation dynamics
- Five conflict-handling styles (Thomas-Kilmann)
- Interest-based vs position-based framing
- Cross-functional interdependence
- 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
Vantage Consumer Goods, a mid-size FMCG company launching a new snack brand, has its production and marketing teams locked in recurring disputes over delivery commitments. Marketing, led by Neha, commits to retailers for a festive-season launch based on aggressive volume targets, while production, led by Rakesh, insists current capacity supports only 70% of that volume without a costly overtime shift. Three prior launches have suffered stockouts after marketing over-promised, and Rakesh has started refusing to verbally confirm any numbers marketing quotes to clients without written sign-off, which marketing sees as obstructive and slow. The dispute has become personal, with each team blaming the other in leadership meetings rather than solving the volume problem jointly. The COO has one week before the retailer contract must be finalized and needs the teams to reach a workable commitment.
Marketing's targeted festive volume
100,000 units
Production's current confirmed capacity
70,000 units without overtime
Overtime shift cost premium
18% higher unit cost
Prior launches with stockouts
3 of last 4
Time to retailer contract deadline
1 week
Leadership meetings spent on blame rather than solutions
4 of last 5
ACollaborative problem-solving workshop with data-sharing
COO convenes a joint session where marketing shares real retailer demand data and production shares true capacity constraints, aiming for an integrative solution (e.g., phased volume commitment, overtime cost-sharing).
BCOO imposes a compromise volume commitment
The COO unilaterally sets the retailer commitment at 85,000 units, splitting the difference, and mandates both teams accept it to meet the deadline.
CFormalize a structured escalation and sign-off protocol
Institute a rule that all retailer volume commitments require written joint sign-off from marketing and production before communication to any client, with defined turnaround times.
ACollaborative problem-solving workshop with data-sharing
Strengths
- Targets the underlying task conflict (capacity vs demand) with shared facts, potentially expanding the pie
- Can reduce relationship conflict by refocusing on joint problem-solving instead of blame
Risks
- Requires time and willingness from both sides to be transparent, which may be low given existing distrust
- Risk of the session itself becoming another blame session without strong facilitation
BCOO imposes a compromise volume commitment
Strengths
- Fast, decisive, and meets the one-week deadline pressure
- Removes ambiguity by giving both teams a single number to work against
Risks
- A compromise dictated top-down does not resolve the underlying relationship conflict or distrust
- 85,000 units may still not be achievable without overtime, repeating the stockout pattern
CFormalize a structured escalation and sign-off protocol
Strengths
- Reduces process conflict by clarifying decision rights and sequencing
- Prevents future over-promising by requiring production's technical confirmation upfront
Risks
- Does not address current relationship conflict or urgent contract deadline directly
- Could slow down responsiveness to genuine market opportunities if applied too rigidly
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?
COO convenes a joint session where marketing shares real retailer demand data and production shares true capacity constraints, aiming for an integrative solution (e.g., phased volume commitment, overtime cost-sharing).
Strengths: Targets the underlying task conflict (capacity vs demand) with shared facts, potentially expanding the pie; Can reduce relationship conflict by refocusing on joint problem-solving instead of blame. Risks: Requires time and willingness from both sides to be transparent, which may be low given existing distrust; Risk of the session itself becoming another blame session without strong facilitation.
The COO unilaterally sets the retailer commitment at 85,000 units, splitting the difference, and mandates both teams accept it to meet the deadline.
Strengths: Fast, decisive, and meets the one-week deadline pressure; Removes ambiguity by giving both teams a single number to work against. Risks: A compromise dictated top-down does not resolve the underlying relationship conflict or distrust; 85,000 units may still not be achievable without overtime, repeating the stockout pattern.
Institute a rule that all retailer volume commitments require written joint sign-off from marketing and production before communication to any client, with defined turnaround times.
Strengths: Reduces process conflict by clarifying decision rights and sequencing; Prevents future over-promising by requiring production's technical confirmation upfront. Risks: Does not address current relationship conflict or urgent contract deadline directly; Could slow down responsiveness to genuine market opportunities if applied too rigidly.
Set the weight of each criterion (1–5), then score every alternative (1–5). The matrix is a thinking aid, not a verdict.
| Criterion | Weight | A | B | C |
|---|---|---|---|---|
| Behavioural impact | ||||
| Employee acceptance | ||||
| Feasibility | ||||
| Cost (higher = more affordable) | ||||
| Risk containment | ||||
| Long-term sustainability |
With your current weights, alternative A scores highest. A matrix only reflects the weights you chose. Evidence, ethics, feasibility and the people affected still belong in your judgement — you decide.
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.
- 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
- How can you tell the difference between task conflict and relationship conflict in this dispute?
- Why might resolving the immediate volume number not be enough to fix the relationship between Neha and Rakesh?
- Which conflict-handling style would you personally default to under a one-week deadline, and what would it cost?
- How does repeated stockout history change the trust dynamic between production and marketing?
Task conflict differs from relationship conflict primarily in that task conflict:
What evidence indicates the Vantage dispute has moved from task conflict into relationship conflict?
Which approach best addresses both the immediate deadline and the recurring root cause of stockouts?