Run a twenty-minute meeting audit and turn status calls into async updates

Your team is tired, but the calendar still looks normal. The recurring meetings are short enough on paper, and the damage is in the repetition. A twenty-minute audit can find the status calls that should be async, the meetings that are too long, and the rituals that no longer earn their place.

The calendar is a policy

Every standing meeting is a decision about how the team spends attention. If the calendar is not reviewed, it becomes a default. The default usually favors the meeting that was easiest to create, not the meeting that still earns its place. A chief of staff can change that by treating the calendar like a document with owners, dates, and a review date.

Meeting load is measurable. The average knowledge worker now sits through 21.7 meetings in a week. In a small company, that load can look smaller, but the effect is the same: fewer blocks for work that requires concentration. The audit is a calendar review with a decision attached to each line.

Ask each meeting three blunt questions

For each recurring meeting, ask whether it needs to be live. A live call earns its place when the team must resolve disagreement, make a decision under uncertainty, or build trust across a new relationship. If the agenda is only updates, the meeting is probably a status call. The audit separates live work from written work.

Then ask whether it is running long. Many meetings survive because nobody has measured the actual time against the value produced. A standing call that was created for a fast-moving project can outlive the project. The fix is often a shorter slot, a tighter agenda, or a time limit that forces the owner to choose what matters.

Finally ask whether it is needed at all. Some meetings exist because they were copied from a larger company, a previous stage, or a founder's habit. The test is simple: if the meeting is removed, what decision gets delayed, what relationship weakens, and what work becomes harder? If the answer is nothing concrete, the meeting can be killed.

The numbers show where the fatigue comes from. 45% of meeting fatigue is tied to meetings that are too long. 41% is tied to too many meetings overall. 39% is linked to meetings that could have been an email.

Use this checklist for every standing meeting. Each item should be answerable quickly.

• Does it need to be live, or can it become async?
• Is it running longer than the decision it protects?
• Is it needed at all, or is it a status call that could have been an email?
• What is the outcome: keep, shorten, async, or kill?
• Who will write the decision into the weekly cadence?

The live question turns status into written work. A recurring standup that only reports blockers can become an async standup. The team posts updates, flags risks, and names the decision that still needs a live call. The live meeting, if it remains, becomes a decision call.

Length protects the owner's time. A meeting that is too long usually hides a scope problem. The owner can cut the agenda, split the audience, or move the update to a document. The meeting keeps only the part that requires shared attention.

Necessity is the hardest because it asks the team to admit that a ritual may be unnecessary. The answer is not always kill. Sometimes the meeting should become a less frequent review, a document, or a note in the ops review. Make the change visible instead of letting the calendar stay unchanged.

Async works when the decision is written down

Async updates fail when they become a meeting with no owner. The fix is a short document with a clear structure: what changed, what is blocked, what decision is needed, and who is responsible. The document is the meeting's output, written before the next live call.

When a decision is made, write it down in the same place. When follow-up notes are not shared, 70% of meeting decisions fade from memory within 24 hours. The logging step matters because the decision needs a record. The team needs to know what changed, why it changed, and where the next decision will appear.

The cost of unmanaged meetings is not only lost hours. 74% of employees report doing work on a typical Sunday, while 21% say that Sunday work amounts to a full or near-full day. A meeting culture that extends into the weekend is a sign that the team is not getting enough protected time during the week.

Put the audit on the calendar as a recurring review, and write the output into the weekly cadence as a short list of meetings that changed, with owners and dates.