How to manage conflict in a team

Most managers do one of two things. They wait, hoping it settles, until it arrives as a resignation or a shouting match. Or they jump in fast, make both people feel heard, agree with everyone and change nothing. Both feel like leadership at the time. Neither is.

What follows is a sequence with the sentences included. Say them out loud once before you use them. Words that look reasonable on a screen can leave your mouth sounding like an accusation.

First, work out what you are actually dealing with

Conflict on teams comes in three flavours, and they need different handling. Getting this wrong is why so many conversations go nowhere.

• Task conflict is disagreement about the work itself: the approach, the standard, the priority. This kind is useful. A team with none of it is not aligned, it is quiet.
• Process conflict is disagreement about how and who: ownership, sequence, who signs off, who was meant to tell the client. Most of what managers call a personality clash is this, unresolved for six weeks.
• Relationship conflict is about the person: tone, respect, history. This one damages teams, and it is almost never where things started.

Nearly every relationship conflict on a team began as a task or process conflict that nobody closed. You are usually not fixing personalities. You are fixing a decision nobody made.

Before the conversation, finish this sentence for yourself: "The undecided question underneath this is ______." If you cannot finish it, you are not ready to talk yet.

The opening thirty seconds decide everything

A bad opener puts the other person into defence before you have made your point, and you spend twenty minutes climbing back out. A good one names the topic, bounds the time, and states your intent.

Say: "I want to talk about the handover on Thursday, the one where the client got two different dates. Ten minutes. Now or after lunch, your pick."

That sentence is doing quiet work. The topic is specific, so nobody spends the walk over imagining they are being fired. The time is bounded, so it feels survivable. The choice of when hands back a scrap of control.

Wrong way, better way

The conversation, in sequence

Roughly fifteen minutes, one to one. The order matters more than the wording.

1. Minute one: name it and state your intent. "I want to talk about the handover on Thursday. I'm not here to tell you off, I want to work out what happened so it doesn't happen again." Then stop talking.
2. Minutes two to five: ask, then be quiet. "How did it look from where you were sitting?" Count to five in your head before you fill the silence. The useful sentence arrives after the awkward pause, not before it. This is where active listening earns its keep.
3. Minute six: play it back before you respond. "So the way you saw it, you'd flagged the date twice, nobody came back, and you made a call. Have I got that right?" If they say no, you have just avoided arguing with a position they do not hold.
4. Minutes seven to nine: your side, once, as observation. Describe what you saw and its effect, not what you assume they intended. "The client got two dates within an hour. I had to call them to sort it out, and it cost us credibility." The SBI feedback model is the frame here: situation, behaviour, impact, nothing else.
5. Minutes ten to twelve: isolate the real disagreement. "It sounds like we agree the client should only ever get one date. Where we differ is whether you wait for me when I've gone quiet. Is that fair?" Most conflicts shrink at this step, because the actual gap is narrower than the argument around it.
6. Minutes thirteen to fifteen: close with a decision, an owner and a date. "Right. From now on, if I haven't come back within four hours, you make the call and copy me. I'll do the same for you. Let's check in a fortnight and see if that's holding." Write it down in two lines and send it. Conflicts that end on a feeling reopen. Conflicts that end on a decision usually do not.

When it is between two of your people

The instinct is shuttle diplomacy: talk to each of them, carry messages, keep the peace. It fails reliably. Both people start optimising for your sympathy rather than a resolution, and you become the permanent go-between.

1. Ten minutes with each, separately, first. One question does most of the work: "What do you want to be different a month from now?" It pulls people out of grievance and into outcome. Tell them you will be putting them in a room together, so nobody is ambushed.
2. Set the rules out loud before anyone speaks. "Three ground rules. One, no interrupting. Two, before you reply, you tell me what you heard. Three, we leave with a decision, not a feeling. I'm running this, I'm not judging it."
3. Each states their position uninterrupted, three minutes. You time it. If someone talks over the other, the intervention is short and neutral: "Hold that. You'll get your three."
4. Force the summary. "Before you respond, tell me what you heard her say." People cannot repeat back an argument and keep caricaturing it at the same time. This single move defuses more conflicts than any amount of empathy language.
5. Name the decision that has to be made. "So this is really about who owns the client relationship during a handover. That's a decision, and I'll make it if you two can't in the next ten minutes."
6. End with three written commitments and a review date. Two weeks later, ask them both, separately, whether it is holding. Skip the follow-up and everyone learns that agreements made in your office are decorative.

When it goes wrong

It will, in fairly predictable ways. The recovery move matters more than avoiding the failure.

• They get upset, or angry. Do not retreat and do not push on. "Let's stop for ten minutes. I'm not taking back what I said, but I'd rather say it when we can both hear it properly." Then actually stop, and actually come back. Abandoning the conversation here teaches the team that tears end discussions.
• They agree with everything and change nothing. That was compliance, not agreement. Go back and get the objection out: "You agreed quickly and I don't fully believe it. Tell me the part you don't buy." If nothing surfaces, the psychological safety on your team is thinner than you think, and that is the bigger problem.
• The same conflict reappears the following week. You closed with a truce rather than a decision. Reopen it once, name the pattern, then write down who decides what in one sentence and circulate it. Repeated conflicts are usually undefined decision rights wearing a costume.
• One party is your strongest performer and everyone is watching. This is the one that costs you the team. Say it directly: "You are very good at the work. The way Thursday landed on the team is a separate thing, and it isn't optional." Protecting a high performer from feedback is the fastest way to lose the three people around them.
• Halfway through, you realise you were wrong. Say so, plainly and without a performance of it: "I came in thinking you'd gone around me. What you've just told me changes that. My mistake." You lose nothing. A manager who can update in public makes it safe for everyone else to.

The three habits that prevent most of it

Conflict management is mostly conflict prevention done six weeks earlier.

• Make decision rights explicit. Who decides, who is consulted, who is merely told. Ambiguity here generates more workplace conflict than any personality on your team.
• Insist that disagreement happens in the room. If people only object afterwards in side channels, you do not have harmony. You have a storm running underground, which is what Tuckman's storming stage looks like when it is suppressed.
• Close every disagreement out loud. What we decided, who owns it, when we revisit it. Twenty seconds saves a fortnight of re-litigating.

Reading this will not change what you do on Thursday

You already knew most of it. The gap between managers who handle conflict well and managers who avoid it is not knowledge, it is what their body does when someone's voice goes up. That shifts only through rehearsal: saying the awkward sentence out loud, badly, somewhere it costs you nothing, then again with the feedback applied.

That is the whole argument for experiential learning here. Put managers in a real disagreement with low consequences, let them open it clumsily, then run it again. Two rounds of that change more behaviour than a year of reading, including this page.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.