Conflict Management & Team Dynamics: Types, Causes, Styles & Teamwork

TAKEAWAYS:

• Conflict is inevitable but can be constructive if managed via collaboration (win-win) or accommodation (yielding for harmony).
• Teams ≠ Groups: Teams have shared goals, interdependence, and accountability (e.g., Ncell’s customer support squad vs. a casual WhatsApp group).
• Tuckman’s 5 stages (Forming → Storming → Norming → Performing → Adjourning) explain why teams struggle midway—norming is critical for trust.
• Belbin’s team roles (e.g., Shaper, Monitor-Evaluator) help assign tasks based on personality (e.g., Daraz’s logistics team needs Completer-Finishers).
• Power distance in Nepali orgs (high in banks like Nabil, low in startups like Pathao) affects conflict styles—avoidance is common but harmful.
• Exam focus: Case analysis (e.g., TGSS e-commerce conflict) + comparison tables (conflict styles, team vs. group) + real-world ties (e.g., Kathmandu traffic as a conflict metaphor).

---

1. What Is Conflict? Types and Causes

Conflict arises when perceived incompatibilities exist between goals, values, or resources. It’s not inherently bad—functional conflict improves performance (e.g., debates in NEPSE boardrooms), while dysfunctional conflict harms morale (e.g., NTC’s internal turf wars).

Types of Conflict

Causes of Conflict

---

2. Conflict Management Styles (Thomas-Kilmann Model)

The Thomas-Kilmann Instrument (TKI) classifies 5 styles based on assertiveness (own concerns) vs. cooperativeness (others’ concerns). Use the right style for the situation:

• Forming: "Who’s in charge?" (e.g., new NTC project team).
• Storming: "Why isn’t my idea adopted?" (e.g., Daraz’s delivery partners vs. HQ).
• Norming: "We’ve got rules now!" (e.g., Ncell’s "no personal calls" policy).
• Performing: "We’re crushing goals!" (e.g., Pathao’s rider coordination).
• Adjourning: "What’s next?" (e.g., post-event cleanup at a Chaudhary Group expo).

REAL-WORLD TRACE: Kathmandu Traffic as a Conflict Metaphor

• Forming: Drivers ignore rules (no lanes, honking).
• Storming: Accidents → blame games (bike vs. bus).
• Norming: "Slow zones" emerge (e.g., Thapathali traffic police coordination).
• Performing: (Hypothetical) Smart traffic lights reduce gridlock.

---

4. Managing Conflict in Teams: Techniques and Tools

A. Problem-Solving (Collaboration)

1. Define the issue: "Sales vs. support teams argue over customer data access."
2. Generate solutions: Shared dashboard? Rotate responsibilities?
3. Evaluate: Pilot the dashboard for 2 weeks.
4. Implement: Train teams on the new system.

B. Smoothing (Accommodation)

• When: Harmony > task completion (e.g., during Dashain at a Nepali SME).
• How: "Let’s table this until after the festival."
• Risk: Suppresses real issues (e.g., unaddressed NTC corruption).

C. Forcing (Competing)

• When: Crises (e.g., Ncell’s network outage).
• How: "We’re switching to backup towers—no debate."
• Risk: Low morale if overused.

D. Compromising

• Example: NEPSE’s "split the difference" rule for share price disputes.

E. Avoiding

• When: Trivial conflicts (e.g., office printer jams).
• Risk: Escalates into bigger issues (e.g., NTC’s delayed projects).

---

5. Case Study: Conflict at The Giant Super Stores (TGSS)

Scenario: TGSS’s top management prioritizes profitability over customer service. Regional managers clash with customer support teams over refund policies.

Analysis Using TKI Styles

SOLUTION:

1. Train managers in TKI styles (workshop at TGSS HQ).
2. Implement a conflict escalation matrix:
   • Minor: Team lead mediates.
   • Major: Cross-functional committee (e.g., sales + support reps).
3. Incentivize collaboration: Reward teams that resolve conflicts internally.

---

6. Organizational Culture and Conflict

Nepal’s high-power-distance culture (Hofstede) affects conflict:

• Hierarchical orgs (e.g., Nabil Bank): Avoidance or forcing.
• Flat orgs (e.g., Pathao): Collaboration or compromising.

WORKED EXAMPLE: NTC’s Fiber Expansion Conflict

• Cause: Engineering team (technical) vs. finance team (budget cuts).
• Cultural Barrier: Engineers avoid confronting finance due to hierarchy.
• Fix:
  1. Cross-training: Finance staff learn basic telecom costs.
  2. Shared goal: "Expand fiber to 50% rural areas by 2025."
  3. Tool: SWOT analysis to prioritize low-cost regions.

---

7. Building High-Performing Teams

Belbin’s Team Roles in Action

TEAM-BUILDING TIPS:

• Diversity: Mix Plants (ideas) + Implementers (execution).
• Psychological safety: Encourage "pre-mortems" (e.g., "What could go wrong with this NTC project?").
• Tools: Slack for async updates, weekly "retro" meetings.

---

8. Conflict in Nepali Business Context

Challenges

1. Lack of conflict resolution training: Many managers default to avoidance.
2. Family-owned businesses: Emotional conflicts (e.g., Chaudhary Group succession).
3. Legal ambiguity: No strong labor laws for gig workers (e.g., Pathao drivers).

Success Stories

• Ncell: Uses collaborative style for network upgrades (e.g., joint Ncell-NTC towers).
• Daraz: Compromising with vendors on late fees during Dashain.
• Nabil Bank: Problem-solving for loan disputes via mediation committees.

---

In the Real World

1. eSewa’s Payment Disputes

   • Conflict: Users report failed transactions; eSewa’s customer service blames banks.
   • Style Used: Initially avoiding (blame-shifting), now collaborating (joint fraud task forces with Nabil Bank).
   • Outcome: Reduced disputes by 30% via shared databases.

2. Pathao’s Rider Conflicts

   • Conflict: Riders vs. dispatchers over route fairness.
   • Style Used: Compromising (dynamic fare adjustments) + technology (automated route suggestions).
   • Outcome: 20% higher rider retention.

3. NTC’s Infrastructure Projects

   • Conflict: Engineering vs. procurement teams over supplier contracts.
   • Style Used: Forcing (HQ mandates local suppliers) → led to corruption scandals.
   • Better Approach: Collaborate with suppliers via transparency portals (like NEPSE’s disclosure rules).

---

Exam Tip

1. Case Analysis (30% of marks):

   • Structure: Problem → Root Cause → Style Used → Better Approach.
   • Example: For TGSS, link avoidance to "low customer satisfaction scores" and suggest collaboration via "shared dashboards."

2. Comparison Tables (20% of marks):

   • Always include Nepali examples (e.g., Ncell vs. Pathao conflict styles).

3. Definitions + Applications (20%):

   • Team: "A group with interdependent goals (e.g., NEPSE’s audit team)."
   • Conflict: "Perceived incompatibility → functional (e.g., NTC’s innovation debates) or dysfunctional (e.g., Nabil Bank’s nepotism)."

4. Diagrams (15%):

   • Draw Tuckman’s stages or TKI grid in exams. Label with Nepali org examples.

5. Short Answers (15%):

   • Two differences between group and team:
     1. Accountability: Team = shared (e.g., Daraz’s delivery squad); Group = individual.
     2. Skills: Team = complementary (e.g., Belbin’s Shaper + Monitor).

---

PRO TIP: Memorize one Nepali company per style (e.g., Ncell = collaborating, NTC = forcing). Examiners love real-world ties!