Recurring meetings expand quietly until they consume the week, leaving the actual work squeezed into the gaps between calls, and many remote teams now experiment with meeting-free weeks to reclaim focus. The idea is not to stop communicating, it is to move routine communication into writing and reserve live time for the conversations that genuinely need it. Done well, a meeting-free week produces deeper work, clearer decisions, and a calmer team; done badly, it produces confusion, duplicated effort, and a frantic catch-up week afterwards. The difference is preparation, not willpower.

Start by listing every recurring meeting and asking, for each one, what decision it produces, who needs to be present for that decision, and whether the same outcome could come from a written update. Status meetings, where each person reports progress in turn, almost always fail this test, because the same information in writing is faster to read, searchable later, and accessible to people in other time zones. Meetings that resolve disagreements, plan complex work, or build relationships pass the test and should be kept, though perhaps less often or with a sharper agenda.

Calculate the cost honestly: multiply the number of attendees by the duration, add preparation time, and consider the focus cost of a meeting that splits a morning in half, since fragmented days produce less deep work than the calendar suggests. Share the audit with the team and agree which meetings will pause, which will become written updates, and which will continue, because a meeting-free week imposed without agreement breeds resentment and shadow meetings. Set a clear start and end, one week to begin with, and a review date to judge the experiment fairly.

Replace each cancelled status meeting with a short written update, posted on the same day the meeting would have occurred, covering progress, next steps, and blockers, with a clear owner for each item. Keep updates in a shared channel or document where anyone can read them asynchronously, and set a norm that questions are answered in the thread, so the discussion itself becomes the record. For decisions that would have been made in a meeting, use a short decision document: the proposal, the options, the recommendation, and a deadline for objections, after which the decision stands unless someone raises a substantive concern.

Protect a small amount of live time for genuine exceptions, such as an incident, a conflict, or a decision that stalls in writing, and make it easy to request a focused call for those cases without guilt. The goal is not zero meetings, it is zero routine meetings, and a team that can call a meeting when it needs one, but does not default to one, has the best of both worlds. Watch for the failure mode where written updates become long essays nobody reads: keep them short, structured, and skimmable, with detail linked rather than pasted.

At the end of the week, review with the team: what decisions were made, what was delayed, what information was missing, and how did focus and energy compare with a normal week? Keep the changes that worked, restore the meetings that proved necessary, and convert the rest into written rituals permanently, rather than letting the calendar quietly refill. Many teams settle on a rhythm of one meeting-free week per month, or a meeting-free day each week, which preserves the benefits without the risks of a permanent ban.

Track a few simple measures across experiments: the number of recurring meetings, the time to decision on typical items, and a quick team survey on focus and alignment, so the judgement is based on evidence rather than nostalgia for the old calendar. A meeting-free week is a tool for revealing which meetings earn their time, and the lasting value is often the audit itself, which leaves a leaner calendar even after meetings return. Cut with care, replace with writing, and let the work, not the calendar, set the pace.