Meetings are often used as a repair mechanism for incomplete context. People gather because the request is ambiguous, the decision history is missing, ownership is unclear, or the evidence lives across several tools.
Meetings hide a context tax
A meeting can resolve ambiguity quickly for the people present, but the result is fragile unless it becomes durable. New participants need another explanation. Absent teams learn late. Agents cannot reliably use what remained in spoken conversation.
The calendar cost is visible. The repeated reconstruction cost also needs to be counted.
Write for action
Useful async context explains the objective, current state, proposed change, affected owners, constraints, evidence, requested response, deadline, and escalation path. This is not documentation for its own sake. It is the minimum interface required for coordinated action.
A reader should be able to identify what they must decide or do within the first screen.
Use synchronous time deliberately
Conversation is appropriate when the problem is genuinely ambiguous, trust is strained, ideas need rapid exploration, or a consequential conflict needs resolution. The written artifact still matters because it prepares the discussion and records the result.
The rule is simple: synchronize for interaction, not for information transfer.
Measure unresolved dependencies
Teams can test whether context is working by tracking clarification cycles, time to acknowledgement, decisions reopened due to missing information, and work blocked on meetings. These measures reveal whether the communication system supports execution.
Reducing meeting count alone is a poor goal. A team can have fewer meetings and worse coordination.
A meeting inventory that leads to a change
This chapter is the migration practice that accompanies Async by Default. The protocol is defined there. Here the question is how to replace an existing interaction without losing the work it quietly performs.
Take a recurring cross-team sync and list the last three decisions or actions it produced. In the fictional Northstar case, the retry meeting contains status collection, a genuine disagreement about client behavior, and an informal learning conversation. Removing the entire meeting would discard useful work along with the status recital.
| Work happening in the meeting | Replacement or retained interaction |
|---|---|
| Collect progress | One owner-maintained change record with current state. |
| Discover a blocked dependency | Routed request with recipient, deadline, and escalation. |
| Resolve conflicting retry semantics | Short conversation prepared by the competing written proposals. |
| Help a junior understand the race | Protected review walkthrough, with consented notes. |
The practical unit of redesign is the job, not the calendar entry.
Before and after
Before: “Any updates on safe retries?” Five people reconstruct the last discussion. Nobody knows whether Checkout has accepted the key contract.
After: CHANGE-42 links the accepted semantics, names Luis as the recipient, and shows an unresolved objection. The live discussion starts at the objection. The owner records the resolution and affected revisions afterward.
This does not guarantee fewer minutes of conversation. It should reduce repeated reconstruction and make the result usable by people who were absent. That is the hypothesis to test.
Silence, time zones, and overload
An async process needs response expectations that match working hours. A deadline of “tomorrow” without a time zone is not a contract. Urgency needs an escalation route and a reason; otherwise every request competes by sounding urgent.
Give recipients a way to reject the assignment, name another owner, or report insufficient capacity. Acknowledgement should not create unlimited work. When requests exceed capacity, a human resolves priority instead of an agent sending more reminders.
Use the smallest artifact that preserves the decision. If the replacement requires more maintenance than the interaction it supports, simplify it. The solution to a confusing meeting is not automatically a longer document.
Test the replacement
Run the new arrangement for two occurrences of the old meeting. Check whether actions have owners, whether an absent participant can reconstruct the result, and whether unresolved dependencies age less. Ask the participants what useful interaction disappeared.
Keep the parts that improved coordination. Restore the parts that carried trust, discovery, or learning until there is a better mechanism for them.