Conflict Between People Who Never Meet

Conflict in a distributed team follows a recognisable arc: a misread message, a sharper reply, a thread that hardens, and two people who now avoid each other in a way nobody else can see.

The mechanics are worth understanding because they are largely about the medium rather than the people.

Why text escalates

No tone. A neutral sentence is read according to the reader's current mood. On a bad day, "can you explain the reasoning here" is an attack.

No repair. In a room, a comment that lands wrong is visible immediately and gets softened in the next breath. In text the sender has no idea it landed wrong, and the receiver spends an hour composing a reply.

Asymmetric time. The receiver reads a message written in ten seconds and thinks about it for a day. The weight is not shared.

Audience. Disagreement in a channel is performed in front of colleagues, which raises the cost of backing down for both people.

The manager's problem: it stays hidden

In an office, tension between two people is visible — seating changes, meetings get shorter, others mention it.

Remotely it manifests as slightly slower responses, work routed around a person, two people never in the same call. Each is individually unremarkable, and a manager can miss the pattern for months while the team quietly reorganises around it.

Signals worth noticing: someone stops being included in threads they used to be in; a request that used to go directly now comes via you; two people are never in the same meeting; a project that involves both has slowed for reasons nobody can name.

Getting it out of text

The first move is almost always to move the conversation off the medium that is making it worse.

Call the two people separately first, not together. Each needs to say their version to someone who is not the other person. Do this before any joint conversation.

Then a joint call, if appropriate, with a stated purpose and a facilitator. Not "let's clear the air" — a specific question to resolve.

Never mediate in writing. A manager adding a message to a hostile thread is adding fuel with authority attached.

What to listen for

Most remote conflicts that look interpersonal turn out to be structural:

Unclear ownership. Two people who both believe they decide something will conflict indefinitely until someone resolves the ownership.

Incompatible expectations about response time. One person considers a day normal; the other reads it as being ignored. Neither is wrong and nobody stated the norm.

Invisible workload. Someone declining requests looks obstructive when their queue is not visible.

A dependency with no agreed process. Recurring friction at the same handoff is a process problem wearing a personality costume.

Fixing the structure resolves the conflict more reliably than any conversation about how people communicate.

What not to do

Do not tell them to sort it out. They cannot; the medium is part of the problem and neither has the standing to change it.

Do not move it to a group channel to get others' views. It becomes a performance.

Do not let it run. In an office an unresolved tension is uncomfortable. Remotely it becomes a permanent rerouting of work, and eventually one of them leaves without ever saying why.

Do not assume the quieter person is fine. Withdrawal is the most common remote response to conflict, and it looks like nothing.

Prevention

Stated response norms. Clear ownership. A team habit of moving to a call after two rounds of disagreement — stated as a norm so that suggesting it is not itself an escalation.

That last one is small and prevents a substantial share of what would otherwise become conflict.