Handle conflict between employees with a structured, neutral process focused on behavior rather than blame: screen for serious misconduct, hear each person separately, identify the root cause, agree on specific actions, then document the agreement and follow up. Most ordinary disagreements need two or three conversations spread over a couple of weeks.
The hard part is not the method. It is that most managers delay, and the delay is usually fear rather than indifference. Anyone who has had to learn how to handle conflict between employees under deadline pressure knows the feeling. Nobody wants to be the person who made it worse, so the conversation slips from one month to the next while the tension hardens into something quieter and worse.
That pattern shows up constantly in manager forums. Threads on r/AskHR and Workplace Stack Exchange return to the same few worries: taking sides by accident, being blamed months later for a bad outcome, and not knowing whether a disagreement has quietly turned into harassment. Answering those three worries is most of the job.
What follows is the order things have to happen in, with the scripts and the written plan included so nothing depends on you being articulate under pressure. This is how to handle conflict between employees whether the two sit on the same team, whether it is a cross-department fight over who owns a project, and even in the harder version where one of the two reports to you.
Table of Contents
- What You Need
- How to Handle Conflict Between Employees Step by Step
- Common Mistakes
- Frequently Asked Questions
- Should a manager mediate conflict between two employees?
- How should a manager document an employee conflict?
- What if employees continue arguing after an agreement?
- How do managers prevent retaliation after a workplace complaint?
- When can employees resolve conflict without a manager?
- How do you separate personal conflict from an employment-law issue?
What You Need
Gather five things before you speak to anyone. Missing one of them is how well-intentioned conversations turn unfair.
- A private room. A conference room with a glass wall is not private. If you cannot get one, two separate rooms and two separate conversations is the fallback.
- The relevant paperwork. Job descriptions for both people, any prior feedback you have given, performance notes, and the section of the handbook or policy on conduct, bullying, and grievance.
- Both accounts of the events. Dates, times, messages, and meetings. Read them before you form a view, not after.
- A note-taking method that suits your organization. A company system, a locked file, or a dated document kept per your records rules. Know who is allowed to see it.
- A named escalation contact. Your HR partner, and the number for security or after-hours support if the situation changes.
Also check whether the two people share other work. If a client, a new hire, or a shift roster depends on them cooperating, that is part of the impact you are managing even though nobody said so.
One thing you do not need is the history of every past annoyance. Managers often arrive with two years of accumulated grievances, which turns a solvable problem into a trial.
How to Handle Conflict Between Employees Step by Step
Seven stages, in this order. Skipping ahead is what produces the recurring messes I have seen: a joint meeting convened before either account has been heard, or an apology demanded before the underlying workload problem was ever named.
1. Receive the Complaint Without Taking Sides
Take the report seriously, and do not react to it. Say something close to this: “Thank you for telling me. I want to understand this properly, so I will speak with each of you separately before deciding anything.”
That sentence does real work. It tells the person raising it that the complaint will not disappear, and it tells them you are not going to hold a tribunal in the next ten minutes.
Then listen without interrupting, ask open questions, and paraphrase what you hear back. “So the deadline moved twice and the second move was not communicated. Have I got that right?”
Avoid deciding guilt, however obvious it feels. The manager who says “that clearly wasn’t acceptable” in the first meeting has now told the other employee that the outcome is decided.
You will know this step worked when the person has given you a specific account rather than a character description, and can tell you what outcome they actually want.
2. Check Whether Anyone Needs Immediate Support
Some conflicts are not yours to resolve at all. Pause the normal process if the report includes threats, physical violence, discrimination, harassment, serious distress, or a real health and safety risk.
The distinctions that matter: a personality clash is a relationship problem; repeated unwanted conduct of a sexual or racial nature is a conduct problem; anything involving safety is an emergency. Conflating the three is how a manager ends up mediating a harassment complaint and destroying the evidence trail along with it.
Route those cases to HR, to workplace security, or to emergency services when there is immediate danger. If your organization offers an Employee Assistance Program, mention it early; it is confidential and it gets people support without putting anything on a record.
For the boundary cases, the test is simple. Would you be comfortable if this employee’s manager were the one deciding? If not, it belongs in the formal process. Our guide to how to handle workplace bullying covers the conduct side in more detail.
Say clearly what happens next and when. “I am going to speak with both of you separately this week, and I will come back to you by Friday.” Managers who leave people without a date get chased, and chasing is what produces the two-sided pressure you were trying to avoid.
3. Meet With Each Employee Separately
Run one conversation per person, same questions for both, roughly twenty minutes each. Write the questions down in advance so neither gets a more sympathetic interview than the other.
Useful openings: “Walk me through what happened, from your side.” “What did you need at the time?” “What have you already tried?” “What would a good outcome look like for you?”
Then push for observable detail. “He is difficult” is useless. “He replied to my request in a group channel in front of eleven people and told me to reread the brief” is workable.
Establish the shared goal too. Nearly everyone involved wants the same project to ship and wants their reputation intact, and naming that out loud gives you something to build on.
Do not promise secrecy. Say what you can hold confidential, and what you cannot. “I will not share the detail of our conversation with the wider team. If something here affects your work, or your safety, I will need to act on it.”
For remote and hybrid teams, this stage is where most friction actually shows up. A line that would be harmless face to face gets read in a channel as contempt, and the writer has no idea. Ask about the channel and the tone, not just the words.
You will know this step worked when each account rests on things you could have observed yourself, and neither person needs you to explain what the other one meant.
4. Clarify the Conflict and Its Impact
Write the problem down in one neutral sentence that both people could read and accept. If they argue with your sentence, the sentence is not neutral enough yet.
Most conflicts fall into three types, and the type decides your response:
| Type | What it looks like | Manager response |
|---|---|---|
| Task conflict | Disagreement about how the work gets done, priorities, or standards | Usually productive. Set the goal, the decision owner, and a date; do not adjudicate every method choice. |
| Relationship conflict | Personal friction, cliques, exclusion, repeated slights | Address the behavior directly, agree how they will work together, check in often. |
| Values conflict | Disagreement about what the organization should do or stand for | Do not mediate. Clarify the stated values and decision rights, and escalate if it keeps recurring. |
Now name the impact in work terms: missed handoffs, a client waiting on a reply, the same task being done twice, a new starter copying the tension. Managers who only describe feelings leave the employees with no shared problem to solve.
Check the file for anything prior. If either person has had this feedback before, say so plainly and refer to it. Consistency of standard is most of what fairness means to the person on the receiving end.
You will know this step worked when both employees can restate the problem in the same words as you can.
5. Set Boundaries and Explain the Standard
Tell both people which parts are ordinary disagreement and which are not. “We will disagree about priorities, and I will not have either of you raising this in front of the client” is a boundary they can act on.
Apply the same standard to both. If one person can be terse in the channel because they are senior and the other cannot, you have described a hierarchy, not a standard.
Where a policy is engaged, name it and read the relevant line out loud. People comply with rules they have heard rather than rules they assume exist.
This is also the stage to name the thing nobody wants to say: if the behavior continues, there are consequences, and they apply equally. Say it once, plainly, and then do it.
6. Agree on a Joint Action Plan
Bring them together only once both accounts are in. Give each person the same ground rules beforehand: one person speaks at a time, no interrupting, describe what happened rather than what the other person is, and nothing agreed today is a surprise to anyone.
Keep it to observable behavior. “Jordan will include Sam on the handoff note before the Thursday client update” can be verified next week. “We will have better communication” cannot.
Ask them to generate the actions rather than handing them down. People commit to plans they helped write, and asking also reveals whether they understand each other’s constraints.
Then write it down while they are in the room. A useful record has six fields:
- Date and who attended
- The issue, in neutral language
- Who was spoken to separately, and when
- The root cause, in one line
- Agreed actions, each with a named owner and a date
- The review date and who runs it
Add a short relationship plan for anything that will keep happening: how they will exchange information, how quickly they will respond, and what happens when one of them is blocked.
For remote teams, name the channel. Async written updates by a set time, video for anything with emotional charge, and a rule that a document never gets discussed to death in chat without a fifteen-minute call.
You will know this step worked when there is a signed or acknowledged plan with observable actions and a date on the calendar.
7. Follow Up and Close the Matter
The follow-up is the stage most managers skip, and it is the one that decides whether anything changed. Book the check-in before you leave the room, and treat it as a real meeting rather than a courtesy call.
Meet with each person separately again. Ask what changed, what got in the way, and whether anything has restarted. Watch behavior rather than mood: response times, who is copied on what, whether handoffs land on time.
If the behavior has not changed, enforce the boundary you stated, consistently and without drama. Repeated disrespect after a clear agreement is a conduct matter, not a communication problem, and it moves to HR with your notes attached.
Keep records of anything material. Dates, agreed actions, whether actions happened. Write facts, not conclusions about character, and never speculate about motive. Store notes where your policy says they belong.
Close it out loud when it is over. Managers often leave the situation half-open, and both employees assume the tension is still live. A short note saying the plan is being met and no further action is needed ends the uncertainty for everyone, including you.
Do not treat a signed agreement as proof that anything changed. People sign things under pressure and wait to see what you do next.
Say this part out loud in a first conversation: conflict that drags on is a psychosocial hazard, not just an awkward week. Sustained tension is associated with stress, burnout, sick leave, disengagement and turnover, and it costs output long before anyone resigns. If someone is exhausted rather than annoyed, our piece on talking to your boss about burnout covers the conversation shape.
Persistent low-level conflict that never formally escalates is the version most likely to damage the team, and the one that slips through a normal process entirely. Nobody complains, everybody adjusts, and the work gets slower.
Common Mistakes
These are the errors I see most, with the correction for each.
Deciding who is right early. The moment you name a culprit, you become a party to the dispute. Hold the standard, not the verdict.
Investigating both people in the same room. It produces performance, not facts. Each person performs for an audience, and the quieter one says less, not more.
Letting retaliation run quietly. “I did not know you two were feuding” is not a defense. State the no-retaliation rule to both people, separately, and write it into the plan.
Making it personal with the manager. If you have a view about one of them, park it. Your irritation leaks into the conversation, and both of them can feel it.
Promising total confidentiality. You cannot promise it, and finding out later that you had promised it is a serious breach. Say what you can and cannot keep private, as above.
Leaving nothing in writing. Six weeks later, everyone remembers the meeting differently. Notes are not distrust; they are what makes a fair process defensible.
Treating the signed agreement as the finish line. Agreement is a commitment, not evidence. Verification is the finish line.
Waiting for the conflict to become serious enough to deserve your time. Every serious one you end up managing started as something small you had a free afternoon for.
Prevention is mostly unglamorous: clear role ownership, decision rights written down, expectations about channel and response time, and regular one-to-ones where problems get said out loud before they harden. Managers who were trained properly tend to have fewer escalations than managers who were sent in alone and told to cope.
If you want to hear how friction actually feels before it becomes formal, running focus groups with employees is a low-risk way to surface it. Once conflict is live, structured conversations work better than anonymous feedback, because the two people have to be in the same room for it to close.
Frequently Asked Questions
Should a manager mediate conflict between two employees?
Yes, for ordinary disagreements, especially task and relationship conflict, where both people work for you and no misconduct is alleged. Mediation stops being appropriate when the complaint involves harassment, discrimination, bullying or violence, or when one party manages the other. Those need HR or a formal process, because the power balance makes a meeting you run unfair by default.
How should a manager document an employee conflict?
Record the date and attendees of each meeting, the issue in neutral language, who was spoken to separately, the agreed actions with named owners and dates, and the review date. Write facts you could have observed rather than conclusions about someone’s character or motives. Keep notes where your records policy says, limit who can read them, and tell both employees that notes are being kept and why.
What if employees continue arguing after an agreement?
Meet with each of them separately and refer to the written plan and the date you both agreed. Apply the consequences you stated, consistently and without a lecture, because leniency toward one person resets the whole agreement. Do not renegotiate the plan repeatedly in front of the team. If disrespect continues after a clear standard, that is a conduct issue and it goes to HR with your notes attached.
How do managers prevent retaliation after a workplace complaint?
Tell both people separately, in writing where you can, that retaliation is not acceptable and describe what it looks like in practice, including exclusion and badmouthing in channels. Document the instruction and the date you gave it. Watch for retaliation afterwards, because it usually arrives quietly, and act on observable behavior rather than on what someone claims was their intent when they spoke to the wider team.
When can employees resolve conflict without a manager?
A direct conversation is fine for low-stakes task disagreements where both people are willing, there is no real power imbalance, and no conduct concern is involved. Start with open questions and describe the impact on the work rather than the other person’s character. Bring in a manager when the disagreement recurs, affects shared work or a third party, or when one of the two is the other’s supervisor.
How do you separate personal conflict from an employment-law issue?
Personal conflict is about behavior between people and is handled through boundaries, agreements and follow-up. An employment-law issue touches protected characteristics, pay, hours, leave, safety, or retaliation, and it may involve the law of your state or country rather than company policy. Do not investigate it yourself or promise an outcome. Document what you were told, route it to HR promptly, and seek individual legal advice if you are unsure.
If you have never had to work out how to handle conflict between employees before, start with the next conflict that is still small. Read the two accounts, book twenty minutes with each person separately, and put a date on your calendar for the follow-up you are going to owe them. That sequence, done early and done the same way for everybody, resolves more workplace conflict than any technique that comes after it.