An Asynchronous Workday: Useful Updates Without Constant Meetings

All Remote Work Desk Editorial Desk

Picture the status meeting that runs thirty minutes so that each of six people can say they are still working on what they were working on yesterday. Some of that information may work better as a short written update that colleagues can read when they need it. An asynchronous workday replaces that kind of meeting with written updates people can act on later, and keeps live conversation for the moments that genuinely need it.

What the evidence does and does not say

It helps to be clear about what is known. A study of more than 61,000 Microsoft employees in the United States, led by Longqi Yang and published in Nature Human Behaviour, found that firm-wide remote work during the pandemic shifted communication toward asynchronous channels such as email and messaging and away from synchronous ones. It also found that collaboration became more siloed: according to UC Berkeley's Haas School of Business, which publicized the work of co-author David Holtz, the share of collaboration time spent with colleagues in other groups fell by about a quarter relative to its pre-pandemic level. That second finding matters, because moving work into writing does not automatically keep people connected across teams. The study covered one company during an exceptional period, so it describes a pattern rather than a rule.

A much smaller Microsoft Human Factors Lab study, with 14 participants, measured brain activity during video meetings and reported a different pattern in EEG signals associated with stress when meetings included breaks, compared with four meetings back to back. With so few people and ten-minute meditation breaks as the standardized activity, it is better read as a prompt to protect gaps than as proof of a precise effect.

The software company 37signals describes its own approach in a public guide to internal communication. It treats asynchronous communication as the default and real-time as occasional, favors long-form writing over chat for anything substantive, and notes that an hour-long meeting with five people consumes five hours of collective time. That is one company's practice, not research, but it states the idea clearly.

Write updates that stand on their own

The core skill of async work is writing a message that does not need you present to be understood. A useful update usually answers four questions: what changed since last time, what is next, what is blocked, and what you need from whom by when. Putting the request in the first lines matters more than polish, because a reader skimming a dozen updates will act on the ones that make the ask obvious.

Keep updates where the work lives. A note attached to the project, ticket or shared document is easier to find next week than one buried in a chat stream, a point 37signals makes when it contrasts writing that persists with chat that scrolls away.

A hypothetical update

Here is the shape of a good one, written by an imagined analyst at the end of their morning. Done: cleaned the March sales data and flagged three duplicate accounts in the shared sheet. Next: building the regional summary this afternoon. Blocked: need confirmation from Priya on whether returns count against regional totals, ideally by tomorrow noon. No meeting needed unless the answer changes the scope. Anyone reading it later knows what to do, and Priya can answer in a sentence.

Shape the day around focus and response windows

Async does not mean unreachable. It means agreeing when people check in so nobody feels pressure to watch notifications all day. A team could agree on two or three response windows, for example late morning and mid-afternoon, with focused work between them. Urgent issues get a separate, clearly defined channel, so everything else can wait without anxiety. If you still have several meetings, leaving space between them by ending calls five or ten minutes early is a small change most calendars can support.

Know when to switch to a live conversation

A conversation is often better when a thread has gone back and forth several times without converging, when a decision involves tension or disappointment, when someone new needs context quickly, or when a problem is urgent and delay is costly. A good habit is to switch to a short call, then write a summary afterward so the decision lands back in the shared record.

Tradeoffs worth naming

Long written updates can create barriers when readers need more context, language support or another format. Some decisions also benefit from discussion in real time. The Microsoft study's finding about narrower collaboration networks is a reason to preserve cross-team contact, although it does not prove that written updates themselves caused that change. Offer a way to ask questions, and plan occasional live sessions when they serve a clear purpose.

Start small. Replace one recurring status meeting with a written update for a month, keep the slot free as focus time, and then ask the team whether anything important was missed. The answer will tell you more than any general rule.

Sources

Microsoft Research, The effects of remote work on collaboration among information workers: https://www.microsoft.com/en-us/research/publication/the-effects-of-remote-work-on-collaboration-among-information-workers/ Berkeley Haas Newsroom, When everyone works remotely, communication and collaboration suffer, study finds: https://newsroom.haas.berkeley.edu/research/when-everyone-works-remotely-communication-and-collaboration-suffer-study-finds/ Microsoft WorkLab, Research Proves Your Brain Needs Breaks: https://www.microsoft.com/en-us/worklab/work-trend-index/brain-research 37signals, Guide to Internal Communication: https://basecamp.com/guides/how-we-communicate