Async vs sync — when to use which
What you'll learn
Async by default; sync for the human moments.
- Async-default for status, plans, decisions with > 3 readers.
- Sync-default for feedback, conflict, recognition, ambiguous topics.
- Write async first; promote to sync when you can't finish the message.
Pick async when the response can wait a few hours, the audience is more than three, or the topic benefits from people thinking in writing. Pick sync when the topic is high-stakes, requires back-and-forth iteration, or involves an interpersonal moment (feedback, conflict, recognition).
Defaulting to sync (meetings) for everything is the dominant failure mode. Defaulting to async for everything is the equal-and-opposite failure mode — async feedback delivered without warmth lands as cold; async conflict festers without a real-time pressure-valve.
Practical heuristic: write the message async first. If you find yourself writing 'I think it'd be easier to chat about this', that's the moment to schedule the sync — but with a written agenda derived from the draft you just wrote.
Key points
- Async-default for status, plans, decisions with > 3 readers.
- Sync-default for feedback, conflict, recognition, ambiguous topics.
- Write async first; promote to sync when you can't finish the message.
Pitfalls
- Calling a 'quick sync' for what could have been a 5-sentence message.
- Delivering hard feedback async — the words land flatter than intended.
Image descriptions
- async-sync-quadrant
- A two-by-two quadrant labelled 'audience size' on the horizontal axis and 'stakes' on the vertical. The top-right cell (large audience, high stakes) is shaded as async-with-sync-decision; the top-left (small audience, high stakes) sits squarely in the sync column; the bottom-left (small audience, low stakes) is informal sync; the bottom-right (large audience, low stakes) is pure async.
Ask your L&D team
In a real Adept rollout this routes to your company's L&D Claude project; in the demo it opens a fresh Claude chat.