Async work done right

Async work gets sold as a perk: no meetings, work whenever you like. Then teams try it, replace their standups with a firehose of Slack messages, and wonder why everyone feels more interrupted than before. They kept the expectation of instant replies and just moved it to a new app.

Async isn't a tool choice. It's a set of habits that let people do focused work without waiting on each other. Three of them carry most of the weight.

Write things down where they can be found

The core move of async work is turning conversations into documents. A decision made in a call lives only in the memory of whoever was there. A decision written in a shared doc is available to everyone, forever, including the person who joins next month.

So write down the things that would otherwise need a meeting:

• Decisions. What we chose, the options we rejected, and why. The "why" is what saves you from relitigating it in six weeks.
• Project state. What's done, what's in progress, what's blocked and on whom. One place, updated as things change, not a status recited live every morning.
• How things work. The steps to ship, the accounts involved, the gotchas. Every question you answer twice is a doc you should have written once.

The test of good async writing is simple: could someone act on this without asking a follow-up question? If not, add the missing context now. You're trading five minutes of writing for a day of back-and-forth across time zones.

Design for overlap, not for "always on"

Fully async — where nobody is ever expected to be online at the same time — sounds ideal and works badly. Some things genuinely need a live conversation: a tricky design call, a tense bit of feedback, the first day of a new project. Zero overlap means those either don't happen or happen badly over text.

The workable version is a few hours of shared time and hard boundaries around the rest:

• Agree on an overlap window — even two or three hours — when live conversation is fair game. Outside it, no one owes an instant reply.
• Set a real expectation for response time. "Within one working day" is async. "Within ten minutes" is a meeting you haven't scheduled.
• Batch your own messages. Instead of firing off six questions as they occur to you, collect them and send one considered message. Every ping is an interruption to someone's focus block.

Overlap is for the handful of things that need it. Everything else waits, on purpose.

Trust people to close the loop

The habit that quietly kills async teams is checking in. If a manager needs to know what everyone's doing right now, the team drifts back to status meetings and "quick calls," and the async gains evaporate.

Async runs on trust and clear ownership instead of supervision:

• Every task has one owner. Not a group that might pick it up — one named person responsible for moving it or flagging that they can't.
• Owners post updates without being asked. A short note when something ships, stalls, or changes. The update replaces the check-in.
• Blocked means say so, loudly. The worst async failure is silent waiting — someone stuck for two days who never said they were stuck. Raising a blocker fast is a sign the system is working, not that you've failed.

Judge the work by what gets delivered, not by who was green on Slack at 2pm. Presence and progress are not the same thing, and async only pays off once a team stops confusing them.

The quiet payoff

Get these three habits right — write it down, protect a small overlap, trust people to own their work — and async stops feeling like a compromise. Deep work gets long uninterrupted stretches. Time zones stop being a tax. New people onboard by reading instead of interrupting.

None of it comes from the tools. Slack, docs, and a shared calendar are the same whether a team is frantic or calm. The difference is whether people have agreed to write clearly, wait patiently, and trust each other to close the loop. That agreement is the actual product of async work — the meetings you don't have are just the receipt.