Respond When an Employee Wants You to Solve a Conflict
Support an employee through a peer conflict while deciding what the manager needs to own.
An employee who walks into your office and says "fix this with my coworker" is handing you a test disguised as a request. Say yes without asking questions and you either take on a problem that belongs to two adults, or you miss a real safety or policy issue hiding under a personality complaint. Push back too fast and the employee stops bringing you anything, and the conflict keeps damaging the work while you stay in the dark. The right response sits in the middle. Listen long enough to understand what actually happened, then decide what you own and what the two employees need to work out themselves.
Why This Conversation Goes Wrong
Most managers treat this moment as a choice between two extremes. Either rescue the employee by stepping in and handling everything, or send them back to solve it alone. Both responses fail for the same reason, neither one is based on the facts of what happened.
Rescuing feels helpful in the moment. You deliver a verdict, the employee feels heard, and the meeting ends quickly. But you have now taken ownership of a relationship problem without hearing the other side, and you have taught the employee that the fastest way to win a disagreement is to bring it to you first. Sending them back without any structure feels like healthy delegation, but if the complaint involves a real work failure, a policy violation, or a safety concern, you have just told someone with a legitimate problem that it is theirs to manage alone. Both mistakes come from skipping the step where you actually find out what happened before you decide how to respond.
How to Prepare
Before you respond to the request, get the facts you need to sort a work disagreement from something more serious. Ask about the specific event that triggered the complaint, not the general pattern of frustration. Ask what work was affected and how. Ask what the employee already tried before coming to you. Ask directly whether there is a safety or policy concern involved, because that question changes everything about how you proceed.
A disagreement about who owns a decision, who missed a handoff, or who gets credit for a piece of work usually calls for a structured conversation between the two employees, with you facilitating. A report involving harassment, discrimination, retaliation, or a safety issue calls for your organization's formal process, and you should not try to mediate that yourself. If you are not sure which category you are in, ask more questions before you commit to either path. Rushing that judgment is where managers get into trouble.
What to Say
Employee Jordan told manager Keiko, "You need to tell Morgan to stop changing my files. I cannot keep working like this."
Keiko did not agree or disagree. She said, "Walk me through one recent time this happened and what it affected."
Jordan pulled up a project file and said, "Morgan moved the delivery date without telling me. The client got my original date, then a different one showed up on the shared file."
Keiko said, "That is a real problem, and I can see why it landed on you. Here is what I will do. I will clarify today who owns date changes on this project. Are you willing to sit down with Morgan while I walk through the handoff with both of you?"
Jordan said, "Yes, as long as we stick to the project and not everything else."
Keiko answered, "That is exactly how we will run it. We will look at the file history together, agree on who gives notice before a date changes, and write down who has to approve it next time."
Notice what Keiko did not do. She did not promise to talk to Morgan on Jordan's behalf. She did not agree that Morgan was wrong before hearing anything else. She asked for one concrete example, confirmed the impact was real, and proposed a specific next step that she would run, not one she was leaving Jordan to handle alone. That combination, taking ownership of the process while withholding judgment on the person, is what keeps this kind of conversation from becoming a referendum on someone's character.
Mistakes to Avoid
Do not accept one employee's account as the full picture and act on it. Jordan's version may be accurate, but Morgan has not spoken yet, and a decision made before that conversation will look unfair once Morgan's side comes out.
Do not turn the meeting into a performance review of the other employee. Keiko's job in this exchange is to fix a handoff problem, not to build a case against Morgan.
Do not skip the question about safety or policy because the complaint sounds like a normal work disagreement. Plenty of serious reports start out sounding like a scheduling dispute. Ask the direct question every time, even when you think you already know the answer.
Do not let the joint conversation happen without a plan. If you put two frustrated employees in a room with no structure and no agreed outcome, you get a longer version of the same argument, now with an audience.
Do not disappear after the meeting. A plan that nobody checks on turns into an agreement that quietly stops working. If your organization is also working through a related issue, such as a team that has learned to route problems around a difficult manager instead of raising them directly, the piece on how to Coach a Leader When the Team Bypasses the Escalation Route covers a similar pattern of deciding what to own and what to hand back.
How to Practice and Score It
This conversation is hard to get right on the first try because it asks you to do two things at once, show the employee you take their concern seriously and hold back from taking sides before you have both accounts. Reading about it helps, but running through it out loud is what actually builds the skill.
Practice the exchange with a partner or with a tool built for this kind of rehearsal, and score yourself against a short list. Did you ask for a specific event instead of accepting a general complaint. Did you ask the safety or policy question out loud, not just think about it. Did you propose a next step you own, rather than a vague instruction to work it out. Did you end with an agreement specific enough that both employees could repeat it back in the same words.
DealSpeak runs this exact scenario as a practice conversation, with an AI counterpart playing the employee and feedback on where your response held up and where it slipped into rescuing or deflecting. It sits alongside other HR and Leadership practice conversations built around the moments that come up most often for people managers, including what to say when the topic shifts from a peer conflict to something raised through formal channels, like the guidance in Explain the Next Step After an Engagement Survey.
Set a reminder to check the handoff again within a week of the agreement. If the same gap shows up twice, treat it as a signal that the first conversation missed something, and go back to the facts before you decide what to do next.
Practice these next
End a development discussion with a behavior, setting, and review point that both people can recognize.
Keep a growth conversation honest, useful, and separate from promises about future roles.
Restart a missed improvement commitment with evidence, curiosity, and a specific next action.
Create a specific opening for dissent and show how the manager will use what they hear.
Use observed meeting behavior to restore space for colleagues to finish their thinking.
Use one concrete handoff to clarify quality, impact, and the next check.