Every guide, in one list

Most async communication fails because the sender wrote as though the reader could ask a question. In another time zone, they cannot.

The most expensive thing a distributed team loses is not information. It is the reasoning behind a choice everyone has forgotten making.

Without a written norm, everyone invents one, and the most anxious person's version becomes the culture.

Async has real limits, and teams that treat it as an ideology spend weeks on things a call would have settled in twenty minutes.

The daily call exists to answer a question that a written format answers better and without occupying fifteen minutes of everyone's morning.

Every distributed team eventually has a communication problem that is really a routing problem.

Recurring meetings are created constantly and deleted almost never. The audit is the only mechanism that removes them.

A distributed meeting has a higher cost per minute and a lower tolerance for drift. Both argue for more structure, not less.

A transcript is not a record. The useful artefact is much shorter and takes deliberate effort to produce.

Most meetings that are cancelled come back, because the need was real and nothing replaced it.

The conversations that happened incidentally in an office do not happen at all remotely, which makes the scheduled one carry much more weight.

A day-long workshop translated directly to video is a bad day for everybody. The format has to change, not just the venue.

Teams either demand far more shared hours than the work requires, or none at all. Both are decisions made without arithmetic.

Follow-the-sun promises continuous progress and usually delivers a daily re-orientation tax that nobody counted.

Somebody has to take the call at eleven at night. In most distributed teams it is the same person every time, and nobody decided that.

Most time zone errors are not conceptual. They are the daylight saving change nobody accounted for.

A team spread across many zones has notifications arriving around the clock, and the default is that nobody ever has a quiet hour.

Distributed hiring is presented as a talent question and is mostly an administrative one.

Every team has documentation. The problem is that nobody trusts it, and untrusted documentation is worse than none.

Documenting everything is impossible and documenting nothing is expensive. The line is more findable than it looks.

Remote onboarding fails at the informal layer, and everything an office transmitted by accident now has to be transmitted deliberately.

The value of a runbook is not that it contains knowledge. It is that it works when the person reading it is tired and alone.

Most teams do not have too little documentation. They have the same information in five places, disagreeing.

The big documentation push is a recognisable pattern: three enthusiastic weeks, then nothing, then an apologetic restart a year later.

The instinct is to reconstruct the missing visibility. The better move is to stop needing it.

Output measurement is the answer to remote management and it is genuinely difficult, which is why so many teams fall back on activity.

Screenshots, activity scores and keystroke counts are available to any manager who wants them. The question is what they cost.

The social fabric of a team is built incidentally in an office. Remotely it has to be built deliberately, and most attempts are badly aimed.

The temptation is to handle them in writing, where they land worse and are remembered longer.

Sometimes the problem is the model rather than the execution, and it is worth being able to tell the difference.