Remote work
Async or sync: which work belongs in a meeting
Distributed teams tend to arrive at one of two failure modes: everything becomes a call, or nothing does. The line between them is more specific than 'default to async'.
What synchronous time is actually good at
Three things: resolving disagreement, building shared understanding of something genuinely complicated, and anything where how it is said matters as much as what is said.
All three depend on immediate back-and-forth. You say something, watch it land, and adjust. Writing cannot do that, and pretending it can is how a disagreement becomes a forty-message thread that ends where it started.
What written work is better at
Anything that benefits from being thought about before it is answered. Proposals, reasoning, trade-offs, anything with numbers in it. Writing forces the author to be specific in a way that talking does not, and the reader gets to go at their own pace.
It also has a property meetings never will: it exists afterwards. Six months on, the decision and the reasoning are both still there, which is worth more than most teams account for.
The first failure mode: everything is a call
When a team goes remote, the informal conversations that used to happen in passing have nowhere to go, so they become scheduled calls. The calendar fills with fifteen-minute syncs that each replace something that used to cost ninety seconds.
The cost is not the meetings. It is that they land in the narrow window where everyone is awake at once, which is also the only window in which anything genuinely synchronous can happen. Filling it with things that could have been written is how the important call ends up three weeks out.
Settle the time without the thread
Propose a few slots, share one link, and let the group vote. Guests never sign up.
The second failure mode: nothing is
The overcorrection is worse and takes longer to notice. Disagreements that would have taken twenty minutes stretch across days of careful messages, each one a little more defensive than the last, because nobody wants to be the one who escalates to a call.
The tell is a thread that has gone four rounds without converging. At that point more writing will not help, and the twenty minutes is cheap.
Protecting the overlap window
If a team spans time zones, the hours everyone shares are the scarcest resource it has. Treating them as ordinary calendar space is the single most expensive mistake distributed teams make.
Two rules cover most of it. Nothing goes in the overlap window that could have been written. And rotate which side of the world takes the awkward hour, so the cost is shared rather than always paid by the same people — which is what quietly makes one office's opinions count more than another's.
When you do need the call
Send the context first and say what the call decides. A synchronous hour spent explaining what a document already said is the worst of both approaches.
And propose times rather than picking one, because no calendar system can see the availability of people outside your organisation, and in a distributed team that is often most of the people you need.