Asynchronous communication works when information has a reliable home that people trust more than their memory of a conversation. Most recurring meetings exist to compensate for the absence of that home. Deleting the meeting without building the home makes coordination worse. Building the home shortens the meeting on its own, without anyone enforcing a rule.
What a Recurring Meeting Is Really For
A standing meeting on the calendar is a claim about where information lives. It says that the current state of the business exists only in the heads of the attendees, and that retrieving it requires assembling them.
That claim is often true. Project status sits in one person, customer sentiment in another, capacity in a third, and none of it is written down anywhere the others can reach.
Under those conditions the meeting is not waste. It is the only functioning retrieval mechanism the business has, which is why attempts to cancel it fail so consistently.
The correct target is the underlying condition. When the state of the business exists somewhere legible, the meeting stops carrying the retrieval load and can carry something else.
That something else is decisions, disagreement, and judgment, which are the only activities that genuinely require people to be present at the same time.
Counting recurring blocks on a calendar gives a rough measure of how much of the operating picture has never been written down. Each block represents a category of information with no other route to the people who need it.
The measure is uncomfortable because it is accurate. Growing businesses add meetings steadily, and the additions are usually correct responses to real gaps rather than poor discipline.
The Status Meeting Is a Symptom
Status meetings are the clearest example. Each attendee reports what they did, what they will do, and what is blocking them.
Almost none of that content requires simultaneous presence. It is a broadcast of facts, delivered serially, to an audience where most people need only a fraction of what is said.
The cost is not merely the meeting length. It is the number of people multiplied by the length, plus the fragmentation of the working day around a fixed interruption.
Those meetings persist because the alternative was never built. Asking people to write updates instead fails when nobody agrees on where updates go, what they contain, or who is obliged to read them.
Written updates without a defined destination become another inbox, and another inbox is a worse version of the meeting rather than a better one.
Status meetings also perform a second function that rarely gets acknowledged. They confirm that colleagues are working, which reassures managers who lack any other visibility into progress.
That function deserves an honest name. Where a meeting exists to reassure rather than to inform, the fix is a visible record of work rather than a better agenda.
Working through how written coordination replaces the need to assemble people starts with the destination question rather than the tooling question.
What a Reliable Home Requires
Information has a home when four conditions hold, and all four are needed for people to stop relying on conversation.
The first condition is a single location per category of information. Project status lives in one place. Customer issues live in one place. Decisions live in one place. Two locations for the same category means neither is trusted.
The second condition is currency. Information that is sometimes stale is functionally useless, because every reader must verify it by asking someone, which reintroduces the conversation the system was meant to replace.
The third condition is an obligation to read. A destination nobody is expected to check produces writers who feel ignored and readers who feel overwhelmed. Obligation has to be specific about who and how often.
The fourth condition is a format that survives skimming. Long prose updates go unread. Short structured entries, with the state first and the explanation second, get read even by busy people.
Decisions deserve particular attention, because they are the category most often left homeless. A choice gets made in a conversation, understood differently by each participant, and never recorded anywhere.
Weeks later the same question returns and the discussion restarts from the beginning. A written decision log with the choice, the reason, and the date removes an entire class of repeated meeting.
Businesses that satisfy those four conditions find their status meetings shorten without any policy change. Attendees arrive already informed, and the meeting naturally moves to the parts that were unresolved.
Why Deleting Meetings Backfires
Removing a meeting before building the alternative produces predictable damage, and the damage arrives with a delay that obscures the cause.
The first effect is a rise in direct messages. Information that used to be broadcast to everyone becomes a series of private exchanges, which means the same content gets transmitted repeatedly with variations.
The second effect is uneven knowledge. Some people ask and stay informed. Others do not ask and fall behind, and the gap tends to follow seniority and confidence rather than need.
The third effect is slower decisions. When nobody knows the current state, every decision requires a discovery phase first, and the discovery phase is invisible in any calendar.
The fourth effect is the return of the meeting, usually within a quarter, under a different name and with the same agenda. The underlying need never went away.
A fifth effect lands on newer staff hardest. People who joined recently rely on meetings to absorb context they have no other way to acquire, and removing that channel slows them for months.
Experienced staff rarely notice this, since they already hold the context. Decisions about coordination made only by long-tenured people tend to underestimate what the record has to carry.
The lesson is sequencing rather than principle. Build the home, wait for people to trust it, then let the meeting shrink to fit what remains.
The Meetings Worth Protecting
Not every meeting is a symptom, and treating all of them as waste produces a different failure.
Anything involving disagreement belongs in real time. Written exchanges about contested topics escalate badly, because tone is absent and each party rereads the other in the least generous available interpretation.
Anything involving a decision with real consequence belongs in real time. Decisions require questions, and questions require the ability to interrupt, which written formats handle poorly.
Anything involving a person rather than a project belongs in real time. Concerns about workload, direction, or fit surface through hesitation and tone, neither of which survives translation into a written update.
The value of a properly run regular conversation between a manager and one person increases when routine reporting has moved elsewhere, because the time is no longer consumed by status.
Difficult feedback belongs in real time as well, and the temptation to write it is strongest exactly where writing serves worst. Written criticism is read repeatedly, each reading colder than the last.
The pattern is consistent. Information transfer should be written. Judgment, conflict, and human context should be spoken. Most calendars invert this, spending live time on transfer and handling judgment through hurried messages.
Building It Without a New Platform
Most businesses already own more than enough tooling for this, and adding another product usually delays the work rather than advancing it.
Start by naming the categories that currently require a meeting to retrieve. Typically there are three or four, covering work in progress, customer problems, capacity, and pending decisions.
Assign each category one destination in a system people already open daily. The choice of system matters far less than the singularity of it.
Define the shape of an entry, and make it short. State first, change second, blocker third. Anything longer will be written inconsistently and read partially.
Set the obligation explicitly. Name who writes, how often, and who is expected to have read before the next live conversation happens.
Expect the first month of entries to be poor. People write for an imagined reader and only calibrate once they see what colleagues actually need from the record.
Editing the format after a few weeks is normal and healthy. A record designed in advance and never revised tends to collect fields nobody uses while omitting the one thing everyone asks about.
Then hold the meeting anyway for a while, and use it to check whether the written record matched reality. That comparison is what builds trust, and trust is the actual product being constructed.
Once the record is trusted, cut the agenda to items that were unresolved in writing. The meeting shortens by itself, which is a far more durable outcome than shortening it by decree.
The instinct to attack meetings directly is understandable and misdirected. A calendar full of recurring blocks is a readable map of everything the business failed to write down, and the blocks are load bearing until something else carries the load. Businesses that build the record first find their meetings shrink quietly and stay shrunk. Businesses that cut first find the meetings return, because the need was never about preference. It was about where the truth lives.
Frequently Asked Questions
How do you know which meetings to remove?
Look at what the meeting produces rather than what it covers. Meetings that end with everyone knowing something they did not know before are transfer meetings, and transfer belongs in writing. Meetings that end with a decision, a resolved disagreement, or a changed plan are doing work that requires presence. The distinction is more reliable than length or attendance when deciding what to cut.
What if people do not read the written updates?
Non-reading usually signals a format problem or an obligation problem rather than a discipline problem. Updates that are long, inconsistent, or buried in a system nobody opens will go unread regardless of instruction. Naming who must read, and referencing the written record openly during live conversations, changes behaviour faster than reminders. If the record is the only source of the answer, people read it.
Does asynchronous work suit every team?
It suits information transfer everywhere and suits judgment work nowhere. Teams doing highly interdependent creative work need more live contact than teams executing defined processes. What changes across contexts is the ratio rather than the principle. Every team benefits from removing status reporting out of live time, and no team benefits from handling conflict in writing.
How long does it take before meetings actually shorten?
Trust in a written record builds over several weeks of the record being correct. Until people have checked it against reality a few times, they will keep asking in person, which is rational behaviour rather than resistance. Running both the record and the meeting in parallel for a stretch is the fastest path. The meeting shortens once attendees stop discovering surprises.
Should a business buy a dedicated tool for this?
Rarely at the start. The constraint is agreement about where information lives, and buying software converts a decision problem into a configuration project. Existing shared documents or a channel structure in current messaging are usually sufficient to test the discipline. Tooling becomes worth considering after the habit exists and the volume genuinely exceeds what simple systems handle.
What about the informal information people share before meetings begin?
That content is real and worth preserving deliberately. Casual exchange surfaces early warnings and relationship context that structured updates never capture. Businesses that remove all live contact lose it and usually notice only after a problem escalates. Keeping a small amount of unstructured time is a cheap way to retain that signal.
No comments:
Post a Comment