The Meeting That Earns Its Time
When I receive a meeting invitation without an agenda, I decline it. This is not a quirk or a policy — it is a direct expression of how I think about work. Outcomes over activities means that every block of time on my calendar needs to have a defined purpose, and a meeting without an agenda is, by definition, purposeless until someone arrives and improvises one. Usually that someone ends up being me, which means I have been drafted into managing something I had planned only to support, at the cost of everything else I had intended to do with that time.
The agenda requirement is not really about the document. It is about the thinking that producing the document forces. An agenda requires whoever called the meeting to articulate, in advance, what the meeting is actually for. That articulation is where most bad meetings reveal themselves before they happen, because the honest answer is often that the meeting is for discussing something, and discussion is not a sufficient reason to put eight people in a room for an hour.
Discussion belongs before the meeting, not in it. The work of a well-run team happens in the spaces between meetings: in documents read and annotated, in questions asked and answered asynchronously, in analysis completed and shared before anyone sits down together. By the time the meeting starts, the discussion should already have happened. What the meeting is for is to make decisions on the basis of that prior work. That is the only use of synchronous time that justifies the full cost of it, which, when you account for every person in the room and everything each of them is not doing while they are there, is considerably higher than most organizations treat it.
The pre-work requirement follows directly from this. A meeting without pre-work is a meeting where the group will spend its first twenty minutes reaching a shared understanding of the situation that each individual could have arrived at independently, in five minutes, by reading a document the night before. That twenty minutes is not collaboration. It is catch-up, and it is expensive catch-up at that.
What a meeting that earns its time actually looks like is fairly unglamorous. The agenda is distributed at least twenty-four hours in advance. The relevant documents are read before anyone arrives. The meeting itself moves quickly through context, because context was established in advance, and spends the majority of its time on the decisions that only the group can make together. Those decisions are recorded. Owners and deadlines are assigned. The meeting ends, ideally early, and everyone leaves knowing exactly what changed as a result of being in the room.
The test I apply is simple: could your team walk out of this meeting and immediately articulate what is different about today than it was before it started? If yes, the meeting worked. If the answer involves phrases like "we covered a lot of ground" or "we need to follow up on a few things," you held a status update, gave it a better name, and will do it again next week.
