Meeting Hygiene

Meetings only accumulate. Creating one takes an invite; removing one takes a person willing to say out loud that it should go away, and that person usually doesn't appear. Every new hire adds another set of people to align with, and a meeting that once made it onto the recurring calendar keeps opening in weeks when there is nothing to discuss.

Part of the reason is that the cost stays invisible. The calendar says thirty minutes, but five attendees make it two and a half hours of company time. Stopping work beforehand and picking it back up afterward adds more. None of that appears on anyone's ledger, so adding one more person to the invite always feels free.

Pagedeck ran into this directly. Around the time headcount passed twenty, Noa laid out a week of the calendar and counted twelve hours booked in meetings. Half of them re-covered material that had already been shared in writing. Two had been created six months earlier by someone who had since left, and they were still running with no purpose anyone could name. Meeting hygiene exists so that this state gets caught by a rule instead of waiting for one person to feel awkward enough to raise it.

It works by fixing what has to be true before a meeting opens, during it, and after it, and by not opening the meeting when those conditions aren't met.

In practice the rules come down to five.

1. Write the purpose in one sentence. The invite says whether the session decides something, discusses something, or announces something, because those three run differently. If it decides something, name who decides.
2. If it only announces, don't hold it. A session where people just listen can be a document instead. Teams that already practice documentation-first working, where things get written before they get said, filter out the most meetings at this step.
3. Send the agenda and any reading a day ahead. Explaining background live eats twenty minutes of a thirty-minute slot. When people arrive having read it, those twenty minutes go to the discussion instead. If the material isn't ready, moving the meeting is the better call.
4. Cut the invite list to the people the purpose needs. The attendees added just in case consume the most total time. Anyone who doesn't shape the decision but needs the outcome gets the notes instead, which is almost always enough.
5. Before anyone leaves, write down what was decided and what happens next. That means action items with an owner and a date attached. Skip this and the same topic reappears on the next agenda untouched.

Teams often add group-level rules on top: cancel a recurring meeting the day before if no agenda came in, or block Wednesday afternoons so nobody schedules anything. Deciding once, in advance, holds up better than asking each person to make the judgment every time.

The first place it gets used is the periodic sweep of recurring meetings. Once a quarter, every repeating calendar entry gets pulled out and its purpose rewritten. Anything that can't be stated in one sentence is deleted. Whatever survives gets checked for whether the cadence or the invite list can shrink — a weekly that works fine as a biweekly gives back half its cost immediately.

It also acts as a gate when someone creates a meeting. Put purpose and agenda fields in the invite template and people occasionally realize, while filling them in, that they don't need the meeting. Two of Pagedeck's weekly sync meetings turned into shared documents this way.

The rules also sort what belongs in synchronous communication, where everyone is present at the same moment, and what belongs in asynchronous communication, where they aren't. On a team whose working hours barely overlap, overlapping time is scarce enough that it gets reserved for discussion and decisions while sharing moves to writing.

Meetings with an obvious purpose are not exempt. A kickoff already exists to align goals and roles, but without a written list of attendees and decisions it turns into two hours of conversation. A retrospective loses its point entirely if nothing gets written down at the end, so the fifth rule carries most of the weight there.

"Is this meeting a decision or an announcement? If it's an announcement, send it as a doc."

Asking whether the group actually needs to gather before the slot gets created.

"No agenda came in, so I'm cancelling tomorrow's recurring session."

Applying the rule that a standing invite doesn't justify a meeting with nothing in it.

"Let's spend the last five minutes on who does what by when."

Protecting the close so the discussion doesn't dissolve without a conclusion.

At Pagedeck the person who invokes these rules most often is Mia, since most product meetings pass through her calendar. When someone asks her to set one up, her first question is what they want decided. If the answer is that they'd like to hear how things are going, she sends that week's document instead.

It runs the other way too. When Theo says a design direction has collected thirty comments over three days without resolving, Mia books thirty minutes. Once written round trips start stacking up, with half a day lost to each one, gathering is the cheaper option. That is the part people miss: these are rules for putting meetings in the right place, not rules for having fewer of them.

The most common misreading is that meeting hygiene is a campaign to cut meetings. The argument opens with wasted time, so the conclusion comes naturally. But the target is density, not count. Remove a session people needed and the decision slips, and a slipped decision gets filled in with different guesses by different people, which shows up later as rework. Going from ten meetings to five while still deciding nothing in those five leaves the team worse off than it started. Fewer meetings is a result, not a goal.

The second misreading is that the form is the rule. Once the invite template has a purpose field and a notes template circulates, it looks adopted. What usually happens is that the purpose field says "discussion" and the notes are a transcript of who said what. A template doesn't make the judgment for anyone. The rule only works when somebody sends back an invite with an empty purpose field, and the teams that sustain it are the ones where decision-making has already named who that somebody is.