--- title: "Async communication that works — Leadership & Communication" description: "Why async is a leadership skill Asynchronous (async) communication means people contribute at different times: written proposals, comments on documents…" url: https://optimizeall.com/learn/leadership-and-communication/async-communication updated: 2026-10-05 --- Leadership & Communication · Leading in the AI era: agents, async and responsible AI · lesson 20 of 21 · 15 min # Async communication that works ## Why async is a leadership skill Asynchronous (async) communication means people contribute at different times: written proposals, comments on documents, recorded video walkthroughs, threaded chat and status updates. Synchronous (sync) communication happens in real time: meetings, calls and live chat. Async is not "fewer meetings" as a slogan. It is a way of working that lets teams across time zones, shift patterns and caring responsibilities contribute fully, protects focus time and creates a written record of decisions. Some fully remote companies (GitLab is a well-known example with a public handbook) document an async-first approach in detail. You do not need to be fully remote to benefit: hybrid and office teams waste the same hours on status meetings and interruptions. ## When to use async and when to meet | Use async for | Use sync (meet) for | |---|---| | Status updates and progress reports | Building relationships, especially with new people | | Proposals that need thoughtful input | Conflict, sensitive or emotional topics | | Reviewing documents, designs, code | Complex problems with many unknowns (after a written pre-read) | | Decisions with a clear owner and deadline | Crises needing rapid coordination | | Sharing information and walkthroughs | Celebrations and team rituals | A useful default: **start async; escalate to a meeting when the thread goes in circles or emotions rise.** A good rule is "three rounds and we talk". ## The five building blocks 1. **A written proposal format with a comment deadline.** Owner, context, recommendation, options, open questions, decision date. Silence by the deadline counts as "no objection" only if the team has agreed that rule. 2. **Clear channel norms and response times.** For example: chat, same working day; documents, comment by the stated deadline; email, two working days; urgent, phone. Put them in the team working agreement. 3. **Threads per topic.** One thread per decision or issue, with a clear title. No decisions buried in direct messages. 4. **Recorded walkthroughs.** A 3–5 minute screen recording (for example with Loom, or the recording feature in Microsoft Teams, Zoom or Google Meet, depending on your tools) replaces many "can you walk me through it" meetings. Add a written summary; not everyone can watch video. 5. **A decision log.** Every decision gets a line: what, who decided, when, link to the thread. This is how async teams avoid re-litigating. ## Writing for async Async only works if messages can be understood without a follow-up call. Apply BLUF (bottom line up front), state exactly what you need from whom by when, include the context a reader in another time zone needs, and link to sources instead of saying "as discussed". Assume the reader has not been in any of your meetings. ## Worked example *Illustrative.* Farah leads an eight-person product team split between Karachi, Dubai and Toronto, with only a two-hour overlap. The daily stand-up was held at a time that suited Dubai, so Toronto joined at dawn and Karachi missed family dinners. She replaced it with an async stand-up in a chat thread by 10:00 local time (yesterday, today, blockers), a weekly 45-minute live meeting in the overlap for problem-solving and connection, and a proposal template with 48-hour comment windows. Blockers were now visible earlier, because they were written down, and the team regained several hours a week. ## Hands-on: three async templates **1. Async proposal (paste into a shared doc):** ```text PROPOSAL: [title] Owner: [name] Decide by: [date, time + time zone] Bottom line: I propose we ___. Context: why now; what problem; link to data Options: A (recommended) / B / do nothing — pros, cons, cost, risk Open questions: 1. ___ (I need input from ___) How to respond: comment in the doc by [deadline]. Say "agree", "agree with changes", or "object" with a reason. Silence = no objection (team norm). Decision rule: owner decides after comments / consent / escalate to ___ ``` **2. Async stand-up (in a thread, by an agreed local time):** ```text Yesterday: shipped X; reviewed Y Today: Z Blockers: waiting on data export from @name (needed by Thu) FYI: out Friday afternoon ``` **3. Recorded walkthrough script (for a 3–5 minute video):** ```text 0:00 What this is and what I need from you (decision/feedback) by when 0:30 Context in two sentences 1:00 Walk through the key screen/document (only what matters) 3:00 Options/risks 3:30 Repeat the ask and the deadline; link to the written summary ``` **AI support:** AI assistants in chat and document tools can summarise long threads and draft decision-log entries. Always have the decision owner check the summary before it is recorded, and follow your team's rules on which tools may process internal data. ## Measuring success Track time in meetings per person, time to decision, the proportion of decisions logged, blocked-work time and, in pulse surveys, whether people in every time zone feel able to contribute. ## Common mistakes - Replacing meetings with a flood of unstructured messages. - No deadlines, so proposals drift for weeks. - Expecting instant replies, which turns async into "sync with extra steps". - Videos with no written summary or no clear ask. - Decisions made in DMs and never logged. - Using async for conflict or sensitive feedback. ## Quick self-check Look at your last week. Which meeting could have been an async proposal or a recorded walkthrough? Which long thread should have become a 15-minute call? ## Video lecture: Async communication that works Lecture coming soon · 13 chapters · about 9 minutes. Read the full transcript below. 1. Async communication that works 2. Why it matters 3. Async or meet? 4. The family recipe book 5. Five building blocks 6. Writing for async 7. Worked example 1: Maya's shop (illustrative) 8. Worked example 2: Farah's team (illustrative) 9. AI and async 10. Watch me: an async proposal 11. Measuring success 12. Common mistakes 13. Recap and try this now ## Lecture transcript ### Async communication that works It's four in the afternoon in Toronto, one in the morning in Karachi, and nine in the morning in Dubai. Your team needs to agree on a product change. If the only way to decide is a meeting, someone joins at dawn or at midnight, or the decision waits a week. There's a better way. In this lecture you'll learn what asynchronous communication really is, when to use it and when to meet, the five building blocks of an async team, how to write for readers you'll never be online with, and three templates you can use tomorrow. ### Why it matters Why does this matter? Async isn't a slogan about fewer meetings. It's a way of working that lets people across time zones, shift patterns and caring responsibilities contribute fully. It protects focus time, because people aren't pulled into calls every hour. And it creates a written record, so decisions don't get lost or re-argued. Some fully remote companies, GitLab being a well-known example with a public handbook, document an async-first approach in detail. But you don't need to be fully remote. Hybrid and office teams waste the same hours on status meetings and interruptions. ### Async or meet? Here's the concept. Async means people contribute at different times: written proposals, comments on documents, recorded video walkthroughs, threaded chat and written updates. Sync means real time: meetings, calls and live chat. Neither is better. They're tools for different jobs. Use async for status updates, proposals that need thoughtful input, reviewing documents, decisions with a clear owner and deadline, and walkthroughs. Meet for building relationships, conflict and sensitive topics, messy problems with many unknowns, and genuine crises. Here's the key idea: start async, and move to a meeting when the thread goes in circles or emotions rise. Three rounds, and we talk. ### The family recipe book Here's an analogy. Think of the difference between a phone call and a well-run relay of letters in a family recipe book. A phone call is great for catching up and sorting out a disagreement. But when your grandmother's recipe passes through the family, each person adds a note in the margin: less sugar, bake ten minutes longer. Nobody needs to be in the kitchen at the same time, and the book keeps the history. Async communication is the recipe book. It's slower for any single exchange, but the whole family contributes and nothing gets lost. ### Five building blocks Now the five building blocks. One: a written proposal format with a comment deadline, including owner, context, recommendation, options and a decide-by date. Two: channel norms and response times, such as chat the same working day, documents by the stated deadline, and phone only for real urgency. Three: one thread per topic, with a clear title, and no team decisions buried in direct messages. Four: recorded walkthroughs of three to five minutes, always with a written summary. And five: a decision log, a single line per decision: what, who, when, and a link to the thread. That's how async teams avoid re-arguing. ### Writing for async Writing for async is its own skill. Assume your reader wasn't in any of your meetings and is reading at a different time of day. Put the bottom line first. State exactly what you need, from whom, and by when, including the time zone. Give just enough context, and link to sources instead of writing as discussed. Say how to respond: agree, agree with changes, or object with a reason. And agree as a team whether silence by the deadline counts as no objection. Without that rule, proposals drift for weeks. ### Worked example 1: Maya's shop (illustrative) A simple worked example. Maya runs a small online shop in Bristol with two part-time staff who work different days. Things keep falling through the gaps because handovers happen by quick chats when they overlap, which is rarely. She sets up one shared thread per topic, suppliers, orders and social posts, and a short written handover at the end of each shift: done, in progress, needs attention. Orders stop being missed within a fortnight, and nobody has to stay late to catch the next person. ### Worked example 2: Farah's team (illustrative) Now a realistic business scenario, illustrative. Farah leads an eight-person product team split across Karachi, Dubai and Toronto, with only two hours of overlap. The daily stand-up suits Dubai, so Toronto joins at dawn and Karachi misses family dinners. Farah replaces it with an async stand-up in a thread by ten in the morning local time: yesterday, today, blockers. She keeps one forty-five-minute live meeting a week in the overlap, for problem-solving and connection. Proposals get forty-eight-hour comment windows. Blockers now surface earlier, because they're written down, and the team wins back several hours a week. ### AI and async Where does AI fit? AI features in chat and document tools can summarise long threads, pull out open questions, and draft decision-log entries. That's genuinely useful when you come back from leave to two hundred messages. But the summary can miss nuance or state a decision that wasn't actually made. So the decision owner checks it before it's recorded. And follow your team's rules on which tools can process internal information. Also watch for the opposite problem: AI makes it easy to write long messages. In async, shorter and clearer wins. ### Watch me: an async proposal Watch me do it. I write an illustrative async proposal: move our monthly client report from a slide deck to a live dashboard. Bottom line: I propose we switch from the March report. Context: the deck takes two days to build, and clients ask for data between reports. Options: switch, keep the deck, or a hybrid. Open question for our analyst: can the dashboard handle client-level permissions? Decide by Thursday, five in the afternoon, UK time. How to respond: agree, agree with changes, or object with a reason. Then I record a three-minute walkthrough of a prototype, paste the link and a written summary, and post it in the reporting thread. ### Measuring success How do you measure success? Track meeting hours per person and time to decision. Look at the share of decisions that make it into the decision log. Watch blocked-work time. And in pulse surveys, split by location: do people in every time zone feel they can contribute and are kept informed? If proposals routinely miss their deadlines, or the same decisions get re-opened, tighten your norms rather than adding meetings back. ### Common mistakes Common mistakes. Replacing meetings with a flood of unstructured messages. Proposals without deadlines. Expecting instant replies, which turns async into sync with extra steps. Videos with no written summary or no clear ask. Decisions made in private messages and never logged. Using async for conflict or sensitive feedback. And a leader who says async-first, then calls everyone into ad hoc meetings. People copy what you do, not what you write in the working agreement. ### Recap and try this now Let's recap. Async lets everyone contribute, protects focus and records decisions. Start async, and move to a meeting after three rounds or when emotions rise. Build the five blocks: proposals with deadlines, channel norms, topic threads, short walkthroughs with summaries, and a decision log. Write so nobody needs a follow-up call. Use AI summaries, but have owners check them. Your try this now: convert one recurring status meeting into an async stand-up or written update for two weeks, using the templates in the lesson, then ask the team what to keep. Next, we'll look at using AI in everyday management responsibly. ## Key takeaways - Async lets people contribute across time zones and schedules, protects focus and creates a record of decisions. - Start async; move to a meeting when a thread goes in circles or emotions rise. - Use written proposals with comment deadlines, channel norms, topic threads, recorded walkthroughs and a decision log. - Write so nobody needs a follow-up call: bottom line first, clear ask, context and links. - Keep conflict, sensitive feedback and relationship-building for live conversations. ## Try it Convert one recurring status meeting into an async stand-up or written update for two weeks, then ask the team what worked and what to change. - [Previous: Leading teams that work with AI agents](https://optimizeall.com/learn/leadership-and-communication/leading-teams-that-use-ai-agents) - [Next: Using AI in everyday management, responsibly](https://optimizeall.com/learn/leadership-and-communication/ai-in-everyday-management) - [All lessons of Leadership & Communication](https://optimizeall.com/learn/leadership-and-communication)