Operations ·
When a meeting can become a written update
A recurring meeting should have a clear job. Separate information sharing from decisions that genuinely need people in the same conversation.
By Norwind
Name the purpose before changing the format
Review a recurring meeting by asking what participants should be able to do afterward. If the answer is simply to know the current status, a written update may cover the need. If the meeting resolves an uncertain tradeoff or disagreement, a live discussion may be valuable. Removing a meeting without replacing its useful function can create more messages and less clarity.
Make the written alternative complete
A useful update names what changed, what remains uncertain and what someone needs to decide. Give the decision an owner and a date when it is needed. Link to the relevant working material rather than asking readers to search a shared drive. Keep the update in a place the team already uses, with a clear way to ask for clarification.
Keep the conversations that earn their place
Try the alternative for a limited period and ask whether decisions still arrive in time. Bring people together when a written exchange stops making progress. A meeting can become shorter or less frequent without disappearing. The point is to protect attention while preserving shared understanding. Software can support the handoff, but a new reporting tool will not define the purpose of a meeting for you.
A practical check
- Classify the meeting as an update, a decision or working time.
- Name the reader and the action a written update should support.
- Review whether the alternative creates new confusion.