Teams that move to fully remote work usually find their calendars fuller, not emptier. The cause is that conversations which previously happened without scheduling now have nowhere else to go.
Offices carry a large volume of unscheduled exchange
A shared floor produces constant low-cost contact: a question asked in passing, an overheard answer, a two-minute correction before a decision hardens.
None of that appears on a calendar, so it is invisible in any measurement of meeting load. It is nonetheless doing substantial coordination work.
Remove the shared floor and the work still needs doing. The only remaining container for it is a scheduled call.
Scheduling has a minimum size
A hallway question takes ninety seconds. The same question booked as a meeting takes thirty minutes, because calendars are granular and nobody books ninety seconds.
The conversation also expands to fill the slot. Having assembled people, participants raise adjacent topics rather than end early.
So a set of exchanges that consumed minutes in aggregate now consumes hours, and the difference is a property of the container rather than the content.
Uncertainty about status generates further meetings
In an office, presence is a crude but constant signal that work is proceeding. Without it, managers substitute check-ins, which are meetings created to answer a question presence used to answer for free.
Each check-in is defensible in isolation. Collectively they form a recurring layer that persists long after the underlying uncertainty has been resolved.
Recurring meetings are also rarely cancelled, because cancelling one requires someone to assert that it is no longer needed.
Written channels absorb the load only if they are trusted
Teams that document decisions in writing genuinely need fewer meetings, but only when people believe the written record is current and complete.
If the record is stale, reading it is a risk rather than a shortcut, and the safe behaviour is to ask a person directly, which returns the load to calendars.
The trust is built by discipline about updating, not by choosing a tool. A well-maintained document in a plain format outperforms a neglected one in a sophisticated system.
Reducing load requires replacing the function, not the meeting
Cancelling meetings without providing another route for the same information produces confusion followed by their quiet reinstatement within a quarter.
What works is identifying which specific function each recurring meeting serves — status, decision, or relationship — and moving only the ones a written or asynchronous form can carry.
Status usually moves well. Decisions with genuine disagreement usually do not, and forcing them into writing simply lengthens the argument.