Try this: export your own calendar to a spreadsheet and add up the recurring meetings. For a lot of leaders the number lands somewhere north of thirty hours a week before a single one-off call. That is the equivalent of four full working days every week sitting in rooms, most of them rooms someone created years earlier, for reasons no one can fully reconstruct anymore. Then run the experiment that feels reckless at first: cancel almost every recurring meeting on the calendar, one at a time, and watch to see what breaks.
Almost nothing does. That is a hard thing to accept, because the alternative is admitting that a large share of the working week had been theater. But the evidence is hard to argue with. Decisions still get made. Information still moves. The work still ships. What changes is that you get back something close to twenty hours a week, and the people who had been sitting in those meetings get their time back too, multiplied across a team. This is what auditing meeting culture this way teaches, along with the one meeting worth defending to anyone.
Most recurring meetings are habits wearing the costume of necessity
The thing about a recurring meeting is that it is born to solve a real problem and then it outlives the problem by years. Someone schedules a weekly sync because a launch is going sideways and the team needs to coordinate fast. The launch ships. The meeting stays. Six months later, eleven people sit in it every Tuesday because the calendar invite never died, and nobody wants to be the person who suggests killing it, because that feels like saying the work does not matter. So it persists out of politeness and inertia, and the cost compounds quietly.
Let me put a number on it, because leadership conversations about time tend to stay vague. A weekly hour-long meeting with eight people is not eight hours. With preparation, the context switch in and out, and the recovery time before anyone gets back into real work, the honest cost is closer to twelve or fifteen hours a week. Over a year that is somewhere north of six hundred hours, the rough equivalent of a third of a full-time employee, spent on one recurring meeting that may or may not still be earning its place. Multiply that across the dozen standing meetings a typical company runs and you are looking at several headcount worth of capacity, invisible because it never appears as a line item.
I am not against meetings. I am against meetings that run on autopilot. The discipline I wish I had adopted years earlier is simple to state and hard to practice: every recurring meeting should have to re-earn its place on the calendar, and the default should be deletion, not renewal.
What I cancelled, and what actually happened
Start with the meetings that make you wince to look at. The weekly all-hands status update, where each team lead reads out what their team has done, is a good first target. It is a ritual of reassurance, not information, because anyone who needs the status can already see it in the work itself. Replace it with a written update that takes ten minutes to read on a Monday morning. Few people will mourn it.
Next are the standing cross-functional syncs, the ones that exist so that marketing and product and engineering can "stay aligned." Alignment, it turns out, does not happen because you put people in a room every week. It happens because the right people share the same context about a specific decision at the moment the decision is live. A weekly slot is the wrong tool for that. It is either too early, when there is nothing to align on, or too late, when the decision already drifted. The better move is to replace those syncs with short, decision-specific threads opened the moment a real fork appears.
A few rules emerged from the experiment that I now treat as house policy for time management across the company:
- If a meeting is for sharing status, it should be a document. Reading is faster than listening, and a document can be skimmed, searched, and referenced later.
- If a meeting has no decision to make, it does not need to happen. Decisions justify meetings. Updates do not.
- Every recurring meeting gets an expiry date. If it is still valuable when the date arrives, anyone can renew it deliberately. The default is that it ends.
Example: Picture a project review that used to be a ninety-minute meeting every two weeks, eight people, slides built the night before. Move the entire thing into writing directly on the work, inside a tool like Atlas, where the project, the tasks, and the open questions already live. The review then happens asynchronously across two days. People read, comment where they have something to add, and the project owner resolves the open threads. The ninety-minute meeting is gone, the decisions are better because they are written down and considered rather than blurted out under time pressure, and the slide-building tax disappears entirely.
The hidden cost was not the time, it was the shape of the day
Here is the lesson that surprises people most, and the one worth passing to anyone looking honestly at their calendar. The real damage from a meeting-heavy schedule is not the hours the meetings consume. It is what they do to the hours in between. A day with four meetings scattered across it has no usable blocks of deep focus left in it, even though it might only contain four hours of actual meeting time. The gaps are too short and too fragmented to start anything hard, so they get filled with shallow work, and the genuinely difficult thinking gets pushed to evenings and weekends or, more often, simply does not happen.
When you clear the recurring meetings, the gift is not the reclaimed twenty hours. It is that the remaining hours connect into real blocks. You can sit with a hard strategic question for three uninterrupted hours instead of in twenty-minute slivers between calls. The quality of the thinking goes up in a way that is hard to quantify but obvious in the decisions. The same holds for a whole team whose afternoons get protected from meetings entirely. Output does not just go up by the hours saved. It goes up because the hours that remain are finally shaped for the work.
The objections, and why most of them did not survive contact
When you start cancelling meetings, the same objections come up every time, and they are worth taking seriously because they are not stupid. The first is that meetings build culture and connection, and that killing them will leave people isolated. There is truth in this, but it confuses two different things. Connection is real and worth protecting. A status meeting is not where it happens. People do not bond by watching each other read updates off a screen. They bond over shared work, over solving a hard problem together, over the unstructured conversation that a status meeting actually crowds out. Clear the calendar and you do not lose connection. You make room for the kind that matters, and you can fund a few deliberate gatherings whose entire purpose is connection, with no agenda pretending otherwise.
The second objection was that asynchronous written updates would not get read, and that the meeting at least forced attention. This one has a kernel of truth and a flaw. The kernel is that a document nobody reads is worse than a meeting nobody can skip. The flaw is that the meeting did not actually have anyone's attention either. We have all sat in the status meeting answering email under the table. The solution was not to keep the meeting. It was to write updates worth reading, short, specific, and honest about what is going wrong, and to make reading them a genuine expectation rather than a hope. A good written update gets read precisely because it respects the reader's time, which the meeting never did.
The third objection comes from people who derive their sense of importance from the meetings themselves. Being in the room feels like being central. This is the hardest one to address because it is real and human and nobody says it out loud. The honest response is that importance should come from the work and its outcomes, not from attendance, and a healthy meeting culture is one where nobody's status depends on being in a room. Getting there takes more than a calendar change. It takes being explicit that people are measured by what they ship and decide, not by how many invites they appear on.
The one I kept, and would never drop
None of this is an argument for meeting nihilism. There is exactly one recurring meeting worth defending through the entire purge: the weekly one-on-one. Everything said about status meetings being documents does not apply here, because a one-on-one is not a status meeting. It is the one place where the things that never make it into a document get said. The hesitation in someone's voice when a project is quietly going wrong. The frustration that has not yet become a complaint. The ambition someone is too cautious to put in writing. None of that survives translation to text, and none of it shows up in the work until it is too late to help.
The one-on-one is where trust is built and where problems surface while they are still small enough to fix cheaply. It is worth treating as the most valuable hour on the calendar, the one you never cancel, because cancelling it sends a message no leader means to send. Every other meeting has to justify its existence against the cost of the time it takes. The one-on-one justifies itself by being the only channel for the most important information a leader can have, which is how the people doing the work are actually doing. If you are going to keep one meeting, keep that one, and have the courage to question all the rest. You can read more on the discipline of focused work over on the wrxstack blog.