Async-First Doesn’t Mean Async-Only

“异步优先”并不意味着“只能异步”

Key Takeaways 核心要点

Asynchronous discussions can lose momentum because participants are focused on different tasks. For complex or important topics, it’s often better to switch to synchronous communication. At least in my experience working in a Japanese-speaking organization, AI-generated messages are often still too verbose to send as-is. As writing becomes cheaper, it’s even more important to reduce the cognitive load on readers. Async-first does not mean async-only. Keeping written records while introducing short meetings when necessary can reduce the overall cost of communication. 异步讨论可能会因为参与者专注于不同任务而失去动力。对于复杂或重要的话题，切换到同步沟通往往效果更好。至少在我于一家日语工作环境的公司任职的经验来看，AI 生成的消息通常过于冗长，无法直接发送。随着写作成本的降低，减轻读者的认知负担变得愈发重要。“异步优先”并不意味着“只能异步”。在保持书面记录的同时，在必要时引入简短会议，可以降低整体沟通成本。

Context 背景

I currently work from Vancouver, Canada, for a fully remote and fully flexible organization based in Japan. Since everyone works on their own schedule, much of our day-to-day communication, decision-making, and discussion happens asynchronously. There are many benefits to this way of working. People can think at their own pace, and discussions naturally leave a written record. As someone who is fairly introverted, I also appreciate having time to think through my ideas before sharing them. Recently, however, I’ve started to realize that keeping every discussion asynchronous is not always the most efficient approach. 我目前在加拿大温哥华工作，服务于一家总部位于日本、完全远程且时间高度灵活的公司。由于每个人都有自己的工作时间表，我们大部分的日常沟通、决策和讨论都是异步进行的。这种工作方式有很多好处：人们可以按照自己的节奏思考，讨论也会自然地留下书面记录。作为一个比较内向的人，我也很庆幸在分享想法之前有时间进行深思熟虑。然而最近，我开始意识到，将所有讨论都保持在异步状态并不总是最高效的方法。

Complex discussions are expensive to read 复杂的讨论阅读成本很高

When discussing multiple options, I usually start by sharing my recommendation, then document the reasoning behind it and the pros and cons of alternative approaches. The more complicated the topic becomes, the longer the document becomes. Writing requires effort, but so does reading. Someone has to understand the background, process the trade-offs, form an opinion, and respond. Lately, I’ve become more aware of the reader’s cost than the writer’s. In our company, Japanese is the shared language, and much of our written communication is now assisted by AI. While AI makes it easier to produce long documents, the resulting text can still be unnecessarily verbose or difficult to follow. AI makes writing cheaper. It does not necessarily make reading cheaper. On top of that, everyone already has their own priorities. When a message arrives, people are often in the middle of something else. Replies become spread out over hours or days. Discussions can lose momentum, and important but non-urgent topics may eventually fade away without reaching a conclusion. 在讨论多个选项时，我通常会先分享我的建议，然后记录背后的逻辑以及其他方案的优缺点。话题越复杂，文档就越长。写作需要付出努力，阅读也是如此。对方必须理解背景、权衡利弊、形成观点并做出回应。最近，我比以往更关注读者的成本而非作者的成本。在我们公司，日语是通用语言，我们大部分的书面沟通现在都有 AI 辅助。虽然 AI 让撰写长文档变得更容易，但生成的文本往往显得过于冗长或难以理解。AI 降低了写作成本，但并不一定降低了阅读成本。此外，每个人都有自己的优先级。当消息送达时，人们往往正忙于其他事情。回复变得断断续续，跨越数小时甚至数天。讨论可能会失去动力，而那些重要但不紧急的话题最终可能会在没有结论的情况下不了了之。

Write first, then talk 先写后谈

To address this, I’ve started scheduling short meetings whenever a discussion becomes too complex to resolve asynchronously. This doesn’t mean abandoning written communication. I still document the background, context, and available options. AI helps me draft these documents quickly, but I always review and simplify them before sharing. Once everyone has the necessary context, a short meeting allows the team to focus on the same problem at the same time. I’ve found that questions that would otherwise require many rounds of messages can often be resolved in just a few minutes of conversation. There’s another benefit as well. In a fully remote, fully flexible environment, opportunities to talk to teammates naturally become less frequent. Even when the purpose is purely technical, real-time conversations can help build mutual understanding and trust. 为了解决这个问题，每当讨论变得过于复杂而无法通过异步方式解决时，我就会安排简短的会议。这并不意味着放弃书面沟通。我仍然会记录背景、上下文和可选方案。AI 帮助我快速起草这些文档，但在分享之前，我总是会进行审阅和简化。一旦每个人都掌握了必要的背景信息，简短的会议就能让团队在同一时间专注于同一个问题。我发现，原本需要多轮消息往返才能解决的问题，往往只需几分钟的交谈就能搞定。此外还有另一个好处：在完全远程、高度灵活的环境中，与队友交谈的机会自然会减少。即使目的纯粹是技术性的，实时对话也有助于建立相互理解和信任。

Async-first doesn’t mean avoiding meetings “异步优先”并不意味着避免会议

I used to believe that if a team was designed around asynchronous communication, then most discussions should stay asynchronous. I don’t think that anymore. Asynchronous communication is a tool, not the goal. If a topic is simple, asynchronous communication works well. If a discussion becomes complex, stalls, or requires multiple rounds of clarification, a short synchronous conversation can be the more efficient option. I’ve learned not to hesitate to schedule a meeting when it helps move an important discussion forward. Being async-first doesn’t mean avoiding synchronous communication. It means choosing the communication style that minimizes the overall cost for the team. 我曾经认为，如果一个团队是围绕异步沟通设计的，那么大多数讨论都应该保持异步。我现在不再这样认为了。异步沟通是一种工具，而不是目标。如果话题简单，异步沟通效果很好；如果讨论变得复杂、停滞不前或需要多轮澄清，简短的同步对话往往是更高效的选择。我学会了在有助于推动重要讨论进展时，不要犹豫去安排会议。“异步优先”并不意味着避免同步沟通，而是意味着选择一种能为团队降低整体成本的沟通方式。