Working async, explained
"Async" gets used to mean three different things. This guide separates them and gives you a working definition you can actually use in interviews and on the job.
The three definitions in the wild
- "Async" = "We use Slack." This is not async. This is synchronous communication on a tool with a delay button.
- "Async" = "We don't expect immediate replies." Closer. But still synchronous in practice if performance is implicitly evaluated on response time.
- "Async" = "Most decisions happen in writing, on a documented thread, with an explicit deadline for input." This is real async. Adopt this definition.
Why parents need real async
The parent calendar is not a delay; it is a schedule. You are not "slow to respond" between 3pm and 5pm — you are doing pickup. A team built on real async treats your 5pm reply the same way it treats a colleague's 11am reply: as the moment they got to it. A team built on Slack-with-a-delay-button does not, even if it claims to.
What real async looks like in practice
- Decisions are proposed in a written document with a clear deadline (24h, 72h, one week).
- Input is collected in writing, on the document or in a thread linked to it.
- Meetings are reserved for things that genuinely require real-time back-and-forth — usually creative work, hard conflict resolution, or onboarding.
- Status updates are written, weekly, in a consistent format. They are not Slack performances of busyness.
- Working hours are published per person, in a shared place, and respected.
How to evaluate a team's async claim in interviews
Three questions get you ninety percent of the truth:
- "Walk me through the last significant decision the team made. Where did it happen?" If the answer is "in a meeting," it's a synchronous team.
- "What's the team's expectation on Slack response time?" If the answer is "as soon as you see it," it's a synchronous team.
- "Can you show me a recent written proposal or RFC?" If they can't, the team's writing muscle is underdeveloped and async will be performative.
How to be a great async teammate
Write more than you think you need to. Default to the document, not the DM. When you do meet, send a written agenda 24 hours ahead and a written decision summary within 24 hours after. Publish your hours and your "I'm offline now" times. Reply to threads even when your reply is "agreed, no objections" — silence reads as ambiguity in writing-first cultures.
The most underrated async skill
Tight subject lines and clear first sentences. The first 12 words of your message determine whether it gets read carefully or skimmed. Front-load the ask, the deadline, and the level of input you need. "Decision needed by Thursday: which vendor?" is worth ten times "Hey when you get a chance can we chat about a thing."
What async cannot do
Async is not a substitute for trust, for clear priorities, or for a manager who knows how to give feedback. It will not save a chaotic team, and it will not rescue a role that is fundamentally a synchronous job pretending to be a remote one. If the underlying work shape requires four hours of real-time presence per day, no amount of "we use async" will make it parent-friendly.