How to Handle Conflict on Remote Teams

The pull request comment said, "Why did you do it this way?" Nothing else. The engineer who wrote it, in Dublin, meant it as a real question and logged off for the night thirty seconds later. The engineer who read it, in São Paulo, had just sat down with coffee at the start of her day, and with eleven hours to go before Dublin woke up, she read it maybe forty times. By mid-afternoon it wasn't a question anymore. It was proof that the guy in Dublin thought she didn't know what she was doing.

That is the shape of almost every conflict I have watched curdle on a distributed team. There was no real disagreement underneath it. Just a small ambiguous signal, read at the worst possible hour, with nobody around to take the edge off, left to sit for a full sleep cycle until it hardened into something personal.

The office defuses conflict for free

Think about how a misunderstanding dies in a room. Someone says a thing that lands wrong. You see the other person's face do something, catch the flicker, and say "wait, that came out harsh, I didn't mean it like that," and it's over in ten seconds. Or you don't catch it, but you walk past their desk an hour later, read the set of their shoulders, and clear the air before it has time to set.

None of that survives being distributed. The signal is a block of text with no face attached to it. The feedback loop that would have caught the misread in ten seconds is now a day long, if it closes at all. And the person on the receiving end is usually alone when they read it, with no colleague nearby to say "I'm sure they didn't mean it that way." They have the message, their own worst reading of the message, and a lot of quiet hours to sit with both.

This is a cousin of the thing that makes hard feedback something you should never push async. Written criticism read alone at the wrong hour loses its tone and invites a darker re-reading. Conflict between peers works the same way, with one difference: nobody chose to start it. It begins by accident, from a terse line that would have been completely fine said out loud.

Text amplifies, distance delays

Two forces turn a nothing into a something on a distributed team.

The first is that text runs colder and flatter than whatever was in the writer's head. "Fine, do it your way" is warm in person and arctic on a screen. People read emotional weather into a missing emoji, a period where there'd normally be an exclamation mark, a reply that came back two words shorter than usual. Across cultures they read different weather. A line a German engineer means as efficient and respectful can read as curt to an American expecting a softer wrapper. That is less a conflict than a cross-cultural translation gap, but it blows up the same way.

The second force is time. In the same building, a flare-up gets sorted out the same afternoon. On a team split across twelve hours, the wronged party gets a full working day to compose the grievance, show it to a work friend, and quietly decide the other person is the problem, all before that person knows anything happened. Resentment compounds in the dark. By the time both are awake at once, one has built a case and the other is about to learn they were on trial.

Catch it early, because it hides

The hard part is that this kind of conflict almost never announces itself. Nobody posts "I'm annoyed at Marcus." It shows up sideways. Two people who used to @ each other constantly go quiet. Someone starts cc'ing the manager on messages that never needed a manager. A review thread that should have taken two comments takes nine, each one a degree stiffer than the last. Work starts routing around a person instead of through them.

If you manage the team, those are the signals to watch, and they are easy to miss because the output still looks fine when you manage by output. Two engineers can be furious at each other and still close every ticket on time. The dashboard tells you nothing. What tells you is the texture: who has gone cold on whom, which collaborations slowed down, where the tone dropped a few degrees. A good retrospective surfaces some of it, but the genuinely sharp stuff rarely comes out in a group setting. You find it in a 1:1, if you think to ask.

When it's real, get them in a room

Here is the rule I would tattoo on a distributed manager. The moment a conflict is actually between two people, and not just a misread message, stop letting it happen in writing.

Async is the right default for almost all work. It is close to the worst medium for a disagreement that has gone personal, because every strength of it flips into a weakness. The permanence that makes async great for decisions means every sharp word is on the record, re-readable, quotable back at whoever said it. The reflection time that helps people write a careful proposal hands an angry person hours to sharpen the knife. Two upset people typing across a day of delay do not converge on peace. They escalate in slow motion and build a paper trail of it.

So get them live. Not a recorded video, not a long thread with the manager refereeing in the margins. A real synchronous conversation where tone is audible and the loop is instant, which usually means spending some of the scarce overlap window on it. Spend it anyway. The 1:1 stays synchronous for exactly this class of problem, the stuff a message can't carry, and a conflict between two teammates is that same category one person wider.

If there is genuinely no shared hour, treat it as a scheduling problem you solve once, not a license to mediate by text. Somebody takes an early morning or a late evening. The cost of one awkward call is nothing next to two senior people deciding they can no longer work together.

What the manager actually does

Getting them in a room is not the same as sitting them in a room and watching them go at it. Talk to each person alone first. Most of the time the disagreement turns out much smaller than the feelings stacked on top of it, and half of it evaporates the second each person hears that the other wasn't trying to do the thing they got accused of inside someone's head. A lot of remote conflict is two reasonable people who each filled an information gap with the least charitable guess available, because the gap sat there all night with nothing else to fill it.

Then, if it still needs a joint conversation, bring them together around something concrete to solve rather than a vague "let's clear the air." Clearing the air with no task to point at just hands two tense people a blank canvas and a reason to keep painting. A real decision to make together gives the repair somewhere useful to happen.

And watch your own behavior, because it sets the ceiling. If you answer a sharp Slack message with a sharper one, you have taught the whole team how disputes are conducted here. Tone at the top of a remote team travels further than it would in an office, because text is the only thing anyone has to read you by.

The cheaper fix is not starting them

Most of the above is cleanup. The better investment is leaking less of the ambiguity that starts these fights in the first place. A team that writes with a bit more warmth and a lot less terseness simply manufactures fewer of them. Before you fire off a two-word reply, assume it will be read alone, near midnight, by someone having a rough day, maybe in their second language. Add the sentence that makes your intent obvious. It costs four seconds and saves the other person a wrecked evening, and you a mediation session three days from now.

You will not head all of it off. People are people, and some conflicts are real and worth having in the open. But a large share of what explodes on a distributed team was never a real fight to begin with. It was a flat message, a long night, and nobody in the room to lean over and say, "hey, I think you read that one wrong."

Let Timely Handle the Clock Math

When a disagreement needs a live conversation, you don't want to lose the one hour you share to a timezone mix-up. Timely reads each person's Slack timezone and converts every time you mention into their own local clock, so "let's talk at 2" shows up in Dublin and São Paulo saying exactly when. It won't resolve the conflict, but it gets both people on the call at the same moment.

Add Timely to Slack — Free · See how it works