Meeting facilitation is the deliberate design and guidance of a discussion so that a group stays focused, participates well, and leaves with clear outcomes. A facilitator's job is to protect the process — the flow of conversation, the distribution of airtime, the path to a decision — rather than to drive the content. This distinction matters because meetings often fail not for lack of expertise in the room but because the conversation drifts, ownership is unclear, or the group never converges on a choice. The most useful question a facilitator can ask before any meeting begins is whether live interaction will produce better alignment, speed, or decision quality than asynchronous communication alone. If the answer is no, the meeting probably should not exist.
The single most important thing to define before any meeting is the outcome: the specific decision, alignment, or next step the group should leave with. An outcome is not a topic; topics are what the meeting will discuss, while outcomes are what the meeting will produce. A useful outcome statement is a single sentence describing an observable result — for example, "We leave with a chosen vendor and a named implementation owner." Topics without outcomes usually produce no decision. A meeting framed only as "be back by 5pm" states a constraint, not an outcome, and the group leaves without knowing what they were supposed to produce. Once the outcome is written down, every agenda item can be tested against it: if an item does not serve the outcome, it does not belong in the meeting.
Good meetings are designed around constraints, not just goals. A meeting charter captures the design choices in one place — purpose, audience, cadence, owner, success metrics, and the decision rights the meeting actually has — so participants know what they are walking into. The minimum viable meeting principle says to strip every agenda item, attendee, and minute until only those essential to the outcome remain, and then add back only when justified. The two-pizza rule applies the same idea to headcount: a meeting is usually sharpest with six to eight people, because beyond that, coordination costs rise, ownership dilutes, and the loudest voices tend to dominate. Different meeting types deserve different designs: a working meeting produces shared understanding and drafts, while a decision meeting commits to a choice, and trying to do both at once usually does neither well. Other types — kickoffs, post-mortems, decision workshops, daily standups, war rooms — each have their own conventions, and calling a working session a meeting often sets the wrong expectations before anyone has spoken.