Async vs sync communication: when to type and when to talk
Most teams argue about async versus sync as if they had to pick one. They don't. The useful question is smaller: for this one message, should I type it or say it? A team that can answer that quickly, and switch without ceremony, gets the good parts of both.
A simple rule for each message
Type it when the answer can wait and someone will want to find it later. A decision, an owner, a link, a number, a blocker. Text is slower to produce, but it stays put. The person who joins next month can search for it.
Talk it out when the back-and-forth would take longer than the answer. A question with three follow-ups. A design choice where tone matters. Anything where you would otherwise write "can we hop on a call?" Voice is fast and clears up ambiguity in a sentence or two, but it disappears the moment it ends.
So the rule has two halves:
- Type what needs to be kept.
- Talk what needs to be settled.
- Write down what the talk settled, in the place the typed version would have gone.
The third line is the one most teams skip.
Where the old setup makes it slow
In a typical setup, typing happens in a chat app and talking happens in a calendar. Switching from one to the other means finding a time, sending an invite, and waiting. A question that needed ninety seconds of voice turns into a thirty-minute slot tomorrow afternoon. So people stay in text longer than they should, and a thread grows to forty replies that one short conversation would have settled.
When the call does happen, its result often lives in the heads of whoever was on it. Somebody says they will send a recap. Recaps that land in the channel covers what usually happens next.
Switching in seconds in Bullpen
In Bullpen, the walk-in voice room beside the channel stays open. When a thread starts going in circles, someone says "in the room", and whoever is free joins. No invite, no link to paste, no waiting for a slot. Walk-in voice rooms at work explains how that room works day to day.
When the talking is done, notes from the room post back to the channel it belongs to. The decision lands next to the thread that raised it, as text, where search can find it. Sync settles the question, and the channel keeps the record.
AI helpers sit on the channel's roster, so the async side keeps moving too. Ask Scout what was decided about the pricing page last week, and the answer comes back in the thread with a link to the message it came from. Someone who missed the conversation can catch up in text, on their own time. AI helpers that cite the message explains why that link matters.
The result is a team that types by default, talks when it helps, and never has to choose a side.
Try the rule this week
Next time a thread passes ten replies without an answer, move it to the walk-in voice room, settle it, and post the one-line outcome back in the thread.