Async vs Sync Communication
Level 4 Β· Talking to your own staff
When to send a message and when to hold a meeting. What live and written work each cost, how a firm plans its news, and the rules that keep chat useful.
Course contentsLesson 8 of 8
Level 1 Β· Point first
Level 2 Β· Work documents
Level 3 Β· Presentations
Level 4 Β· Talking to your own staff
After this lesson you can
- Choose between a live meeting and a written message
- Explain what a meeting costs in focused time
- Set reply rules that keep async work async
11 mincovers 3 glossary entries
Worth reading first: Meeting Agendas and All-Hands
When to send a message and when to hold a meeting
Synchronous communication happens with everyone there at once, like a meeting or a call. The asynchronous kind is sent now and answered later, like an email, a shared file or a chat message. A firm uses both to share news and plans with its own staff. Most teams need a mix of the two.
Sync talk is fast for things that need back and forth. A hard choice, a fresh idea, or news that will upset people goes better live. Tone and faces carry meaning that text loses. The cost is that everyone must stop what they are doing at the same moment.
Async talk lets people answer when they are free. It suits updates, questions that can wait a few hours, and teams spread across time zones. A question posted at nine in London can be answered at noon in New York, with no one up at midnight. It also leaves a written record.
Every live meeting breaks the day into pieces. A one-hour meeting at 11 can cost a coder the whole morning. Deep work needs long stretches with no breaks. Teams that move updates to async often find they need fewer meetings, and get more done in the hours left.
Internal communications is the plan for how news reaches staff. Big news goes out in an all-hands or a memo first, so staff do not hear it from the press. Updates go into a regular channel people know to check. Each kind of message gets one home, so people know where to look.
Good async needs a few rules. Say how fast a reply is expected: within a day, not within minutes. Write messages that stand alone, with the context and the ask in one place. Switch to a live call when a thread runs to five or so replies with no answer.
The common mistake is treating chat as if it were a meeting. A team that expects a reply to every chat at once has made async into sync. It gets none of the focus a real meeting gives. Drop the need for quick replies, and the tool is useful again.
Which one to use
- 1
Synchronous
Use it when a choice needs back and forth, or when news needs a face to go with it.
- 2
Asynchronous
Use it for updates, questions that can wait, and people in other time zones.
Worked example
A team across three time zones
A ten-person team works from London, New York and Singapore. Its daily call meant someone was always up at midnight.
They moved the daily update to a written thread and kept one live call a week for decisions. Nobody works at midnight now, and the weekly call is shorter.
The words for this lesson3
Check yourself
A team is spread across London and Singapore. How should it share daily updates?
Finished this lesson?
Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.