Meeting hygiene: 10 rules that save hours every week

Why meeting hygiene matters

A meeting is the most expensive object on a calendar. Six people for thirty minutes is three hours of paid attention, and most teams spend that budget without checking what came out the other side. Meeting hygiene is the practice of treating each recurring meeting as a product the team is shipping every week, with rules that keep it from breaking.

The good news: hygiene is cheap. None of the ten rules below require new software or a manager off-site. They each take a minute or two of pre-flight, and they compound. After a month, the meetings that survive are the ones the team actually wants on the calendar.

Rule 1: every meeting has one owner

One person sets the agenda, runs the call, and writes the recap. Not the most senior person in the room, the one closest to the outcome the meeting is meant to produce. If nobody steps up, the meeting should be cancelled, not held with a default chair.

The owner has a single job during the call: protect the question. Tangents get parked in a list. Side debates get a five-minute time-box or a follow-up. The owner is allowed to be a little rude here, because the alternative is a forty-five-minute meeting that decides nothing.

Rule 2: the agenda is one sharp question

"Marketing sync" is not an agenda. "Should we kill the paid social budget for May?" is. A sharp question forces the owner to know what good looks like before the meeting starts, and it gives every attendee permission to push back if they cannot help answer it.

If a meeting has three sharp questions, it is three meetings. If it has none, it is a status update, and status updates belong in a written channel. The agenda also serves a second purpose: it is the headline of the recap. If you cannot write the headline before the call, you are not ready to hold the call.

Rule 3: cap working meetings at 25 minutes

Most working meetings should be capped at 25 minutes. The cap does three things: it forces a sharper agenda, it leaves a five-minute buffer for the back-to-back calls everyone has after, and it matches how long a small group can hold focus on a single decision before energy drops.

If a topic genuinely needs an hour, split it. A 25-minute decision meeting on Tuesday and a 25-minute review meeting on Thursday will produce a better outcome than a sixty-minute monster on Wednesday, because the team has time to think between the two.

Rule 4: read the doc in silence first

Borrow this one from Amazon. The first three to five minutes of any meeting where a doc exists are spent reading it, in silence, in the room. No "did everyone get a chance to look at this?" because the answer is always no, and now the next twenty minutes are someone summarizing what should have been read.

The silent read is awkward the first two times you do it. After that, the team protects it, because it is the only part of the workday where they are guaranteed not to be interrupted.

Rule 5: decisions are said out loud, in one sentence

When the room reaches a decision, the owner says it. Out loud. In one sentence. Starting with the word "Decided." For example: "Decided: we keep the May paid social budget at $8k and move $2k to influencer outreach."

This sounds like a small ritual. It is the highest-leverage line in the meeting. Without it, half the people in the room leave with slightly different versions of what was just agreed, and the team relitigates the same conversation two weeks later. Voice AI tooling can catch this automatically and tag it as a decision in the recap, but the human ritual still matters because it makes the agreement real for the people who said yes.

Rule 6: every action item gets a name and a date

"We should look into this" is not an action item. "Priya owns reviewing the influencer shortlist by Friday May 8" is. A meeting that ends without owners and dates on every action will produce zero of those actions by the next meeting, and the team will spend the first ten minutes next week figuring out why nothing moved.

If the room cannot agree on an owner, the action is not real yet. Either someone takes it before leaving the call, or it goes back into the parking lot for the next session. Half-owned actions are the single most common reason recurring meetings stop producing.

Rule 7: the written recap goes out the same day

If the recap is not written by end of day, the meeting effectively did not happen. The team will remember vibes, not commitments.

The owner posts the recap in the team's working channel within the same business day. Format: the sharp question, the decision, the action items with owners and dates, and a one-line note on what was parked for next time. Three to five sentences total. People who missed the meeting should be able to act on the recap without asking a follow-up question.

Same-day matters because every hour of delay raises the cost of writing it. The owner has to reconstruct the conversation from notes, and the team starts work on the wrong version of the decision.

Rule 8: kill the meeting when there is nothing to decide

The hardest rule. If the agenda for this week's recurring meeting has no sharp question, the owner cancels it that morning. Not "we will keep it short," not "let's just check in." Cancelled. The calendar block goes back to the team.

Teams resist this because cancelling a meeting feels like admitting waste. It is the opposite. A meeting that runs without a question is the actual waste. The cancellation is the rare moment where the team gets the hour back and notices nothing broke. After two or three of these, the recurring meeting either returns with a sharper purpose or quietly disappears.

Rule 9: status goes async, decisions stay sync

Most weekly meetings are 80% status updates and 20% decisions. The status round is the slowest possible way to share that information. Move it to a written update posted before the call. Use the meeting time only for blockers, decisions, and risks the written update could not resolve.

Done well, this turns a thirty-minute weekly into a fifteen-minute one. Done badly, it produces a written update nobody reads, and the meeting reverts. The way to make it stick: the owner refuses to take questions in the meeting that the written update already answered. The first time someone asks "wait, where are we on the launch?" the owner says "it's in the doc," and the room learns.

Rule 10: review the meeting itself once a quarter

Once every quarter, spend the first ten minutes of one session asking: is this meeting still worth holding? Has the question shifted? Are we the right people in the room? When was the last time we made a real decision here?

This is the single rule that compounds the most. Most meetings rot because nobody is allowed to say they have rotted. A scheduled review gives the team explicit permission. About a third of meetings get cut at this checkpoint, another third get reshaped, and the survivors get sharper. Every quarter, on a recurring calendar invite, owned by the meeting owner.

How to roll this out

You do not need to adopt all ten at once. Pick the two that hurt your team most, run them for a week, and add a new one each week after. The order most teams find useful: rule 6 (action items with names) first, because it is the easiest win, then rule 7 (same-day recap), then rule 5 (decisions said out loud).

The harder rules to land are 8 (cancelling for no agenda) and 9 (status goes async), because they require the owner to push back on calendar inertia. Hold those for week three, after the team has felt what a clean meeting actually feels like.

If you want the recap and decision-tagging to happen automatically, that is what relly does. It listens to the meeting, hears the "Decided:" line, surfaces action items by name and date, and posts the same-day recap to your channel before anyone has to remember to write it. (See how teams use it across strategy, product, and design calls.)