“Can you take a quick look at this?” The message arrives between tasks, accompanied by a link. Look at what? To correct it, approve it or simply read it? And does “quick” mean before noon or sometime this week? In a hybrid team, these few words can trigger a cascade of follow-ups. Working asynchronously is not just about responding at different times: it means learning to write for someone who shares neither our context nor our availability. Looking ahead to September 2026, this skill deserves as much attention as verbal communication skills.
The office no longer fills in all the gaps
When working remotely, conversational shortcuts become apparent. In the office, a glance, a clarification offered in passing or the memory of a discussion can fill in the gaps. On a messaging platform, recipients often have to piece together the intent on their own. They hesitate, interrupt a colleague or wait. The problem is therefore not just about information: silence can be interpreted as disinterest, terse wording as criticism, and a follow-up as monitoring.
The documented practices of distributed companies such as GitLab and Automattic have popularized a different approach: making context accessible without requiring people to be present at the same time. Their experience does not offer a universal formula, but it does highlight an important shift. Writing is no longer merely the administrative record of work. It is becoming one of its main spaces for coordination. Collaborative tools support this shift; they guarantee neither clear messages nor good working relationships.
A good request reduces invisible work
Imagine a marketing manager asking a developer to modify a page. “The form needs revisiting” forces the developer to investigate. A request with context specifies the problem observed, the desired outcome, the constraints and the deadline. It also distinguishes what is established from what still needs checking. This small effort avoids passing the entire burden of clarification to the recipient, then blaming them for not understanding quickly enough.
A more useful formulation would be: “Several reports from support point to a problem on mobile. Can you check how the form behaves and suggest a fix before Thursday? We want to reduce abandonment without adding another field. If the deadline is too tight, let me know on Wednesday what is feasible.” This fictional example does not aspire to literary elegance. It provides a reason, an expected action and room to negotiate.
Four things to check before sending
- Context: why is this request being made, and what reference document supports it?
- Expectations: is the task to inform, comment, recommend, approve or execute?
- Timing: when will the response be useful, and why?
- Room for maneuver: what is open to discussion, and who makes the final call?
These checkpoints are not a mandatory form. For a simple question, two sentences are enough. The key is proportion: enough information to act, but not so much detail that the request gets buried. Putting the expected action first, then providing a link to the context, also respects the reader’s attention.
Explaining a decision means preserving trust
A decision announced without any reasoning can easily look like an arbitrary order. “We are dropping this approach” leaves everyone to imagine the reasons: work deemed inadequate, personal preference or internal politics. In an asynchronous setting, people cannot necessarily ask the question that clears up the misunderstanding straight away. Documenting the reasoning therefore becomes an act of relationship-building, particularly when colleagues have invested time in the option being set aside.
A useful record sets out the problem being addressed, the main options, the criteria used and the consequences. It also specifies the status of the decision: an open proposal, a temporary trial or a decision to be implemented. This distinction avoids a familiar problem in hybrid teams: some people think the discussion is still ongoing while others have already started implementing the decision. Adding the conditions for a possible review makes it possible to remain consistent without presenting every choice as irreversible.
Still, the temptation to produce an endless dossier must be resisted. For a routine decision, a paragraph may be enough. For a major strategic choice, a lasting document is preferable to fifty scattered messages. What matters most is not length, but the ability to find the reasoning, its author and its date.
Clarity does not remove the need for tact
Writing precisely is not a license to write harshly. “This document is incomplete” passes an overall judgment. “The cost assumptions needed to compare the two options are missing” identifies an observable obstacle. The second formulation makes it easier to respond because it separates the person from the problem. It can be firm without forcing the recipient to defend their competence or goodwill first.
Tact does not mean adding so many caveats that the request becomes unreadable, either. A disagreement is more productive when it names the issue: “I do not recommend this schedule because the testing phase seems insufficient to me.” An alternative can then be proposed, or missing information requested. Emojis and friendly language can help, but they cannot fix a contradictory instruction or an ill-judged public criticism.
Fewer meetings, not less conversation
Asynchronous work becomes counterproductive when it turns every exchange into a laborious writing exercise. An escalating conflict, strong emotions or a question that is still very unclear often warrant a call. The right instinct is not to defend text at all costs, but to choose the channel that genuinely reduces uncertainty. After the conversation, a short written summary records the commitments and prevents multiple versions of the agreement from circulating.
This flexibility requires shared rules. What response times are normal? Which channel signals a genuine emergency? Where can decisions be found? Without these conventions, messaging perpetuates constant availability under a misleading label. A team is not asynchronous if everyone has to monitor their notifications to prove they are working. Managers must demonstrate that a delayed response, within the agreed timeframe, does not signal a lack of commitment.
AI can rephrase, but it cannot take responsibility for the relationship
Generative AI assistants already offer to summarize exchanges, organize a note or soften a message. Their widespread adoption is a plausible prospect for hybrid teams by September 2026, without assuming uniform usage. They can help spot a missing deadline or an unclear instruction. But fluent prose can also conceal weak reasoning, erase a useful disagreement or introduce unjustified confidence.
The skill therefore remains a human one: checking facts, preserving nuance and taking responsibility for what is sent. A tool does not necessarily know that a colleague has just been through three changes in priorities. Rereading from the recipient’s perspective remains essential: what will they understand, what must they do, and what burden is being placed on them?
What now? Organizations would benefit from training their teams using real messages rather than handing out abstract communication guidelines. Rewriting an unclear request, documenting a decision, agreeing on a deadline: these modest exercises can change day-to-day working life. The next step could be to assess professional writing not by its elegance, but by its ability to enable action and reduce the burden of collaboration. Less writing to cover ourselves; better writing to work together.
