Patrick Lencioni calls "fear of conflict" one of the five dysfunctions of a team. Teams that avoid conflicts make worse decisions – because nobody speaks uncomfortable truths.
The problem isn't conflicts. The problem is handling them wrong.
Understanding Conflicts
Conflict Types
TASK CONFLICTS:
Different opinions about WHAT should be done
- "We should build feature A" vs. "Feature B is more important"
- Can be productive when constructive
PROCESS CONFLICTS:
Different opinions about HOW something should be done
- "We need more planning" vs. "We should just start"
- Often solvable through clear agreements
RELATIONSHIP CONFLICTS:
Personal tensions between team members
- "I can't work with person X"
- Always destructive, must be addressed
Productive vs. Destructive Conflicts
PRODUCTIVE CONFLICT:
- Focus on issue, not person
- Goal: Find best solution
- Respectful interaction
- All perspectives are heard
- Ends with decision and commitment
DESTRUCTIVE CONFLICT:
- Focus on person, not issue
- Goal: "Winning"
- Personal attacks
- Voices are suppressed
- Ends with resentment and sabotage
Why Teams Avoid Conflicts
The Causes
FALSE HARMONY:
"We're all friends here"
→ Uncomfortable truths remain unsaid
FEAR OF CONSEQUENCES:
"If I disagree, it hurts my career"
→ Self-censorship
LACK OF TRUST:
"I don't know how others will react"
→ Safety in silence
BAD EXPERIENCES:
"Last time it escalated"
→ Avoidance as protection mechanism
The Costs of Conflict Avoidance
BAD DECISIONS:
- Important perspectives missing
- "Groupthink" dominates
- Obvious problems are ignored
PASSIVE AGGRESSION:
- Silent resistance
- Sabotage of decisions
- Gossip instead of direct communication
UNRESOLVED PROBLEMS:
- Problems don't disappear by ignoring
- They grow bigger
- Explosion instead of constructive solution
The Conflict Continuum
NO CONFLICTS PRODUCTIVE DESTRUCTIVE
CONFLICTS CONFLICTS
│ │ │
▼ ▼ ▼
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ • Groupthink│ │ • Open │ │ • Personal │
│ • Passivity │ │ discourse │ │ attacks │
│ • Mediocrity│ │ • Creative │ │ • Hurt │
│ │ │ tension │ │ feelings │
│ • Artificial│ │ • Best │ │ • Sabotage │
│ harmony │ │ ideas │ │ • Distrust │
└─────────────┘ └─────────────┘ └─────────────┘
←─── GOAL: BE HERE ───→
Enabling Productive Conflicts
Build Foundations
PSYCHOLOGICAL SAFETY:
- Admitting mistakes is safe
- Dissent is welcome
- Asking questions is encouraged
- No punishment for disagreement
CLEAR RULES:
- How do we discuss?
- What is "fair game," what isn't?
- How do we make decisions?
- How do we handle dissent after decisions?
TRUST:
- Shared goals
- Assuming good intentions
- Personal relationships
Techniques for Productive Conflicts
DISAGREE AND COMMIT:
1. All opinions are heard
2. Decision is made
3. Everyone commits to execution
4. No "I told you so" later
DEVIL'S ADVOCATE:
- Rotating role
- MUST bring counter-arguments
- Legitimizes dissent
FIST OF FIVE:
For decisions: Everyone shows simultaneously
5 fingers = Full agreement
1 finger = Strong concerns
→ Visible diversity of opinion
Leading Conflicts Constructively
Structuring the Conversation
STEP 1: OBSERVATION (Facts)
"I observed that..."
- No interpretation
- No judgment
- Concrete and specific
STEP 2: IMPACT (on me/team)
"This results in..."
- Describe effects
- Don't accuse
- Stay factual
STEP 3: NEED (what I need)
"I need..."
- Formulate clearly
- Don't demand
- Provide reasons
STEP 4: REQUEST (concrete wish)
"Would you be willing to...?"
- Concrete and actionable
- Formulated as question
- Negotiable
Choosing Language Consciously
INSTEAD OF SAY
─────────────────────────────────────────────────
"You always..." "I've noticed that..."
"That's wrong" "I see it differently because..."
"That never works" "My concerns are..."
"You don't understand" "Let me explain why..."
"You decided without..." "I would have liked..."
Active Listening
MIRRORING:
"If I understand you correctly, you're saying..."
PROBING:
"Can you tell me more about that?"
"What do you specifically mean by...?"
VALIDATING:
"I understand that's frustrating"
"That's an important point"
SUMMARIZING:
"So your main concern is...?"
Specific Conflict Situations
Technical Disagreements
SCENARIO:
Team A wants microservices, Team B wants monolith
DESTRUCTIVE:
"Microservices are modern, monolith is outdated"
→ Judgment instead of arguments
CONSTRUCTIVE:
1. Define criteria (together!)
- Scalability
- Development speed
- Team expertise
- Maintainability
2. Test options against criteria
3. Make trade-offs transparent
4. Make decision
5. Document why
Priority Conflicts
SCENARIO:
Engineering wants to reduce tech debt,
Product wants features
DESTRUCTIVE:
"Product doesn't understand code quality"
"Engineering is too slow"
CONSTRUCTIVE:
1. Shared understanding:
"What is the company's goal?"
2. Quantify trade-offs:
"Tech debt costs us X hours/week"
3. Joint solution:
"20% of capacity for tech debt"
4. Plan review:
"We'll evaluate in 3 months"
Personal Tensions
SCENARIO:
Two team members can't work together
STEPS:
1. Individual conversations
- What exactly is the problem?
- What is your part?
- What do you need to move forward?
2. Joint conversation (if both ready)
- Moderated
- Focused on future
- Concrete agreements
3. Follow-up
- Check regularly
- Acknowledge progress
- Escalate if needed
Leadership Role in Conflicts
What Managers Should Do
ENCOURAGE CONFLICTS:
"I want to hear all perspectives"
"Who sees this differently?"
"What could go wrong?"
MODEL:
- Disagree productively yourself
- Change your mind when convinced
- Admit mistakes
MODERATE:
- Intervene when escalating
- Point to rules
- Focus on the issue
DON'T:
- Suppress conflicts
- Take sides (without reason)
- Reward conflict avoidance
When to Intervene
INTERVENE WHEN:
- Personal attacks
- Voices are suppressed
- Discussion goes in circles
- Disrespectfulness
- Someone is visibly hurt
DON'T INTERVENE WHEN:
- Lively but respectful debate
- Uncomfortable but important points
- Different opinions
- Productive tension
Conflict Prevention
Establish Team Norms
DISCUSSION NORMS:
□ We attack ideas, not people
□ We listen to understand, not to respond
□ We raise concerns early
□ We commit to decisions
□ We give feedback directly, not behind backs
DECISION NORMS:
□ Who decides what?
□ How are stakeholders involved?
□ What happens with dissent?
□ How do we document?
Regular Check-ins
RETROSPECTIVES:
- How is collaboration going?
- Are there unspoken tensions?
- What can we improve?
1:1s:
- Are there conflicts you're bringing up?
- Do you feel heard?
- Where do you need support?
TEAM HEALTH CHECKS:
- Anonymous surveys
- Regular (monthly/quarterly)
- Discuss results
Toolbox
The Conflict Checklist
BEFORE THE CONVERSATION:
□ What exactly is the conflict?
□ What is my part?
□ What is my goal?
□ What are my facts vs. interpretations?
□ Am I in the right state of mind?
DURING THE CONVERSATION:
□ Use I-statements
□ Separate facts from opinions
□ Listen actively
□ Take breaks if needed
□ Work toward solution
AFTER THE CONVERSATION:
□ Document agreements
□ Plan follow-up
□ Get support if needed
Escalation Paths
LEVEL 1: DIRECT
Those involved resolve it themselves
LEVEL 2: MODERATED
Neutral third party moderates
LEVEL 3: MEDIATION
Formal mediation with process
LEVEL 4: MANAGEMENT
Manager decides
LEVEL 5: HR
For serious cases
Conclusion: Conflicts as Opportunity
Teams that can argue productively are stronger than teams that avoid conflicts.
Core Principles:
- Conflicts are normal: They're part of collaboration
- Type of conflict matters: Task conflicts yes, relationship conflicts no
- Psychological safety: Foundation for productive conflicts
- Structure helps: Clear rules and processes
- Leadership models: Managers must demonstrate productive conflict
The uncomfortable truth:
If nobody in your team ever disagrees, that's not a sign of harmony – it's a sign of fear. And fear prevents the best ideas.
Want to understand how to build psychological safety? Our guide on Error Culture in Companies shows how to create an environment where people can be open.
