Async by Default: Writing Culture Beats Meeting Culture

Asynchronous work became a fashionable idea in 2017 and was widely misunderstood as a scheduling preference. It is not. An async-by-default operating model is a decision about where authority lives and how information moves, and organisations that adopted the vocabulary without changing either got the worst of both arrangements: fewer meetings and slower decisions. The argument in its favour was straightforward. Meetings consume the most expensive hours in the company, produce no durable record, exclude anyone absent, require everyone present to move at the pace of the slowest exchange, and fragment the remaining day into intervals too short for demanding work. Writing inverts every one of those properties. A well-written proposal takes an hour to produce and three minutes to read, can be reviewed by twelve people in their own time, and survives as the explanation for why the decision was made. What the advocacy generally omitted is that writing is harder, slower to produce, and pushes work onto the person initiating rather than distributing it around a table. That is the actual trade, and it is a good one — provided the organisation is willing to make it explicit.

The three things async requires

Written decision authority. This is the load-bearing element and the one most often absent. If a proposal can be written, circulated, commented on and then still requires a meeting for someone senior to agree verbally, the writing was added work rather than substituted work. Async functions only when a document can be the decision — which means specifying who decides, what constitutes approval, and what a non-response means after a stated interval. Organisations that did not answer the last question found that documents simply waited. Documentation as the default, not the archive. In a synchronous organisation, the meeting is where things happen and notes are a courtesy. In an async organisation, the document is where things happen and the meeting is the exception. That inverts the incentive: people write because writing is how work gets done, not because someone asked for minutes. Explicit response expectations. Asynchronous does not mean whenever. Without a stated norm — comments within one working day, decisions within three — async degrades into indefinite delay, and the people who suffer are those waiting for an answer to proceed. The most common failure of async adoption is not resistance; it is the absence of a clock.

What stays synchronous

The strong version of the async argument overreaches, and the organisations that did this well were clear about the exceptions. Disagreement with substance behind it resolves faster in conversation, because the real objection usually surfaces only after two or three exchanges. Early ambiguity — where the problem is not yet defined — benefits from the speed of interruption. Anything involving personal difficulty, performance, or emotional content belongs in a conversation, and putting it in writing is a management failure rather than an efficiency gain. Relationship formation for new joiners and new teams needs synchronous time; async works well among people who already trust each other and poorly among strangers. And genuine crisis coordination requires a room, virtual or otherwise. The workable pattern that emerged was async for proposals, status, decisions and documentation; synchronous for disagreement, ambiguity, difficult conversations and crisis. Stated that plainly, most organisations can identify half their recurring meetings as candidates for removal within an afternoon.

Practical Guidance for Async Operating Model Design

• Specify who decides and what approval looks like, in writing. Without named decision rights, written proposals queue for a meeting and async adds work rather than replacing it.
• Set a response clock and a default for silence. Async without a stated interval becomes indefinite delay, which is worse than the meeting it replaced.
• Make the document the artefact of work, not the record of it. If writing happens after decisions, you have added documentation overhead to a synchronous organisation.
• Name the categories that stay synchronous. Disagreement, ambiguity, personal matters and crisis — be explicit, or async becomes a way to avoid hard conversations.
• Have leaders write and comment visibly. Async adoption is determined almost entirely by whether senior people participate in writing or wait to be briefed verbally.
• Default meetings to 25 or 50 minutes and require a written input to hold one. The document requirement removes more meetings than any policy about calendars.
• Protect two-hour uninterrupted blocks and mean it. The benefit of fewer meetings only materialises if the reclaimed time is contiguous.
• Invest in where documents live and how they are found. An async organisation with poor information architecture rediscovers everything repeatedly.

The Regional Angle

Async-by-default runs into regional conditions that make parts of it easier and parts considerably harder, and the honest assessment is mixed. The calendar case is unusually strong here. A group operating across GCC markets already deals with differing weekend days, Ramadan working hours that compress the day substantially, Hajj and Eid periods, and — for organisations with shared service centres in Cairo, Manila or India — genuine time zone spread. The number of hours in which everyone is simultaneously available is small and shrinking, which is the clearest possible argument for written coordination. Groups that run synchronously across this pattern effectively conduct business in a two-hour window and wonder why decisions take weeks. Business culture cuts the other way, and pretending otherwise produces failed rollouts. Regional business runs substantially on relationship and personal presence: decisions are made in conversation, in the majlis, over coffee, on the phone, in the WhatsApp group. Hierarchy is generally more explicit than in Western firms, and written dissent from a junior colleague on a senior person's proposal carries social risk that the async literature — written largely by and for flat technology companies — never addresses. An organisation that mandates written decision-making without acknowledging this gets documents that record decisions made elsewhere, which is the worst outcome: full overhead, no benefit. WhatsApp is the practical incumbent and the sharpest tension. It is asynchronous in a technical sense and synchronous in every behavioural sense — instant, expectation-laden, unsearchable in practice, and invisible to the organisation. Moving proposals and approvals into written form in a governed platform has a genuine secondary benefit here that has nothing to do with productivity: the decision record survives the employee. Given employment-linked residency and the abruptness with which regional staff turnover can happen, an approval trail that leaves with someone's personal phone is a real operational exposure, and this argument persuades finance and legal more reliably than any efficiency claim. Two further specifics. Language is a design decision rather than a detail: a workforce spanning Arabic, English, Hindi, Urdu, Malayalam and Tagalog needs one authoritative language for decisions and policy, with translation as a service rather than parallel authoritative versions — because two authoritative texts eventually diverge and nobody knows which governs. And a large share of the regional workforce is frontline rather than desk-based, in retail, logistics, hospitality, construction and facilities. Async-by-default is a knowledge-worker operating model; for shift-based staff the equivalent is clear written standing instructions and shift handover records, not collaborative documents. Applying one model to both populations is the most common design error in regional rollouts.

The objection worth taking seriously

The strongest criticism is that async-by-default advantages a specific kind of person and disadvantages others in ways that are unrelated to their contribution. Writing well in the organisation's working language is a skill unevenly distributed, and it correlates with education and first language rather than with judgement or expertise. In a multilingual regional workforce, an async-first culture can systematically amplify the voices of those who write fluent English and quietly diminish colleagues whose operational knowledge is deeper but whose written expression is less polished. Meetings, for all their inefficiency, are more forgiving of this. An organisation adopting async without attention to that effect will improve its decision documentation and narrow its decision inputs. There is a second, subtler cost. Written communication strips tone, and disagreement in text reads more harshly than the same point spoken. Teams that moved contentious discussion into comment threads frequently observed conflict escalating faster and resolving more slowly, because each party was responding to the least generous available reading. The mitigation is not more writing guidance; it is discipline about moving to a conversation the moment a thread shows friction — which requires someone to be watching for it. And the honest caveat about the evidence. The loudest advocates for async were distributed technology companies whose work is largely individual, output is measurable, and staff are self-directed knowledge workers. That is a narrow population. A construction group, a hospital, a logistics operator or a manufacturing business has coordination requirements that are genuinely synchronous, and a large share of its people are not at desks. The transferable insight is narrower than the advocacy: default to writing for proposals, decisions and status; keep meetings for disagreement and ambiguity; and stop treating attendance as evidence of contribution. That much generalises. "Async-first" as an identity does not.

Common Questions

What is the first change to make?

Require a written input before any recurring meeting can be held, and let meetings without one be cancelled. It removes more low-value meetings than any calendar policy, and it builds the writing habit without a cultural mandate.

How do you stop async from becoming slow?

A stated response clock and a default for silence — comments within one working day, and no objection by a named date means approved. Async without a deadline is just delay with better documentation.

Which meetings should always stay?

One-to-ones, anything involving disagreement or personal difficulty, problem definition when the question is still unclear, new team formation, and crisis coordination. The test is whether the exchange needs to be iterative and read for tone.

How does AI change async work?

It removes the two frictions that limited adoption most. Drafting assistance lowers the cost of writing a clear proposal, which matters most for colleagues working in a second or third language — and that directly addresses the fairness objection above, because it narrows the gap between a person's judgement and their written fluency. Translation across Arabic, English, Hindi, Urdu and Tagalog makes a multilingual written culture practical in a way it was not, though one authoritative language for the decision record remains necessary. Retrieval over documents and message history addresses the findability problem that made async organisations rediscover their own conclusions. Two cautions. Generated text is longer and more uniform than written text, and async depends on documents being worth reading — so the discipline shifts from producing writing to editing it down. And meeting transcription plus automatic summarisation can quietly reverse the operating model: if every synchronous conversation produces a tidy record, the incentive to write beforehand disappears, and the organisation drifts back to deciding in meetings with better minutes. The written proposal has to remain the input to a decision, not the output of one.

---

Async Operating Model Design — name who decides, set a response clock, and keep disagreement in conversation; async without decision rights is just slower.