Replacing a meeting with something written
Most meetings that are cancelled come back, because the need was real and nothing replaced it.
Meeting reduction fails when meetings are simply removed. The coordination need that produced them does not disappear, it becomes invisible, and after a month somebody reinstates the call because things are being missed. For broader context on online meetings and collaboration, Microsoft Teams is a useful reference.
The replacement has to exist before the deletion.
Identify what the meeting actually produced
Before replacing anything, name the output. Not the agenda — the thing that would be missing without it.
Usually it is one of four: a decision, an alignment on priorities, a set of blockers surfaced, or a sense of what other people are doing. Each has a different written substitute, and using the wrong one is why replacements fail. For a practical software-side reference on the cost of repeated context switching, this reference adds useful detail.
The substitutes that work
- Information broadcast → a written update on a fixed day, in a fixed place, in a fixed format.
- Blocker surfacing → the written check-in, with blockers scannable.
- Decision → a proposal document with a comment period and a named decider, and a stated date when it closes.
- Priority alignment → a maintained, visible list of what is being worked on in priority order, owned by one person.
- Relationship → this one does not have a written substitute. Keep the call, and stop pretending it is a work meeting.
Most decisions do not need a meeting. They need a written proposal, a stated comment window, a named decider and a date the window closes. Silence is agreement, stated in advance.
Written updates need a fixed rhythm
The meeting provided rhythm as well as content. A written replacement with no fixed day drifts, then stops, and the meeting returns.
Same day, same time, same author, same format. Regularity is what makes a written channel readable, because people learn when to look.
Someone has to own the replacement
A meeting has an owner by default — whoever called it. A written process frequently has none, and unowned processes decay silently.
Name the owner when the meeting is cancelled, in the same message. Without that, the deletion has an owner and the replacement does not.
Give it a trial period and a review date
Announce the replacement as a trial with a review at six or eight weeks, and be genuinely willing to reinstate. This lowers resistance considerably, because people are agreeing to an experiment rather than to a permanent loss.
At the review, ask what has been missed rather than whether people like it. Preference and function are different questions, and only one of them matters.