A meeting is expensive in ways that do not appear on the calendar invite. The invite says 30 minutes. The actual cost is 30 minutes of everyone in the room, plus the 15 minutes of context-switching before and after, plus the follow-up thread that exists because not everything got resolved, plus the next meeting to handle the things that fell through.
A two-person daily standup, five days a week, costs the organisation roughly 200 hours of focused work per year. That is more than a month of output from one person, spent on coordination.
We stopped having most meetings. Here is what replaced them.
The default is writing
When something needs to be communicated, the default is a written message, not a call. Not because calls are bad — because writing forces clarity in a way that speaking does not.
Speaking is tolerant of vagueness. You can say something like this and gesture. The listener fills in the gaps. The gaps get filled differently by different people. The follow-up call exists to reconcile the different gap-fills.
Writing is intolerant of vagueness. If you cannot write a clear sentence about what you want, you do not yet know what you want. The discipline of writing the message is the work of thinking the problem through. By the time the message is sent, it is already better than it would have been in a call.
Status updates are documents, not conversations
Every project has a living document. It contains the current state, the decisions made, the open questions, and the next step. When anyone on the project needs to know what is happening, they read the document.
The document is updated at the end of every working session, not at the beginning of a meeting. By the time a status meeting would have started, the status is already written down, already read, already understood.
The meeting that exists to share status is the meeting that does not need to happen.
When synchronous is right
Async does not mean no calls. It means calls are reserved for things that actually require synchronous communication.
Three things that require it: decisions with high emotional weight, where tone matters and written messages risk misread. Complex problems where the back-and-forth of conversation is faster than the back-and-forth of messages. Relationship-building with new clients, where the warmth of a conversation is the work.
Everything else — feedback, status, approvals, questions with clear answers — is handled async. The rule of thumb: if the question can wait four hours for a response, it can be written. If it cannot wait four hours, it probably cannot wait for a meeting to be scheduled either.
The thing nobody says about async
Async is not better for everyone. It is better for focused work and worse for people who think out loud. Some people's best thinking happens in conversation — the act of articulating an idea to another person generates the idea. Async silences that process.
We have adapted by building in deliberate synchronous time for the work that benefits from it. Design reviews. Problem-solving sessions on genuinely hard questions. The beginning of a project, when shared context needs to be established quickly.
Async by default does not mean async always. It means the burden of justification is on the meeting, not on the message.