Meetings as a Symptom: When Sync Calls Are Covering for Broken Async

Too many meetings is almost always a symptom of broken async rather than a scheduling problem. Status and alignment calls exist to rebuild shared understanding that was never captured in a durable record. When the underlying state is declared and queryable, the reason to gather everyone live mostly disappears, and the calendar empties on its own.

Meetings as a symptom, not a cause

Most meeting-reduction efforts treat the calendar as the problem: shorter meetings, fewer attendees, no-meeting Fridays. These help marginally and then fail, because they attack the symptom. The real driver is that the team has no reliable way to know the current state of work without assembling people to say it out loud.

A status meeting is, functionally, a verbal query against everyone's memory because there is no record to query instead. An alignment meeting re-establishes decisions because the decisions were never durably declared. Seen this way, the meeting load is a precise readout of how much state is trapped in people's heads. It is one of the four faces of the coordination tax distributed teams pay.

Which meetings are covering for broken async

Not all meetings are symptoms. Genuine collaboration, debate, relationship-building, and complex real-time problem-solving justify synchronous time. The suspect meetings are the ones whose entire purpose is to transfer or confirm state that could have been written down.

Meeting type	Real purpose	Symptom of broken async?
Daily status standup	Surface current state	Yes, almost always
Alignment sync	Reconfirm decisions	Yes, if decisions were undocumented
Handoff call	Transfer shift context	Yes, replaceable by a wrap
Working session	Solve a hard problem together	No, this is genuine sync work

A test for every recurring call

Apply one question to each recurring meeting: if every participant had read a current, trustworthy record of declared state beforehand, would this meeting still need to happen? If the honest answer is no, the meeting is compensating for a missing record. If the answer is yes, because the value is in live debate or co-creation, keep it.

Run this test across a team's calendar and the pattern is stark. The meetings that survive are the genuinely collaborative ones. The ones that fall are status and alignment rituals, the very meetings people most resent. They were never about collaboration; they were about the absence of a queryable source of truth. For distributed teams, this also intersects with authority, because many alignment meetings are really about confirming who decided what, a theme covered in decision accountability on distributed teams.

Replacing meetings with declared state

The replacement for a status meeting is not another meeting; it is a record that answers the questions the meeting existed to answer. When each person captures their decisions, current state, and open questions into a shared record, anyone can read the team's status on their own schedule, across any timezone, without a call.

This is where a system of record for decisions earns its keep. State is declared once and queried by whoever needs it, and the principle of silence over speculation guarantees the record reflects only what was actually declared, not optimistic filler. Importantly, cutting a meeting without supplying this record does not save anything; the coordination simply leaks into Slack pings and one-off calls. You have to install the async substrate first, then remove the meeting. The handoff version of this substrate is detailed in async handoffs that actually work.

Common Questions

Are all status meetings really unnecessary?

The status-transfer purpose is unnecessary when a trustworthy record exists. Some standups also serve as a team touchpoint or quick unblock forum; if that is the real value, keep them short and explicit about it. The point is to stop using live time to transmit information a record should hold.

If we just cancel meetings, won't things fall apart?

Yes, if you cancel them without replacing the function. The coordination need is real; the meeting is just one way to meet it. Install a declared-state record first so the need is met asynchronously, then the meeting can be removed safely.

How do meetings relate to the coordination tax?

Compensating meetings are one of the four categories of the coordination tax, alongside repeated questions, handoff loss, and blocking on offline owners. They are the most visible category, which is why teams attack them first, often without fixing the underlying async gap.

What about meetings across hard timezone gaps?

Those are the most expensive of all, because someone takes the call at a brutal hour. They are also the easiest to eliminate, since a declared-state record serves both regions on their own clock and removes the need to force overlap at all.