Meeting hygiene
Meetings are the most expensive tool the team owns — a one-hour call with six people costs a working day. Treat them like production changes: intentional, reviewed, and cancelled when they stop earning their keep.
Recommended default
Section titled “Recommended default”No meeting is the default. Hold one only when the work needs synchronous reasoning, a live decision, or a conversation that would take three days over chat. Everything else is a message, a doc, or a comment on the PR.
When a meeting is the right call, every invite carries four things:
- A named owner. One person runs it, writes the notes, and owns the follow-up.
- A stated outcome. Decide X, align on Y, unblock Z — not “discuss.”
- An agenda in the invite body. Not “TBD” and not in a linked doc nobody opens.
- A short default length. 25 or 50 minutes, not 30 or 60. Leave room to breathe between calls.
Invite only the people who need to speak or decide. Everyone else reads the notes.
Why this is the default
Section titled “Why this is the default”Meetings scale badly. Six people in an hour is six person-hours; the same information broadcast in a written update costs one. Async writing forces the author to think clearly and lets readers process at their own pace — a meeting hides muddled reasoning behind confident tone.
The four-part invite is the smallest filter that separates a working meeting from a standing habit. If you can’t name the owner, the outcome, or an agenda, the meeting isn’t ready — and often isn’t needed.
Common mistakes or tradeoffs
Section titled “Common mistakes or tradeoffs”- Recurring meetings nobody cancels. Put an end date on every recurrence. Renew it deliberately, not by default.
- Status meetings that could be a message. If the round-the-room update has no decisions, replace it with a written thread.
- “Optional” attendees marked required. Padding the invite so people feel included wastes their time and dilutes the room.
- No notes, or notes nobody reads. Decisions that live only in someone’s memory get re-litigated next quarter. The load-bearing ones graduate to a decision record.
- Discuss-only agendas. “Discuss the roadmap” is not an outcome. Name what you want to leave the room with.
- Back-to-back scheduling. Every meeting bleeds into the next one. Default to 25/50 so people arrive on time and ready.
Step by step
Section titled “Step by step”- Before inviting, write the outcome you want in one sentence. If you can’t, don’t send the invite.
- Check async first. A shared doc with comments, a chat thread, or a PR review often replaces the meeting entirely.
- Draft the invite with owner, outcome, agenda, and any pre-reads. Cap the length.
- Trim the attendee list. Speakers and deciders are required. Interested parties get the notes.
- Run it to time. Start on the hour, end early when you can, park off-topic threads in writing.
- Post notes within 24 hours — decisions, owners, next steps — where the team already looks. No notes, no meeting.
- Review recurring meetings quarterly. Any that no longer produce decisions or unblock work: cancel or shorten.
Further reading
Section titled “Further reading”- Basecamp, It Doesn’t Have to Be Crazy at Work — Jason Fried and DHH’s case that constant meetings are a symptom of chaotic work, not a driver of it.
- GitLab Handbook — All-Remote Meetings — GitLab’s working defaults: async-first, a named DRI per meeting, 72h invite notice, and non-essential attendees marked optional.