How to resolve conflict in the workplace: steps and scripts managers can use

To resolve a workplace conflict, a manager acts early, hears each person separately, works out what the disagreement is really about, and then brings both people together to agree on what each will do differently. Most conflicts end there. The rest need HR, and the right employee relations case management software only helps if the manager has already documented what happened and when.

Employees are watching how managers handle it. In SHRM's 2024 Civility Index research, only 25% of workers in the United States said they believe managers effectively address acts of incivility, and 31% said respectful treatment is the norm where they work. The same research found that nearly two-thirds of workers agree incivility reduces productivity and 59% agree it hurts morale. Respect is under strain more broadly: Gallup reported in January 2025 that the share of U.S. employees who strongly agree they are treated with respect at work was back at its record low of 37%.

Researchers usually separate three kinds of conflict on a team:

• Task conflict: disagreement about the work itself, such as which vendor to choose, which feature ships first or what the data means.
• Process conflict: disagreement about how the work gets done, such as who owns what, who decides, deadlines and handoffs.
• Relationship conflict: friction between people, such as irritation, distrust, feeling disrespected or a clash of personal values.

The evidence is clearest on the last two. A 2012 meta-analysis of 116 studies covering 8,870 groups found stable negative relationships between relationship and process conflict and group outcomes, while the effects of task conflict were less straightforward. An earlier meta-analysis went further and found that task conflict also correlated negatively, not positively as predicted, with team performance and satisfaction on average, with less harm when task disagreement stayed separate from personal friction.

So the case for conflict is narrower than it is often made out to be. Arguing about the work is least risky when the debate stays about ideas. It turns costly when it spills into who is competent, who is respected and who is on whose side. A manager's job is less "encourage conflict" or "stop conflict" and more "keep disagreement about the work, and fix process and relationship problems fast".

Process conflict is often the easiest to remove because it comes from ambiguity rather than people. If two people keep clashing over handoffs, the fix may be a clear owner and a written decision, not a mediation. Our guide on how to improve team communication covers the routines that prevent much of it.

Myth 1: A healthy team has no conflict. Silence is not harmony. Teams that never disagree about the work may have stopped saying what they think. Look for disagreement that is about ideas, voiced openly and settled with a decision.

Myth 2: Debate is always good for performance. The research above does not support a blanket rule. On average, disagreement about the task was linked to lower, not higher, team performance, and it was least harmful when it stayed separate from personal friction, which is why de-escalation matters as much as candor.

Myth 3: Each person has one fixed conflict style. The co-author of the Thomas-Kilmann model writes that everyone is capable of using all five modes and that nobody can be characterized by a single style, although people lean on some modes out of temperament or practice. Treat a style as a habit you can change, for yourself and for your team.

Myth 4: Raising the issue will damage the relationship. People tend to overestimate the cost of a frank conversation. In experiments by Levine and Cohen, people expected honesty to be less pleasant and less connecting than it turned out to be, and listeners reacted less negatively than expected. The relationship usually suffers more from the conversation that never happens.

The steps work between two employees, between an employee and you, or between two teams. Suppose two senior engineers keep arguing in stand-ups about whether to delay a release to fix technical debt, and the rest of the team has gone quiet.

1. Step in early. Raise it within a few days of noticing the pattern, in private. "I've noticed the release discussions are getting tense, and I'd like to help sort it out before the next planning meeting."
2. Meet each person alone. Ask for specifics: what happened, when, and what they need. Listen without ruling. You are collecting facts and interests, not verdicts.
3. Name the conflict type. Here, the surface is task conflict (delay or ship). Underneath you may find process conflict (nobody knows who has the final say) and some relationship conflict (one feels the other dismisses his estimates in front of the team).
4. Meet together on interests. Set ground rules: one person speaks at a time, describe behavior rather than character, the goal is a plan rather than a winner. Then use the principle that the Harvard Negotiation Project made famous: separate relationship issues from substance, and deal with substance by focusing on interests, not positions. "Delay the release" is a position; "I don't want to spend next quarter on incidents" is an interest. Interests usually leave room for options neither person brought into the room.
5. Agree specific behaviors. Two or three actions that someone else could observe, each with an owner and a date. "Technical-debt items get a fixed share of every sprint, agreed at planning" is a decision; "communicate better" is not one. Settle the process gap too: who decides when the two disagree.
6. Follow up and document. Check in with each person after a week and after a month. Write down what was agreed and what changed (more on documentation below).

If you are part of the conflict yourself, steps 2 and 4 merge into one conversation, which is where the next two sections come in.

A tough discussion goes better when the hard thinking happens before it starts. Take ten minutes and fill in this prep sheet:

Then manage your own state, which is half the work. Pick a private, unhurried slot rather than the end of a bad day. If you notice anger or anxiety rising, name the topic to yourself, breathe and slow your speech before you answer. Calm is a skill you can practice; the guide on emotional intelligence in leadership covers how to read and regulate emotions in moments like this.

Use this five-part structure when you need to raise something uncomfortable with an employee, a peer or your own manager. Adapt the words; keep the order.

1. Open with purpose. "I'd like to talk about Tuesday's client call, because I think it affected how we work together and I'd like us to sort it out."
2. Share facts, then your interpretation. "When I presented the budget, you said twice that the numbers were 'not real.' I took that as a signal you don't trust my estimates. I may be missing something."
3. Ask, then listen until you can repeat it. "How did it look from your side?" Then paraphrase: "So the concern is that the client saw figures you had not reviewed. Did I get that right?"
4. Move from positions to interests. "What matters most to you here?" and "What would need to be true for you to be comfortable with how we present numbers?"
5. Agree and close. "So before client calls, I'll send you the figures 24 hours ahead and you'll raise doubts with me first. Let's check how it's going on the 20th."

Phrases that keep the conversation productive:

The Thomas-Kilmann model maps conflict behavior on two dimensions: assertiveness, how far you try to satisfy your own concerns, and cooperativeness, how far you try to satisfy the other person's. The five modes it defines each fit some situations and cost something in others.

If your default is avoiding, raise any repeated friction within a week. If it is competing, ask two questions before you state your view.

Sometimes the problem is not one incident but a relationship that has slowly soured: two colleagues who worked well for years and now talk only by email.

Signs to watch for:

• Communication shrinks to the formal minimum, or moves to channels with an audience.
• People route work around each other, or each asks you to rule on small points.
• Neutral events get read as hostile ("she copied my manager on purpose").

How to repair it:

1. Find the turning point. Ask each person, separately, when things changed. Often there is a specific event: a credit dispute, a reorganization, a promise not kept.
2. Address that event directly. Unspoken grievances keep reinterpreting the present. Bring the event into the joint conversation using the script above.
3. Reset the working agreement. Agree on how they'll communicate, who decides what, and how disagreements get raised before they build up.
4. Rebuild with small, visible wins. A shared short-term deliverable gives both people evidence that working together is possible again.
5. Accept the limits. A professional, reliable working relationship is a legitimate goal, even without the old warmth.

If one person's behavior is the consistent cause, such as public belittling or taking credit, treat it as a conduct or performance matter, not a mutual conflict. When that person is a leader, see our article on toxic leadership.

Managers can and should resolve ordinary disagreements. Some situations are not "conflicts" in that sense, and mediating them can cause harm.

The fourth row matters because of where the legal line sits. The EEOC says harassment based on protected characteristics becomes unlawful when enduring it becomes a condition of employment, or when it is severe or pervasive enough to create a work environment a reasonable person would find intimidating, hostile or abusive. A manager cannot judge that threshold in a hallway, which is why these cases go to HR.

The last row is about retaliation. Under EEOC guidance, it is unlawful to retaliate against employees for protected activity, which includes raising discrimination or harassment concerns with a supervisor and answering questions in an employer's harassment investigation. After someone raises a concern, check every schedule change, assignment or exclusion that affects them with HR first. Your company's policy and HR team set the exact process; this table is a starting point, not legal advice.

When a performance problem sits underneath the conflict, handle it as one. Our guide on how to address poor performance explains how to set expectations and follow through.

What to document, every time it might escalate:

• Date, time, place and who was present.
• What was said or done, in observable terms and in quotes where you can.
• What you did in response, and when.
• What each person agreed to, with dates.
• What happened at each follow-up.
• Where the record is kept: the system HR designates, not personal notes or a chat thread.

Write facts, not diagnoses. "Raised his voice and said 'this is a joke'" holds up; "was aggressive and unstable" does not.

• Waiting for it to blow over. Repeated friction rarely fades on its own; it moves to side channels.
• Joint meeting first. Bringing people together before hearing each one alone invites a replay of the argument in front of you.
• Ruling on who was right. Verdicts on the past settle little. Agreements about the future settle more.
• Vague agreements. "Be more respectful" gives nobody anything to do. Name behaviors.
• Mediating what is not a conflict. Harassment, threats and retaliation are not two-sided disagreements.
• No follow-up. An agreement nobody checks is a hope.

Resolution is a behavior change you can observe, not a handshake. Track a few signals:

• Recurrence: the same issue between the same people at 30 and 90 days. The goal is none.
• Time to first conversation: days from the first signal you noticed to your first private talk. Aim for under a week.
• Work signals: handoff delays, rework, meetings where one person stays silent, escalations to you for small decisions.
• Case data: for HR, the number of conflict-related cases per team per quarter and the time to close them, read for trends rather than single numbers.
• Pulse survey items: "I am treated with respect at work," "On my team, we can disagree about the work openly," and "Disagreements on my team get resolved fairly." Ask quarterly and compare teams.

Cadence: check in privately at one week and 30 days after any agreement, review team signals in your regular one-on-ones, and look at survey results each quarter. Gallup recommends weekly meaningful conversations between managers and team members to address disrespect, and notes that policies do not replace a manager who understands the person and the situation.

Software cannot hold the conversation, but it can make follow-through reliable. Employee relations case management tools give HR one access-controlled place for complaints, interview notes, evidence and outcomes, so escalated cases get handled consistently and repeat patterns by team become visible. Performance management tools keep one-on-one notes and agreed actions next to goals, which helps separate a performance problem from a personality clash. Internal communications tools reduce process conflict by making decisions, owners and priorities easy to find.

Keep the scale right. Logging every minor disagreement in a case system can make people feel investigated; ordinary conflicts belong in your one-on-one notes, and only escalated matters belong in an HR case file.