BQ-301b · Module 1
Async Communication Design
3 min read
Asynchronous communication — email, Slack, project management tools, recorded video — is where most professional communication happens and where most style-flexing is abandoned. The assumption is that async is just "information transfer" and style does not matter. The assumption is wrong. Async communication is received without the context cues of real-time interaction — no tone of voice, no facial expression, no ability to course-correct mid-message. Every word carries more weight because it is carrying the full interpretive burden alone.
Do This
- For high-D async receivers: front-load the action item, limit to three sentences for routine messages, use bold for key decisions
- For high-I async receivers: open with a personal connection, frame requests collaboratively, use their name
- For high-S async receivers: provide full context upfront, flag any changes from established process, give advance notice of upcoming changes
- For high-C async receivers: attach supporting evidence, explain your reasoning, invite their review with specific questions
Avoid This
- Send the same Slack message format to all recipients — one size fits nobody
- Rely on emoji and casual tone for high-C receivers — they interpret informality as imprecision
- Send long-form async messages to high-D receivers — they stopped reading after the first line
- Surprise high-S receivers with new information in async channels — they need time to process change