When Two People on Your Team Can't Work Together
Most manager-mediated conflicts fail because the manager solves the argument people are having instead of the one they aren't.
The situation
Two of your people have stopped working well together. Nothing dramatic — no shouting, no HR complaint. Just a slow degradation: one CCs you on everything now, the other has started making decisions without looping the first one in. Meetings have an edge. Work that used to take one conversation now takes three, and both of them come to you separately with a version of events in which they are reasonable and the other person is the problem.
You have probably already tried the thing that doesn't work: talking to each of them alone, agreeing with whoever is in the room, and hoping the tension dissolves. It doesn't. Private sympathy with both parties is the single most common way managers make a conflict permanent, because each person leaves believing the manager agrees with them.
Why it happens
Almost every workplace conflict is one of three things, and they need different treatment. Task conflict is disagreement about what to do — this one is healthy and you want some of it. Process conflict is disagreement about who decides, in what order, with what handoff. Relationship conflict is about respect: one person believes the other doesn't take them seriously.
The trap is that process conflict disguises itself as relationship conflict fast. Two people with overlapping authority and no agreed handoff will collide weekly, and after about the fifth collision they stop attributing it to the structure and start attributing it to each other's character. By the time it reaches you, they will describe it entirely in terms of personality — 'she doesn't respect the process,' 'he's territorial' — because the structural cause became invisible to them months ago.
Your job is to figure out which conflict you actually have. If two people are colliding because nobody ever said who has the final call on scope, no amount of relationship repair will fix it. They will simply be more polite while colliding.
The protocol
- 01Interview both separately, once, with the same three questions: What's the work outcome you're trying to protect? Where exactly does the process break? What do you think they think of you? The third question is the one that reveals whether respect is in play.
- 02Name the category to yourself. Task, process, or respect. If it's process, you can fix most of it with a decision-rights conversation and never hold a feelings meeting at all.
- 03Set the joint meeting with a stated purpose and a stated non-purpose. 'We're going to agree how decisions get made on this project. We're not going to relitigate the Q2 launch.' Boundaries make the meeting survivable.
- 04In the room, make each person state the other's position to the other's satisfaction before either argues. It is slow and it feels artificial and it works, because most of the heat comes from feeling unheard, not from disagreement.
- 05Write down the terms: who decides what, what gets shared, by when, and what each person will stop doing. Send it to both within the hour. Unwritten agreements between people who don't trust each other last about four days.
- 06Schedule a 20-minute check at two weeks. Not to discuss feelings — to check whether the terms held.
What to say
Opening the joint meeting
"You're both good at your jobs and the work between you is getting slower. That's my problem to fix, not yours to endure. Today we're deciding how decisions get made between the two of you. We're not settling who was right about the launch — that one's closed."
When one person starts relitigating
"Stop there. I hear that it still stings, and I'm not saying it doesn't matter. But if we spend this hour on March, we'll leave with the same problem we walked in with. What would have to be true about the handoff for March not to repeat?"
Refusing to be the referee
"I've noticed I'm getting CC'd on things the two of you can settle. I'm going to stop replying to those. If you're stuck after one direct conversation, come to me together — not separately."
What not to do
- —Don't let each of them make you their ally in private. Say plainly, in both conversations, that you'll be repeating the substance to the other person.
- —Don't force a friendship. The standard is professional cooperation and clean handoffs, not warmth. Demanding warmth makes honest people perform it, and performed warmth is worse than open distance.
- —Don't separate them as your first move. Reorganizing around a conflict teaches the whole team that avoidance is the escalation path.
- —Don't hold the meeting when you're irritated with both of them. They'll hear it, and you'll get compliance instead of resolution.
- —Don't leave it verbal. If it isn't written, it didn't happen.
Signals you got it right
You stop being CC'd. The volume of copied-in email between the two of them is the cleanest measure you have, and it should drop within a fortnight of the terms being written down.
They disagree in front of you and it stays about the work. Disagreement is not the problem and never was. What you want is an argument about sequencing that ends in a decision rather than in two people privately updating their case against each other.
Neither of them raises the other with you in a one-on-one for a month. Silence here is genuinely good news: it means the issue is being handled between them at the level it belongs.
The one thing that changes everything
Ask yourself whether the structure made this conflict inevitable. Two people with shared responsibility and no named decision-maker will fight, and it isn't a character flaw in either of them — it's a design flaw in your org that they've been absorbing. When that's the cause, the most respectful thing you can do is say so out loud: 'This is on me. I never said who owns the final call. I'm saying it now.'
Facing this right now?
Describe your situation and get a diagnosis, one principle, a named protocol, and the exact words to say.
Describe your situation and get a diagnosis →