A perspective piece from The Listening Market
The meeting that could have been an email has become a truism, a piece of office folklore so widely repeated that it barely raises a smile. But a stranger shift has been taking shape underneath the joke. On a growing number of teams, scattered across cities and time zones, the meeting is becoming the exception rather than the rule. Documents circulate for comment. Decisions happen in writing. Someone waking up in Sydney finds a thread, started eight hours earlier by a colleague in Lisbon and carried along by another in Austin, waiting for a single line of input to move forward.
This is asynchronous work, often shortened with unfortunate bluntness to “async”, and for a long time it lived quietly at the margins of professional life. It was the mode of open-source contributors who never met, or writers working alone at odd hours. Now it is becoming the default operating system for teams that were never going to share a room anyway. The question is not whether colleagues can attend a call at 3am their time. It is whether they need to be in a room together at all for the work to be good.
Remote work outgrew the meeting
The great remote-work experiment revealed something uncomfortable. When offices went home, many companies simply moved their meeting culture onto video calls and called it a day. Calendars filled up worse than before. Days fragmented into a mosaic of thirty-minute blocks, each demanding a fragment of attention, with no block long enough to do the actual work. The problem was never the office. The problem was the meeting.
Distributed teams, especially those spread across more than a handful of time zones, could not keep the fiction going. There is no hour of the day that is reasonable in Sydney, London, and New York simultaneously. So the work had to be reorganised around the one medium that respects no clock: the written word, plus whatever artefacts can be attached to it.
What began as a logistical necessity has turned out to have unexpected advantages. Meetings happen in real time and vanish unless recorded. Writing accumulates. It becomes searchable history, an institutional memory that does not resign when its owner does.
Why the written word scales better
There is a reason large organisations run on documents. A good memo can be read in ten minutes by a thousand people at once, while a meeting to convey the same information takes an hour from each of them. The arithmetic is brutal and entirely in the document’s favour.
Writing also forces a clarity that speech lets people skip. It is hard to ramble for eight hundred words. Vague ideas announce themselves on the page in a way they disguise in conversation. Teams that work in writing tend to find, after an awkward adjustment, that their thinking is sharper, not despite the absence of meetings but because of it.
None of which means async work is anti-conversation. The most mature distributed teams protect a small number of rituals, the weekly video call, the quarterly gathering, the standing one-to-one, and treat them as expensive, precious occasions, used for the things writing does poorly: building trust, resolving tension, deciding the genuinely contested calls. Everything else is written. The meeting stops being the default and becomes the special occasion, which is arguably what it should have been all along.
Trust moves from presence to work
Beneath the operational arguments sits a deeper change in what managers believe they are looking at. In an office, presence was the proxy for work. Someone at a desk at nine, still there at five, was presumed productive. It was never a great proxy, and everyone knew it, but it was easy, and ease wins.
Async work removes the proxy entirely. There is no desk to observe. What remains is the work itself: the pull request, the document, the reply, the shipped thing. Managers have to judge output rather than attendance, which sounds like a small administrative adjustment and is in fact a change of philosophy. It asks leaders to define what good work looks like with enough precision that it can be recognised on its own merits.
Employees, for their part, report a change in the texture of their days. Deep work becomes possible because nothing shatters it every forty minutes. Junior staff, once dependent on hallway osmosis to learn their craft, need deliberate structures instead, documentation, mentoring, chances to write badly in public until they write well. Some teams do this poorly and lose people. The ones that do it well find they have built something sturdier than a culture of proximity ever was.
The tools were never the point
The software industry, with its usual enthusiasm, has built a sprawling marketplace of tools for this way of working: shared documents, threaded discussions, project trackers, wikis, recorded walkthroughs. The tools matter, in the way plumbing matters. But teams that struggle with async work almost never struggle because of missing software. They struggle because their habits, their status rituals, and their sense of what counts as “being at work” were built for a world of shared rooms.
The genuinely hard parts are human. Writing well takes practice, and not everyone starts comfortable. Waiting twelve hours for an answer requires patience that meetings were invented to avoid. Loneliness is real, and so is the strange freedom of being unreachable, which cuts both ways. Async work is not a paradise. It is a trade: the warmth and speed of presence exchanged for depth and continuity. The teams choosing it are betting that for knowledge work, the trade favours depth.
How teams actually make the switch
The transition is less a policy change than a habit change, and the teams that manage it well tend to do the same handful of things. They write down decisions, in a place people can find, so that a choice made in a thread stays visible long after the thread scrolls away. They set explicit norms about response times, because “async” without norms simply becomes “slow sync”: nobody knows whether an answer is expected in an hour or by tomorrow, and the uncertainty is exhausting.
They protect a small band of overlapping hours, finding the two or three hours of the day when most of the team is awake, and spend it on the synchronous things: debates, introductions, celebrations. They treat documentation as onboarding, so a new joiner learns the craft from the team’s accumulated writing rather than from three months of shadowing. And they record the reasoning, not just the conclusion, because in a written culture the reasoning is what the next person inherits.
Mostly, they hold the line against calendar drift. Meetings are seductive precisely because they feel like work, and any distributed team will slowly re-grow a meeting culture unless someone keeps pruning it. The teams that stay async are the ones that keep asking, of every proposed call, the same awkward question: could this be written instead?
A quieter kind of company
Something like a hundred years of office culture taught people to speak fluently in meetings: interrupt politely, hold the room, perform certainty. That skill does not transfer to a document. In writing, the person who wins is the one who thinks clearly, and that person has always existed in every organisation, sometimes at the quiet end of the table, sometimes not at the table at all.
There is something quietly redistributive about that. A brilliant analyst who freezes in a room full of senior voices can produce, unmolested, a piece of writing that shifts a decision. A thoughtful disagreement that would have been swallowed in a call surfaces as a threaded comment, and the team is better for having it.
Async work will not swallow every workplace. Factories, hospitals, restaurants, and a hundred other kinds of work run on simultaneity, and always will. But for the growing share of the economy that runs on thinking, the default has already quietly flipped. The office did not die. It diffused. The room became a document, and the document turned out to be bigger than the room ever was.
