Conflict at Work: What a Manager Should Do, and What HR Should Not

TL;DR

• The core decision: whether what you're watching is disagreement about the work, which you should leave alone, or a broken relationship, which won't fix itself.
• When doing nothing is right: when two people argue hard about the work in the open and then get on with it.
• What has to be true: you can name what the two people actually disagree about, in a sentence, without using the word personality.
• How the options split: by who does the work of resolving it, and whether the process is formal.
• Decision rule: task conflict is a feature and should stay visible. Relationship conflict compounds weekly and needs intervening in early.
• Outcome to expect: one uncomfortable set of conversations, instead of a slow tax on everybody who works near them.

The Thing Everyone Has Stopped Mentioning

Two capable people have stopped working well together. Nobody can say exactly when it started. What's observable is smaller: they don't sit together any more, one of them stopped being copied on things, a meeting got scheduled that both of them needed to be in and only one turned up.

The manager has noticed. They've also noticed that raising it would be awkward, that both people are good at their jobs, and that these things sometimes settle. So the decision is made to keep an eye on it, which is a decision to do nothing described in a way that sounds active. Meanwhile the team routes around it. Somebody else becomes the messenger between them. A piece of work gets split more cautiously than it needed to be.

Then something happens that makes it undeniable, usually a piece of work going wrong in a way that traces directly back to the two of them not talking. At that point the manager has to intervene anyway, months later, with a worse relationship to work with and a team that's been watching the whole time and has drawn its own conclusions about whether things get dealt with here.

Recommended Tools

Best tools for Leadership & Culture

C Culture Amp Culture measurement L Lattice Leadership development L Leapsome People enablement platform

View all recommended tools

The underlying error isn't the delay, it's the diagnosis. Waiting is genuinely the right answer for some conflict. People arguing about how to do the work should argue, and a manager who smooths that over is removing the most useful thing a team does. What doesn't resolve itself is a relationship that's broken, and the two look similar for about a fortnight and then diverge completely.

When You Genuinely Do Not Need to Act Yet

Your current setup is genuinely fine. Two people disagree strongly, say so in the open, and work together afterwards without residue. That's a healthy team doing what it should, and intervening to make it more comfortable would cost you the disagreement without gaining anything. The instinct to smooth this over is the most common unforced error in this area.

Friction is starting to show. The disagreement has started to be about each other rather than about the work, or you've noticed one of them checking who else is in a meeting before accepting. That shift is the signal worth acting on, and it's early enough that a single conversation with each person will usually do it. The cheapest check is whether either of them has said something dismissive about the other's motives rather than their reasoning.

It has become a real cost. Other people are managing around it, information has stopped flowing between two parts of the team, or somebody has become the intermediary. At this point the conflict has stopped being private to the two of them and is taxing everyone nearby, and the cost is accumulating whether or not you're watching it.

The edge case that forces it. Somebody has raised a complaint, or the behaviour has crossed into something that may be unlawful, such as harassment or discrimination. That's no longer conflict management and shouldn't be treated as such. What's required differs sharply by jurisdiction, including what must be investigated and how, so establish what applies where you are and take local advice early rather than handling it informally and finding out afterwards.

Five Questions This Reader Asks at 11pm

Should I get involved at all? If it's about the work and it's happening in the open, no. If it's about each other, or if it's gone underground, yes, and sooner than feels comfortable. The distinguishing question is whether they're arguing about a decision or about a person, and you can usually tell within one conversation.

What if I intervene and make it worse? A real risk, and it's usually caused by one specific mistake: bringing both people into a room before you understand what's actually going on. Separate conversations first, always. A joint meeting held too early turns a private difficulty into a public confrontation that both people then have to defend.

Is it my job or HR's? Yours, in almost every case, and reaching for HR early is frequently a way of avoiding the discomfort. HR's genuine role is where a complaint has been made, where the matter may be unlawful, where you're personally involved, or where a formal process is required. Sending an ordinary interpersonal problem to HR escalates it in both people's eyes and takes it out of your hands.

Do I just separate them? Sometimes that's the honest answer, and it's undervalued as an option. Two people who genuinely cannot work together and hold roles that could be rearranged are cheaper to separate than to repair. What you shouldn't do is separate them silently and call it a solution, because the unaddressed version travels with them.

What if one of them is clearly in the wrong? Then it isn't conflict, it's a performance or conduct issue wearing conflict's clothes, and treating it as a two-sided problem is unfair to the other person. Mediating between somebody behaving badly and somebody on the receiving end tells the second person that their experience is a matter of perspective, which does lasting damage.

Three Honest Categories the Approaches Split Into

Leave it with them. You decline to get involved, on the basis that adults can resolve their own differences, and you say so explicitly if asked. It's right for task conflict, which needs no resolution, and it's right early on when two reasonable people have had one bad exchange. Saying nothing works well precisely because most disagreements do settle. It fails when it's a default rather than a judgement, and it fails invisibly: by the time a manager discovers the thing didn't settle, the relationship has usually hardened, and the team has concluded that problems here get ignored rather than left.

Intervene yourself. You have separate conversations with each person, work out what's actually going on, and either broker something or make a decision. It's right in most situations that need any response at all, because you have the context, the authority and the relationship, and because handling it yourself signals that this is normal management rather than an incident. It fails when you're part of the problem, when you strongly prefer one of the two, or when you bring them together too early. It also fails when it's done once and not followed up, since nearly all of these need a second conversation a fortnight later.

Hand it to a process. A formal grievance, an investigation, a trained mediator, or another manager acting as a neutral. It's right when a complaint has been made, when the matter may be unlawful, when you're personally involved, or when a power imbalance means the more junior person can't speak freely in front of the other. It fails when reached for early, because a formal process changes the nature of the thing permanently: both people start behaving as parties to a case, positions harden into statements, and the informal resolution that was available last week is gone.

Five Diagnostic Questions You Can Self-Assess Against

Can you say what they disagree about in one sentence? Try it. If the sentence names a decision, a priority or an approach, you're looking at task conflict, which is usually productive and shouldn't be smoothed. If you can't get past describing personalities and clashes, either you don't know yet, or there's no substantive disagreement left and what remains is the relationship.

Has either of them questioned the other's motives? This is the clearest single marker of the shift from task to relationship. Disagreeing with somebody's reasoning is normal. Explaining their position by reference to what they're really after, or to what they're like, means the argument has stopped being about the work, and it rarely comes back on its own.

Who else is absorbing this? Look for the intermediary, and there's usually one. Somebody has quietly become the person who talks to both of them, forwards things between them, and softens messages in each direction. That person is paying for the conflict in time and stress, usually without acknowledgement, and their existence is a reliable sign that it's beyond the two of them.

What have you already done about it without calling it that? Most managers have been managing around the problem for weeks: splitting work differently, choosing who goes to which meeting, briefing one before the other. Write that list. It's the evidence that you decided there was a problem some time ago and chose to handle it silently.

Would either of them say there's a conflict? Ask, separately and directly. It's common to find that one person considers it a serious ongoing problem and the other hasn't registered it at all, and that asymmetry changes what you should do entirely. It's also common to find the disagreement is about something concrete and easily settled that neither felt able to raise.

Five Ways Conflict Gets Handled, Reviewed

Waiting for it to pass

You observe, you don't intervene, and you allow the situation to resolve itself. It earns its place more often than its reputation suggests. Most workplace friction genuinely does settle: people have a bad exchange, cool off, and return to normal working without anyone's help, and a manager who intervenes in all of those becomes an unnecessary presence in every minor disagreement.

Where it falls short is that it's rarely a decision. It's the default, chosen because intervening is uncomfortable, and it's applied uniformly to situations that would resolve and situations that won't. The cost is asymmetric: waiting on something that would have settled costs nothing, while waiting on a broken relationship costs a little more every week, and by the time it's undeniable the repair is much harder.

If you're going to wait, put a date on it. Decide that you'll look again in two weeks and what you'll consider evidence either way. That converts avoidance into a plan, and it's the whole difference between the two.

Separating the people

You change the structure so they don't have to work together: different projects, different reporting lines, different parts of the process. It earns its place as an honest answer more often than managers like to admit. Not every pair of people can work together, some relationships are past repair, and where roles can be rearranged at reasonable cost, separation is quicker and kinder than a repair attempt that fails.

It falls short when it's done silently, which is the usual version. Two people quietly kept apart, with nothing said, learn that this is how things are handled, and the underlying behaviour travels with each of them to their next pairing. It also fails when separation isn't actually possible, and pretending otherwise produces a half-measure where they still depend on each other but now have no channel.

Done properly it's explicit: this isn't working, here's the change, and here's what each of you needs to be different regardless. Separation without that conversation is deferral.

Be careful about who absorbs the cost of the rearrangement, because it's rarely neutral. If one person keeps the interesting work and the other is moved, you've made a judgement about which of them matters more and communicated it to the whole team without saying a word. Where the separation genuinely is no-fault, the change should look no-fault, and where it isn't, you should be handling the underlying problem rather than dressing it as a structural tidy-up.

The manager mediating directly

You talk to each person separately, then bring them together with a clear purpose and something specific to agree. It earns its place as the default for most situations that need action. You have the context to know what's real, the authority to make something stick, and the relationship to be heard, and handling it yourself keeps it in the category of ordinary management.

It falls short in three identifiable cases: when you're part of the conflict, when you have an obvious preference between the two people, and when there's a power gap that makes honest speech impossible for one of them. It also fails on sequencing, which is the most common error. A joint meeting before you understand the situation turns a manageable problem into a performance in front of an audience, and neither person can back down afterwards without losing face.

The sequence that works is separate conversations first, then a joint one with a narrow agenda and a specific working agreement, then a follow-up a fortnight later that actually happens.

One thing to decide before the joint meeting: what you'll do if it goes badly in the room. These occasionally escalate rather than settle, and a manager without a plan tends to let it run in the hope it turns. It's better to end it early, say plainly that this isn't working today, and reconvene, than to preside over an exchange both people will remember. Nothing said in a bad joint meeting can be unsaid.

A neutral third party inside the company

Another manager, someone from HR acting informally, or a trained internal mediator sits with both people. It earns its place when the manager is compromised, when the two people are in different teams with no common manager below the senior level, or when previous attempts by the manager have failed. A genuine neutral can hear things neither person would say to somebody with authority over them.

It falls short when the third party isn't actually neutral, which is common in a smaller organisation where everybody has history. It also introduces a delay and a degree of formality that changes the tone, and it can let the manager off a hook they should be on: handing your interpersonal problem to a colleague is sometimes the right call and is frequently avoidance.

Where it's used, the manager should stay involved rather than treating the handover as completion. The agreement still has to be implemented in the team, and that's yours.

A formal process

A grievance, an investigation, or a structured procedure with records and outcomes. It earns its place where it's required: a complaint has been made, the behaviour may be unlawful, there's a safeguarding dimension, or the informal routes have genuinely been exhausted. In those situations, handling things informally isn't kindness, it's exposure, for the organisation and for the person who raised it.

It falls short when used as a first resort, because it converts a relationship problem into a case. People take positions, write things down, and involve representatives, and the ordinary conversation that could have resolved it becomes impossible. It's also slow, it's stressful for everybody involved, and it frequently ends without either person feeling resolved even when the process was run properly.

What's required and how it must be run differs substantially by jurisdiction. Find out what applies where you are before starting anything formal, and take local advice rather than following a procedure borrowed from elsewhere.

The Decision Table

The last row is the one most often misfiled, and the cost lands on the wrong person. Framing a conduct problem as an interpersonal conflict tells the person on the receiving end that what happened to them is a matter of perspective and that they hold half the responsibility for fixing it. That reads as the organisation taking a side while claiming not to.

Telling Task Conflict From Relationship Conflict

Almost every decision in this area follows from this distinction, and it's usually made by instinct rather than by evidence. The signals are observable if you look for them.

The fourth row is the most useful early warning available, and the easiest to dismiss. When two people who used to talk start putting things in writing and copying others, the formality isn't efficiency, it's a record being built by both sides. That shift almost always precedes the point at which somebody raises a complaint, and it's the last moment an informal conversation is easy.

The seventh row catches something managers frequently miss. A disagreement that keeps recurring in the same form with no new arguments has usually stopped being about its stated subject. Either the decision was never actually made, in which case make it, or the subject has become the vehicle for something else, in which case deciding it will change nothing.

What HR Should Stay Out Of

There's a reflex in many organisations to route interpersonal difficulty to HR, and it does harm in specific, predictable ways. Three situations are better kept with the manager.

Ordinary disagreement between two people who report to you. Sending this to HR tells both of them that their difficulty has become a matter for the institution, which raises the stakes immediately, and it removes the person with the most context from the resolution. It also teaches your team that you don't handle things, which affects what they bring you next time. This is the core of management, not an exception to it.

Anything where the manager just wants the discomfort handled. Handing it over feels responsible and frequently isn't, and the tell is whether you'd struggle to say what you want HR to do. If the honest answer is that you'd like somebody else to have the conversation, the problem is the conversation and it's still yours.

And early-stage friction that hasn't been discussed with either person. A surprising amount of conflict reaches HR before anybody has asked the two people what's going on, which means the first formal contact precedes the first honest one. That sequence is close to guaranteed to harden positions.

What HR genuinely should hold is narrower and more important: any complaint, anything that may be unlawful, anything involving a power imbalance the manager can't neutralise, anything where the manager is a party, and any situation where a formal process is required or advisable. In those cases involving HR early is not escalation, it's the correct handling, and delaying it exposes both the organisation and the person who raised the concern. Because the boundaries differ by jurisdiction, agree in advance where the line sits for your organisation and take local advice on it rather than deciding case by case under pressure.

What to Put in Writing

Over-documenting ordinary friction changes what it is, so the bar for writing things down should be higher here than elsewhere. Four things are worth recording.

The third row is the one that determines whether any of this works. Nearly every resolved conflict needs a check-in a fortnight later, and nearly every manager skips it because things appear to have improved. Appearing improved is what the first two weeks look like in both the cases that hold and the cases that don't.

Questions to Ask Before You Commit

On diagnosis. What do they actually disagree about, in one sentence? A bad answer describes personalities.

On the shift. Has either of them questioned the other's motives? A bad answer is that you would have to ask.

On the cost. Who else is absorbing this? A bad answer is nobody, given without checking.

On your position. Can you be fair to both? A bad answer is yes, offered quickly.

On sequencing. Have you spoken to each of them alone? A bad answer is that you were going to bring them together.

On the route. Does this need a formal process, and who confirmed that? A bad answer is a comparison to a previous employer.

What Getting This Wrong Costs

The first cost is paid by people who aren't in the conflict, and it's the one that never appears in any account of it. When two people stop working together, the team adapts: somebody becomes the go-between, work gets split along lines that suit the conflict rather than the task, meetings get arranged around who can be in a room with whom. All of that is real work, done by people with their own jobs, and none of it is visible as the cost of an unaddressed problem.

The second cost is what it teaches everybody watching. A team sees a manager notice something and do nothing for months, and draws a general conclusion rather than a specific one: difficult things don't get dealt with here. That conclusion then shapes what people bring you, including things that have nothing to do with this conflict, and it's much harder to reverse than the original situation was to address.

The third cost is that your options narrow as you wait. In the first fortnight, a conversation with each person usually resolves it, and the relationship is intact enough that both are willing. Six months later the same conversation has to overcome accumulated evidence on both sides, a story each person has told themselves and others, and frequently a written trail. The intervention that would have been easy is now a process, and processes rarely end with two people working well together.

So before you do anything, settle which of three things you have. Task conflict is a disagreement about the work, it's valuable, and your job is to make sure it stays in the open and gets decided. Relationship conflict is a breakdown between two people that won't self-correct and gets more expensive weekly. Conduct is one person behaving unacceptably, and treating it as conflict is unfair to the person on the receiving end. Different problems, different responses, and the most common failure in this area is treating the third as though it were the second.

When You Are Ready to Go Further

Nothing here needs a mediator or a policy. It needs an honest diagnosis, a separate conversation with each person this week rather than next month, and a follow-up date written down at the time.

The step beyond the individual case is knowing where the line sits. Most organisations have never agreed what belongs with a manager and what belongs with HR, so the answer is decided ad hoc under pressure, differently each time, which produces inconsistency that employees experience as unfairness. Settling that in advance, with local advice on the legal boundaries, is worth more than any amount of conflict training.

HROpsLab publishes independent comparison work across HR tooling, applicant tracking and payroll. We sell nothing, we take no vendor money, and we publish no paid placements. If the next step is looking at how consistently these situations are handled across your organisation, our comparison work is one place to start.

Frequently Asked Questions

Most conflict either resolves itself or gets worse every week. The only expensive mistake is not knowing which one you're looking at.