How to Run Meetings That End on Time and Decide Things

Nine people, sixty minutes, a title like 'Q3 Planning Sync.' The first ten minutes are people arriving and catching up. Someone presents context everybody already has. Two people debate a detail that concerns only the two of them while the other seven check email. At minute fifty-five somebody says 'so what are we doing?' and the answer is 'let's take it offline' — and then the same meeting happens again next week with a slightly different title.

The cost is easy to calculate and rarely calculated. Nine people for an hour is more than a day of work. Run weekly for a quarter, that's three weeks of someone's life spent not deciding something.

Most meetings are scheduled for a topic rather than a decision. A topic has no end state, so it expands to fill whatever time is available and then requests more. A decision has a finish line, and everyone in the room can tell whether you crossed it.

The second cause is unclear authority. If nobody knows who decides, the group defaults to seeking consensus, and consensus among nine people is functionally unreachable on anything that matters. What you get instead is the appearance of agreement from the people who spoke and quiet non-commitment from the people who didn't.

The third is attendance by default. People get invited so they won't feel excluded, and every additional person adds obligation to speak, which adds minutes and dilutes accountability. The larger the room, the lower each individual's sense of ownership over the outcome — well documented, and visible in every meeting you've ever sat through wondering why you were there.

Before improving your meetings, remove some. The weekly team sync that exists because it has always existed, the project standup for a project now in maintenance, the review meeting where four people watch two people talk. Each of these has a defender who will argue it builds alignment, and the honest test is simple: cancel it for three weeks and see who notices. Most of the time nobody does, and the three hours a week you recover is real capacity you did not have to hire for.

Status meetings are the biggest single category worth converting. A written update read on someone's own schedule carries more detail, survives being referenced later, and reaches the people who could not attend. The objection is that people will not read it, which is usually true for updates nobody writes carefully — write the first four yourself and set the standard.

What genuinely needs a room is disagreement, ambiguity, and anything with emotional weight. If you protect meetings for those three things and push everything else to writing, the meetings you do hold will be the ones people arrive at prepared for, because they will have learned that your invitations mean something.

Meetings end early. Not on time, early, because a group working toward a named decision reaches it faster than a group working through a topic.

Some of your recurring invites get declined and nothing breaks. That is people correctly reading a clear title and deciding they are not needed, which is exactly what you wanted.

The written close-out stops being contested. When nobody argues a week later about what was agreed, you have eliminated an entire category of rework.

Put the decision in the title of every invite you send. It sounds trivial and it restructures everything downstream: you can't write the title without knowing what you actually want, people arrive prepared for a conclusion, and any meeting you can't title that way reveals itself as an email before it ever gets on a calendar.