A recurring meeting can be an important working session or a habit whose original purpose has disappeared. Replacing it with a written update can give people time back, but only if the work still gets done. The useful question is what requires a shared moment and what can be understood independently.
Do not start by counting meetings as inherently good or bad. Start with the outcome people need after this particular meeting: awareness, a decision, a resolved disagreement, an action plan, or a relationship that benefits from direct conversation.
Split the agenda by the work it performs
Take the last two agendas and label each item. A progress announcement may work in writing. A decision with conflicting constraints may need discussion. A demonstration may be useful as a short recording followed by questions, or as a live session when immediate interaction is central.
This exercise often reveals that one meeting contains several kinds of work. You may be able to move routine updates into a document and keep a shorter live discussion for the unresolved decision. That is more precise than removing the entire meeting or keeping every minute because one part is valuable.
Make the written alternative complete
A useful update includes what changed, what happens next, what is blocked, and what response is requested. Name the owner and provide links to the relevant work. Readers should not have to attend a separate conversation merely to decode phrases such as progressing well or waiting on the team.
Set a response window and an escalation route. A document that nobody is expected to read or answer is not a replacement for coordination. State whether silence means no comment, whether explicit approval is required, and who makes the decision when views differ. Do not turn an unread message into assumed consent for a consequential action.
Keep live discussion where it earns its place
Live discussion can help when people need to clarify several interdependent points quickly, work through disagreement, or handle a conversation that needs care and immediate feedback. Accessibility, time zones, language, and participants' preferences also matter. Offer an appropriate way for people who cannot attend to contribute or receive the outcome.
GitLab's communication handbook describes a preference for written, asynchronous work while recognizing a role for synchronous communication. That is a documented organizational approach, not proof that every team should copy its exact rhythm. Use the distinction to examine your own work rather than importing a slogan.
Try a reversible change
Choose a limited period, such as the next two occurrences, and define what you will observe. Did decisions still happen on time? Did blockers surface? Did people need additional private explanations? Did the written update become a long administrative exercise that merely shifted the burden to one person?
Keep the trial small enough to revise. If a weekly status meeting becomes a written update plus a fifteen-minute discussion when needed, compare the complete effort, including preparation and follow-up. Do not claim a time saving by counting only the removed calendar invitation.
An illustrative redesign
A six-person team has a weekly half-hour meeting. Most time is spent reciting completed tasks, while one dependency regularly needs a decision. The team posts short updates in advance and reserves a smaller session for that dependency when it remains unresolved.
The document names the decision owner, the options, and the requested response date. If no decision is needed, the live slot can be released under the team's agreed process. If an unexpected issue appears, the team has a clear way to call a focused discussion. The result preserves coordination while changing how information travels.
Review the quality of the outcome
At the end of the trial, ask participants where understanding improved or deteriorated. Check a few actual decisions and handoffs rather than relying only on whether people liked having fewer invitations. Restore a live element if the work requires it, and improve the written format where ambiguity caused unnecessary follow-up.
The successful choice is a communication pattern people can use to act. A meeting should have a reason to bring people together; a written update should have enough context and a clear response path to stand on its own. When both are designed around the work, neither needs to become a rule applied to every situation.
Sources
- GitLab: Communication handbook
GitLab describes written, asynchronous communication alongside situations where synchronous discussion is appropriate; this is an organizational practice, not universal experimental proof.