Conflict Management: How to Handle Disagreements at Work

1What Is Conflict Management?

Conflict management is the practice of identifying disagreements between people and resolving them constructively, so the relationship and the work both come out intact, rather than letting conflict fester or explode.

It does not mean eliminating disagreement, which is a normal part of any team; it means having a repeatable way to work through disagreement productively.

2Five Conflict Styles

Most people default to one of five recognizable styles when a disagreement arises, and each style fits some situations better than others.

• Avoiding: sidestepping the disagreement entirely; useful for minor issues, harmful for important ones left unresolved.
• Accommodating: giving in to preserve the relationship; useful occasionally, costly if it becomes a pattern.
• Competing: pushing your position regardless of the other side; useful in true emergencies, damaging otherwise.
• Compromising: both sides give up something to reach a middle ground quickly.
• Collaborating: working together to find a solution that fully satisfies both sides' underlying interests.

3A Practical Resolution Process

A useful resolution process starts by separating the person from the problem: the disagreement is about a decision or approach, not a judgment of someone's worth.

From there, each side states their underlying interest, not just their stated position, since two people can have compatible interests even when their initial positions seem opposed.

• Separate the person from the problem.
• State each side's underlying interest, not just their initial position.
• Generate multiple possible options before evaluating any of them.
• Agree on the option that best serves both interests, or the closest available compromise.
• Follow up afterward to confirm the resolution is actually working.

4Conflict in Technical Teams

Technical teams face conflict regularly, often around code review disagreements, competing architecture opinions, or conflicting priorities between teams sharing a codebase.

Because these disagreements are usually about substance, not personality, they respond especially well to a collaborating approach: focusing on what each side is optimizing for, such as speed versus maintainability, often reveals a solution that satisfies both.

5When Conflict Is Healthy

Disagreement itself is not the problem; a team with zero visible conflict is often one where people are avoiding hard conversations rather than one that is functioning smoothly.

Healthy conflict focuses on ideas and outcomes, stays respectful, and ends with a decision everyone can support, even if it was not their first choice.

6Practicing Conflict Management

Conflict management is a learnable skill, not a fixed personality trait. Practicing it in low-stakes disagreements, such as a minor process disagreement, builds the habit for when higher-stakes conflict arises.

Noticing your own default style is a useful first step, since awareness of a habitual pattern is what makes it possible to choose a different, more suitable approach in a given situation.

7Next Steps

Conflict management means resolving disagreements constructively through a repeatable process, not avoiding or dominating them.

Addressing disagreements early, while they are still small, is consistently easier than waiting until they have hardened into a lasting pattern on a team.