The last five minutes of a meeting decide whether the meeting will matter a week later. The facilitator's closing responsibility is to ensure the meeting ends with a clear summary, named owners, and visible next steps. Action items fail most often when owners, deadlines, or success criteria are vague, so a clear-and-complete action item is phrased as "[verb] [object] by [date] owned by [name], with success criteria visible to the group." Reading action items aloud at the end surfaces ambiguity, overload, and forgotten ownership before people leave the room — unspoken commitments decay, and reading them back is the cheapest insurance against that decay. The DAOD closing template — decisions, actions, owners, dates — forces every decision to leave the room with an owner and a date rather than as a topic of conversation. A next-action check, where each participant states their single next step, is a particularly tight version of this discipline, often used in operational stand-ups and one-on-ones. A check-out question, such as "What are you leaving with?", is a useful closing prompt that surfaces final concerns or commitments.
A decision capsule — a short written summary containing context, choice, owner, deadline, and review date — is designed to outlive the meeting itself. A decision digest is a weekly one-page summary of decisions made across meetings, used to keep the organization aligned without reconvening everyone. A decision log serves the same purpose at the meeting level: it records what was decided, why, and who owns the next actions. Together, these artifacts address the half-life of a meeting, which is the time after which most attendees forget most of what was said — usually within forty-eight hours — and is the reason written notes and action items matter so much. Summarizing often in the meeting itself reduces confusion, confirms shared understanding, and makes it easier to spot disagreement early.
Meetings themselves benefit from retrospection. A retrospective question such as "What helped this meeting work, and what should we change next time?" opens a short debrief. Plus/delta captures what to keep and what to change in about three minutes. Stop-start-continue, where each participant names one thing to stop doing, one to start, and one to continue, is useful at the end of recurring meetings. A decision quality check at the end of a meeting — "On a 1–5 scale, how confident are we this was the right call and that we have the right owner to execute it?" — turns gut feeling into data the group can act on next time. At the portfolio level, recurring meetings accumulate meeting debt, the accumulated cost in time, attention, and morale of recurring low-value meetings that no one has pruned. A meeting audit is a quarterly review of every recurring meeting on a team's calendar to cancel, redesign, or downsize those whose outcomes no longer justify their cost. A simple rule of thumb for meeting cost is to multiply the number of attendees by their average hourly rate by the meeting length — this is the floor of what the meeting must produce to be worth it.
Synchronous and asynchronous facilitation are different disciplines that should be chosen on purpose. Synchronous facilitation guides live discussion; asynchronous facilitation shapes comments, documents, and votes over time without everyone being present at once. Written facilitation is a pattern where a facilitator structures an async thread with prompts, deadlines, and explicit decision steps; a decision deadline — a clear timestamp by which input, votes, or objections must be submitted, after which the decision owner finalizes the call — is what makes the pattern actually close. Specific meeting types deserve specific design: a standup is a short, time-boxed sync focused on blockers and next actions, ideally fifteen minutes total, roughly one minute per person, with any deeper conversation parked for follow-up; a status meeting is a longer broadcast of updates that often belongs in async, and a standup that has drifted into one-person status broadcast is usually a sign it should become async. A silent meeting, where everyone reads the agenda and writes comments in a shared doc before verbal discussion begins, often dramatically shortens the live portion. A kickoff meeting sets purpose, roles, scope, timeline, risks, and decision rights at the start of a project, sometimes replaced by a kickoff memo when stakeholders are distributed or the project is low-complexity. A post-mortem is a structured review after a project or incident; a blameless post-mortem focuses on systems and decisions rather than individuals to surface learning without triggering defensive behavior. A war room is a persistent space where a team meets repeatedly to drive a single complex outcome, with artifacts visible to all. Recurring meetings are held together by working agreements, quorums that define the minimum number of decision-makers who must be present for decisions to be valid, and norms such as a latecomers' tax — anyone joining more than a defined number of minutes late gets a brief written recap instead of re-orientation, to protect on-time participants. Meeting-free days, most often a Friday, signal that the team protects deep work and recovery, and round out a portfolio where every meeting has earned its place.