Cut recurring meetings with a two-part manager audit

Your calendar opens to a wall of standing invites. Most were accepted in a hurry, before you knew what they would cost. Now they repeat, unreviewed, and the team expects you to show up. The question is whether the calendar is doing the work.

The cost is easy to count. Pick one recurring invite and total the hours it consumes each week, then multiply by the year. That number is the real price of the calendar. Aim for a meaningful cut in meeting time, not a perfect calendar.

Brian Chesky built an AI setup to gain company visibility and lower his meeting load. The setup included an intelligence corpus trained on 18,000 Keynote slides, 50,000 Google documents, and other company materials. He built dashboards to monitor internal company activity. The setup cut his meeting time in half. Meetings at large companies are a way for CEOs to learn what is happening because executives often lack direct visibility.

The manager version of that move is a two-part audit. Put durable context in shared docs and dashboards, then cancel the recurring meetings that only feed visibility. Start with the invites, not the people, and reduce meeting load without creating a new reporting ritual. The audit is a cleanup, not a blame game. The alternative to a status update meeting is a shared doc plus a decision path.

Build the context layer before cutting meetings

The context layer should be boring. It should hold the facts that change slowly: the plan, the risks, the metrics, the open questions. It should not become a second meeting transcript. A doc that requires a weekly call to explain itself is not doing the work.

• Inventory every recurring invite. List each standing meeting, its owner, its stated purpose, and the last time it produced a decision. Done looks like a short table where every invite has a reason you can defend.
• Build the context layer. Create a shared doc or dashboard that carries the durable facts: current goals, open risks, recent decisions, and the numbers people keep asking about. The finished page is one that a new teammate can read before asking for a status call.
• Cancel the status meetings it replaces. Remove the recurring invite that only reports what the doc already shows. The usual mistake is canceling before the doc exists. The team will read that as avoidance, not cleanup. The result is a calendar with fewer standing invites and a doc that answers the usual questions.
• Replace the update with a decision path. Any meeting that still has a job needs an explicit job: decide, unblock, or align. The finished calendar gives every remaining invite a named outcome, a time limit, and a reason to exist.

Cancel the status meetings it replaces

Start with the invites that exist to make you feel informed. Those are the easiest to cancel gracefully. Send a short note: the recurring update is moving to the shared doc, and the meeting is closed unless someone needs a decision. Give the team a clear place to ask questions. Then delete the invite, not just the next occurrence.

The note should be short, factual, and final. Name the doc, the owner, and the next time the team can expect a decision.

Do not cancel a meeting that is actually a working session. A room used to solve a problem should stay, but shrink it to the people who can act. A room used to report progress should move the progress to the doc and let the meeting close.

When the team pushes back, ask what they need from the meeting. Visibility belongs in the doc. A decision gets a one-off with a firm deadline and a specific, clear question.

When a recurring invite resists cancellation, ask what decision it is supposed to produce. Knowing what is happening belongs in the shared context, so cancel the invite. Making a choice keeps the meeting, but give it a firm deadline and a named owner.