Every meeting is a tax. It interrupts deep work for everyone in the room, costs the company a multiple of its scheduled length in context-switching, and produces decisions that often could have been made in a written thread in half the time. The compounding cost of a meeting culture is one of the largest hidden taxes inside a growing company.
Do the arithmetic once and it stops being abstract. A recurring one-hour meeting with six people costs six hours of attendance, plus a context-switching penalty on each side that research on interrupted work puts at twenty minutes or more per person. Call it eight to ten real hours, weekly, forever, for one slot on the calendar. Most companies carry ten to twenty of these. Nobody would approve that spend if it arrived as an invoice, which is precisely why it survives: it never does.
The async-default operating model
Async-default does not mean no meetings. It means meetings are reserved for the situations where they are demonstrably better than writing: high-bandwidth debate of a complex trade-off, building trust with someone new, or working through a hard interpersonal conversation. Everything else, status, FYI, light decisions, becomes a written thread.
The sorting question that makes the model workable: is the bottleneck here information or alignment? Information transfers better in writing (readable in two minutes, searchable forever, no scheduling). Genuine alignment problems (people disagree and the disagreement has emotional or political weight) transfer better with faces and voices. Most meetings are information transfer wearing alignment's clothes, and one honest pass through the calendar with that question dissolves half of them.
The shape of a good written thread
A good thread leads with the decision being asked for, includes the context needed to evaluate it, names the recommended option, and gives a response deadline. The author is the single-threaded owner; reviewers respond by the deadline or are presumed to defer.
The deadline-or-defer rule is the load-bearing part, and it is the one teams skip. Without it, async becomes the slowest channel in the company: threads wait on the least responsive reader, and people flee back to meetings because at least meetings end. With it, async is the fastest channel: 48 hours, stated in the first line, silence counts as consent, and the owner ships. Write the rule down as policy so invoking it never reads as rudeness.
The migration, not the announcement
Async cultures are built by subtraction and demonstration, not decree. Pick your noisiest recurring status meeting and replace it with a written round for one month, keeping the slot booked but empty as a safety net. Model the thread format from the top: the first ten good decision-threads should come from leadership, because the company adopts what leaders visibly do, not what they announce. Then run the quarterly audit: for each standing meeting, name the last decision it produced. No answer, no meeting. Expect to cancel a third of the calendar the first time; expect nobody to miss it by the second month.
What you get back
Hours of focused time per person per week, a searchable record of why decisions were made, and a culture where the slowest reviewer no longer sets the company's pace. The cost is real, you have to write better. That is a worthwhile trade.
One honest caveat: async-default raises the bar on writing skill, and unevenly. Some strong operators think out loud and write poorly, and a pure-text culture can mute them. The fix is not to reinstate the meetings; it is to allow a recorded two-minute voice note or a quick call that ends in a written summary. The artifact stays written. The path to it can flex.