Working Well With People You'll Never Meet

There are people I worked with for years whose height I could not guess. I knew how they handled a difficult deadline, which questions they asked before making a decision and whether their “quick thought” was likely to arrive as one sentence or a careful page. I knew the signs that they were overloaded. I never knew whether they would be tall enough to reach the shelf above my desk.

This is sometimes presented as evidence that remote work makes relationships thinner. I experienced something more specific. Distance removed the incidental information that usually stands in for familiarity and made the useful information easier to notice. I could not infer reliability from who arrived first at the office. I had to learn it from how somebody communicated, followed through and responded when a plan changed.

That kind of trust is possible between people who never meet, but it does not appear simply because a company has installed chat and scheduled video calls. It has to be built from visible behaviour and working agreements strong enough to survive silence.

Trust needs evidence

In a shared office, confidence accumulates through small observations nobody records. You see a colleague helping somebody solve a problem. You hear the context behind a delayed task. A five-minute conversation after a meeting repairs a misunderstanding before it becomes a story about somebody's intentions.

Distributed teams receive less of this evidence by accident. What remains visible is often a distorted sample: messages, completed tasks and calendar presence. When a colleague is quiet, nobody can see whether they are concentrating, caring for a child, waiting for information or quietly stuck. The empty space attracts interpretation, and interpretation tends to reflect the observer's anxiety more than the absent person's reality.

The solution is not continuous availability. Presence indicators and rapid replies can produce evidence of responsiveness while saying very little about whether the work is healthy. A team that equates trust with being visibly online will reward interruption and make considered work look suspicious.

Useful evidence is more concrete. People state what they intend to do, make progress visible at sensible intervals and raise uncertainty before it becomes a surprise. Managers explain decisions rather than letting priorities change through scattered messages. Colleagues close loops: they say when something is done, when it is not and what they need next.

These behaviours sound procedural because they are. Trust at work is not only a feeling of warmth. It is confidence that other people will make their actions legible enough for the group to coordinate without constant checking.

Make the work easier to read

The strongest distributed teams I have worked with treated written context as part of the work rather than as an account of work performed elsewhere. A decision included its reason. A project record showed the current owner and next meaningful step. An unanswered question had a place to remain visible without being reposted every few hours.

This reduces a particular kind of remote friction: the private reconstruction each person performs when information is distributed across meetings, direct messages and memory. Reconstruction favours the people closest to the centre of the team. Everyone else spends attention working out what changed and whether they were supposed to notice.

A lightweight working agreement can remove much of that uncertainty. It should answer ordinary questions in language the team actually uses:

• Which decisions require a meeting, and which can be made in writing?
• How quickly is a response genuinely expected in each channel?
• What does somebody do when they are blocked?
• Where does the final decision live after the conversation ends?
• How do people signal reduced capacity without disclosing private circumstances?
• When is it acceptable to continue without an answer?

The agreement is not a policy carved into stone. It is a shared default that prevents every quiet period from becoming a new negotiation. Teams should revise it when reality repeatedly disagrees.

Documentation alone cannot create trust. A perfectly maintained project board means little if people are punished for recording uncertainty honestly. The behaviour around the system determines whether it becomes evidence or performance. When managers respond constructively to an early warning, the next warning arrives earlier. When they treat every changed estimate as failure, the board becomes optimistic fiction.

Repair matters more than proximity

Remote relationships are sometimes described as fragile because conflict is harder without physical cues. There is truth in that. A short message can sound colder than intended, and a tense video call ends abruptly when the window closes. There is no shared walk back to a desk in which the temperature can fall naturally.

What matters is whether the team has a reliable way to repair. The best distributed colleagues I know do not attempt delicate disagreement through increasingly precise paragraphs. They recognise when the channel has become part of the problem and switch deliberately: a short call, a private conversation or a pause followed by a clearer written account.

Repair also requires generosity about missing context. “I may be reading this too sharply” is often a more useful opening than an accusation built from a sentence typed between two other tasks. This is not a request to ignore harmful behaviour. It is a recognition that distance removes information, and certainty should reduce with it.

Managers carry additional responsibility here. In an office, they may notice a relationship becoming strained through avoidance or atmosphere. At a distance, the team can continue producing visible output while trust deteriorates privately. Regular conversations need room for how collaboration feels, not only what has shipped. Otherwise the first visible sign may be somebody deciding to leave.

The people I never met did not feel imaginary to me. Our relationships were built from repeated, specific experiences: a colleague naming a risk nobody wanted to hear, another returning with the promised answer, a manager changing a decision after receiving better information. None required a shared room. All required attention.

Distance does not remove the ordinary work of trust. It removes some shortcuts and exposes whether the remaining structure can carry it. When expectations are visible, silence is not automatically suspicious and repair has somewhere to begin, people can work together for years without knowing each other's height—and still know the things that matter.