Remove broadcasting, not decisions
Eight people attend a weekly status meeting. Most repeat information already in tickets. The blocked release decision appears in the final minutes, when two required owners have left. Canceling the meeting could save a calendar slot, but it could also remove the only place the decision was noticed. Replace the broadcast and preserve the conversation that actually needs people.
The recommendation is to identify the meeting's job, write routine updates in a shared place, and schedule live discussion for unresolved decisions. This is an editorial operating approach, not a claim that asynchronous work is always superior. Disagreement, sensitive topics, and weak shared context may require a conversation.
Do not start with a meeting-count target. A short meeting can be wasteful; a long one can resolve a consequential conflict. The useful questions are who needs the information, who can decide, and what outcome cannot be obtained from the proposed replacement.
Some meetings carry hidden work: relationship repair, help-seeking, or learning the context behind a change. If you remove them without another route for that work, the need reappears in private messages. Ask participants what they use the meeting for before assuming the agenda describes its whole purpose.
Illustrative scenario: a status call becomes a decision slot
Amira manages a release team. The recurring call lists completed tasks but rarely resolves the reporting dependency. She proposes a written update before the scheduled slot and reserves the slot only for decisions that need discussion. This is an invented example, not measured savings or a client result.
The replacement update does not say “green overall.” It names the demonstrated result, the blocker, its owner, and the required choice. The receiving test team can see that a scheduled job has not been validated. The product owner can see that keeping the original date requires reduced scope.
Filled release update
Demonstrated: staging export works with the new schema.
Not demonstrated: the overnight reporting job.
Owner: the data lead runs the check before Thursday's review.
Decision needed: reduce reporting scope or move the release if the check fails.
Requested response: product and operations owners confirm the preferred boundary before the review.
Two people disagree about reducing scope. Amira keeps a live discussion for them and the decision owner. Everyone else receives the outcome afterward. The point is not that the disagreement should have been solved by better writing. The update made the disagreement visible early enough to include the right people.
If the written update receives no response, Amira does not treat silence as consent. She checks whether the named owner saw it and whether the response expectation was realistic. The team still needs an accountable decision, not merely proof that a message was sent.
Audit the job before changing the calendar
| Meeting job | Possible replacement | Keep live when |
|---|---|---|
| Broadcast progress | Short update with evidence and owner | Readers lack the context to interpret it |
| Resolve a decision | Written recommendation before discussion | Tradeoffs remain disputed or require specialist review |
| Find blockers | Visible blocker queue and response owner | The problem is not yet understood |
| Handle a sensitive matter | Appropriate private conversation | Confidentiality or interpersonal context matters |
This table is a starting tool, not a policy that every team must adopt. Do not use it to move confidential personnel issues into a shared document. Do not remove required governance, safety, or regulatory meetings without their owners' review. The tool applies to ordinary coordination you have authority to change.
Include the person receiving the work in the replacement design. A status format that suits the sender but omits the receiving team's next dependency merely moves the meeting burden into follow-up questions. A useful update should tell someone what they can proceed with and where a decision is still pending.
Writing needs a response agreement
Agree when the update is posted, who must read it, what response is requested, and how an unresolved decision escalates. “We are asynchronous now” is not a response agreement. Neither is expecting everyone to watch every channel continuously.
Replacement agreement
Updates go in the release record before the review. Named decision owners respond by the agreed checkpoint. Missing responses are followed up directly by the coordinator. Unresolved tradeoffs keep a live slot with the necessary owners. The decision and changed commitments are recorded where the receiving teams can find them.
The leader's responsibility is to protect those expectations. If updates must be written on top of unchanged meeting loads, the replacement becomes additional work. If leaders privately reverse decisions, the shared record loses credibility. Remove duplicate reporting and make the resulting commitments visible.
For the resource conflict behind many meeting discussions, see Make the priority tradeoff explicit. Meeting design determines where a decision happens. Prioritization determines what the available people will actually do.
Test one replacement, not the whole calendar
Choose one recurring status meeting. Identify its broadcast content and one decision it routinely fails to resolve. Try a written update and a narrower live slot for two cycles. At the next review, ask whether owners responded, blockers became visible, and participants could find the decision afterward. Restore or change the conversation if context was lost. A smaller calendar is not the success criterion. Reliable coordination is.