Async coordination without the chaos.
Async is not the absence of communication — it's communication shaped differently. A small set of rituals that keep distributed teams moving without burning anyone out.
The teams that struggle with async aren’t talking too little. They’re talking a great deal — just in a way that doesn’t add up. Threads scatter, decisions get re-litigated, and at the end of the week nobody can say with confidence what was actually agreed.
I’ve spent the last few years inside teams distributed across Bali, London, Manila, and Singapore. The good ones are not the ones with the fewest messages. They’re the ones where the messages they do send hold their shape for longer than the time zone they were written in.
The misconception.
Most founders move to async because they want fewer meetings. The unspoken hope is that async will mean less communication overall. It rarely does. Done well, async means slightly more communication, but it’s written down, structured, and durable. Done badly, it means the same volume of communication but no record of what was said.
Real async needs rituals. Not in the heavy corporate sense — in the small, repeated, voluntary sense. A few things the team does the same way every week, so nobody has to think about how to think about coordination.
The asynchronous workplace is not a workplace without communication. It is a workplace where communication is treated as a record, not a moment.
— MATT MULLENWEG, ON DISTRIBUTED WORK
The Monday brief.
One paragraph per person, posted by end of their Monday, in a single channel. Three lines is plenty: what I’m working on this week, what I need from anyone, and one thing I’m uncertain about.
The brief is short on purpose. It’s not a status report — status reports are written for managers. The Monday brief is written for the rest of the team, so they can plan their own week around it. The “uncertain” line is the most valuable part: it surfaces the things that would otherwise sit unsaid until they became a problem on Thursday.
The Friday close-out.
Same format, mirrored. What shipped, what stuck, what’s carrying over. The close-out lives in the same channel as the brief, threaded under the original post if your tool allows it. By Friday evening, anyone scrolling the channel can see a clean picture of the week.
I tell teams to write the close-out in five minutes, not fifteen. The instinct is to use it as a wrap-up document — to explain, to justify, to add context. Resist that. The close-out works because it’s fast. The moment it becomes a chore, it stops getting written, and the whole system starts to leak.
The decision log.
This is the one most teams skip, and it’s the one that matters most for async sanity. Every meaningful decision — a tool change, a vendor choice, a scope cut — goes into a single document, one line each, with the date and the person who made it.
The decision log is not for discussion. It’s for memory. Three months from now, when someone asks “wait, why did we move off the old CRM?”, the answer is one search away. Without a decision log, you don’t have an answer; you have an oral history, and oral histories drift.
What goes in.
- The decision, in one sentence
- The date it was made
- The person or people who made it
- A link to the conversation, if there was one
What doesn’t go in: the debate, the alternatives, the reasoning in detail. Those belong in the thread you linked to. The log itself stays scannable.
The 24-hour rule on questions.
If you ask a teammate something that requires more than a yes or no, you give them 24 of their working hours to respond. Not your hours — theirs. Anyone in the team can mark a question “this one’s urgent” but the assumption is that urgency is rare.
This sounds slow until you’ve worked inside it. What you trade away is the feeling of getting a fast answer at any moment. What you get back is two things: people who actually do deep work, and answers that have been thought about for more than three minutes.
Default to public.
Direct messages are for personal things — checking in on a colleague, confidential matters, the occasional logistics question. Everything else goes in a shared channel where it can be searched later, where others can learn from the answer, where context lives in one place.
Most async teams underuse this. They drift back into DMs because DMs feel polite — you’re not bothering the wider group. The cost shows up weeks later, when the same question gets asked again by someone else who couldn’t find the first answer because it was hidden in a private thread.
What I tell founders new to async.
Pick two of these rituals. Not all five. The Monday brief and the decision log are usually the right place to start — they cost the least and return the most. Run them for a month before adding anything else.
And give it time. Async coordination is not a tool change; it’s a habit change. The teams I’ve seen succeed at it didn’t do anything clever in the first two weeks. They did the same small things, the same way, until those things became invisible. That’s the goal.