Async by Default Only Works If You Write Things Down

The standard diagnosis for a struggling distributed team is overlap: not enough shared hours, too many time zones, coordination is hard. Overlap is a real constraint, but it is rarely the root cause. Teams that work well across ten time zones and teams that struggle across two differ mostly in whether decisions and context exist in writing.

The verbal default is the actual problem

In a colocated team, enormous amounts of context transfer through overheard conversation, hallway questions, and decisions made in a room. None of that survives distance. A team that keeps its verbal habits and adds distance loses the transfer mechanism without replacing it, and the symptom appears as "we need more sync time".

More meetings can compensate, up to a point, which is why the intuitive fix feels like it works before it collapses under scheduling load.

What must be written to work asynchronously

• Decisions, with the reasoning and the alternatives rejected. A decision without the why gets relitigated every quarter by whoever joined most recently.
• Current state of work, in a place anyone can read without asking. "What is the status" should never require a person.
• How to do recurring things. Deploys, on-call escalation, access requests. Every undocumented process is a dependency on one person's availability.
• Who decides what. Ambiguous ownership is the single largest generator of unnecessary meetings.

Write for the reader who is not there

Asynchronous writing has a different shape from a chat message. Lead with the conclusion, state what you need from the reader in the first two lines, and include enough context that someone who missed the last three weeks can follow. This is more work for the writer and much less work for the five readers, which is exactly the trade a distributed team should be making.

A meeting is a synchronous read of an unwritten document. Writing it first usually eliminates the need for the meeting and produces something the next person can read too.

Overlap is for the things that need it

Reserve shared hours for what genuinely benefits from being live: contentious decisions, early exploration where the shape is unclear, feedback that would be harsh in text, and relationship building. Anything else is a status update in an expensive format.

Making it stick

Two habits carry most of the value. First, decisions get written where the work lives, not in a chat thread that scrolls away. Second, when someone answers a question in chat, the answer moves to the document afterwards. The second one is a small tax that compounds into a team that can absorb new people without ceremony.