Leadership

Managing Conflicts

Conflict on a team isn't a bug. It's a feature -- if you handle it well. Some of the best technical decisions I've seen came from two engineers who disagr...

14 Oct 2023

Managing Conflicts

Conflict on a team isn't a bug. It's a feature -- if you handle it well. Some of the best technical decisions I've seen came from two engineers who disagreed sharply, worked through it, and landed on a better solution than either proposed alone.

The problem isn't conflict. The problem is unmanaged conflict.

Create space for disagreement

Your first job is building an environment where people feel safe raising issues. If your team only agrees in meetings and complains in DMs, you have a communication problem, not a harmony problem.

Ask direct questions. Listen without interrupting. Follow up on what you hear.

Let them solve it first

Not every conflict needs you. In fact, most shouldn't involve you at all. Give people the chance to work it out between themselves. You're their lead, not their referee.

Step in only when they can't resolve it, or when the conflict is affecting the team.

When you do step in, move fast

Unresolved conflict spreads. Two people arguing becomes a team divided. If you see it festering, don't wait. Address it before it poisons the broader culture.

How I handle it

Listen to both sides separately. Don't start with assumptions. Don't rely on what you've heard from others. Sit down with each person and ask for their perspective.

Find the real issue. By the time conflict reaches you, emotions are running high. The original disagreement is often buried under frustration and defensiveness. Slow things down. Ask clarifying questions until you get to the root cause.

Focus on the problem, not the people. "Your approach to the API design creates coupling issues" is productive. "You always make bad decisions" is destructive. Keep the conversation about the work.

Find a resolution both can live with. They don't need to be friends. They need to work together effectively. Sometimes that means a compromise. Sometimes it means a decision where one person doesn't get their way -- and you explain why.

The bigger picture

A team with zero conflict isn't a healthy team. It's a team where people are afraid to speak up. A team with constant conflict isn't healthy either -- something structural is broken.

The goal is productive tension: people who care enough to disagree, trust each other enough to be direct, and respect the outcome enough to commit.