Auditing the meetings you have
Recurring meetings are created constantly and deleted almost never. The audit is the only mechanism that removes them.
Read the guideSection · 6 guides
Meetings
Which ones to keep, how to run them so they end early, and what to replace the rest with.
Home/Meetings
A distributed team's meeting load grows quietly, because every uncertainty has an obvious solution — put a call in the calendar — and no corresponding force removes them again. For broader context on online meetings and collaboration, Microsoft Teams is a useful reference.
This section is about the deletion side: which meetings genuinely need to be synchronous, what the alternatives look like in practice, and how to run the survivors so that people leave knowing what happens next. For a practical software-side reference on attendance records and meeting participation, employee attendance tracking software adds useful detail.
Running the meetings that survive
A distributed meeting has a higher cost per minute and a lower tolerance for drift. Both argue for more structure, not less.
Read the guideNotes that are worth the ten minutes
A transcript is not a record. The useful artefact is much shorter and takes deliberate effort to produce.
Read the guideReplacing a meeting with something written
Most meetings that are cancelled come back, because the need was real and nothing replaced it.
Read the guideOne-to-ones when there are no corridors
The conversations that happened incidentally in an office do not happen at all remotely, which makes the scheduled one carry much more weight.
Read the guideWorkshops and long sessions online
A day-long workshop translated directly to video is a bad day for everybody. The format has to change, not just the venue.
Read the guide