Dr. Neil's Notes
General > People
Default to Async
Introduction
Most distributed teams treat asynchronous communication as the consolation prize for not being in the same room. A meeting is the real thing, and async is what you do when a meeting is not possible. I think this is backwards.
Async, done well, is a more powerful way of working than synchronous-first. It produces better thinking, creates durable records, respects time zones, protects deep work, and gives people the space to contribute when they are at their best rather than when they happen to be online simultaneously.
Writing Things Down
If something only exists in someone's head, or only in a meeting that just ended, it does not exist for the colleague coming online eight hours later. Writing decisions down, capturing the context behind a direction, and explaining the reasoning rather than just the outcome are not administrative overhead. They are the mechanism by which a distributed team actually functions as a single team rather than a collection of individuals in different locations.
A well-written brief also forces clearer thinking. The process of writing for an audience that will read it without the ability to ask clarifying questions in real time requires more precision than speaking to a room. That precision improves the quality of the thinking itself, not just the record of it.
Answering a question with documentation rather than a direct reply is also worth recognising as the better outcome. The question gets a durable answer, and the next person with the same question does not need to ask.
Protecting Deep Work
Meetings are the enemy of flow. I have been in organisations where the meeting load was so heavy that the only time real work happened was at the edges of the day. Early mornings, evenings, or the rare afternoon when the calendar happened to be free. That is not sustainable, and it is not necessary.
The most productive stretches I have experienced in my career have consistently been long, uninterrupted blocks of focused work. Distributed teams have the opportunity to build this in structurally. To agree on meeting-free hours, to batch synchronous time for the decisions that genuinely need human conversation, and to protect the rest.
Context Over Instructions
There is a useful distinction between communicating context and communicating instructions. Instructions tell someone what to do. Context tells them why, and what success looks like. When the team understands the why clearly enough, they can make good decisions in your absence without needing an instruction for each new situation.
Over-communicating context is one of the highest-leverage things a leader can do in a distributed setting. It is the gift that keeps giving long after the original message was written.
Channel Norms
Without agreed norms for which channel carries which kind of communication, responsiveness expectations tend to fill the vacuum. People assume everything needs an immediate reply because the channel being used implies urgency. That anxiety erodes autonomy and fragments focus.
A simple agreement about what belongs where, long-form documents for proposals and decisions, threaded channels for coordination, direct messages for time-sensitive matters, removes a surprising amount of low-level friction. The specific channels matter less than the shared understanding of what each one is for.