Meetings run short exactly as often as somebody decided what “done” would look like. Your hub gives you calendars, invites and attachments, but the moment worth engineering is days earlier: the invitation you send. Get that right and almost everything else follows.
The invitation is the specification
An invite does not need to be long; it does need to name its species.
- Decide. One decision is being made. Name it in the invite. If there is no decision, it may be an announcement — which might not deserve a meeting at all.
- Design. An artefact gets reviewed or drafted together. Links go inside the description, not as an “I’ll follow up”.
- Gather. A checkpoint. If nobody would notice a cancellation, shorten the slot instead of adding slides.
In practice
Share the background material one business day before, not four minutes before. Attendees read on their own time only when reading is possible, and someone who opens the document cold will spend the meeting catching up instead of deciding.
The first three minutes
Open by restating the sentence from the invite: the decision on the table. Not as a formality — as a fence. Wandering happens most in meetings whose purpose was never written down, and it costs the best people the most, because they are the ones who fill silence with tangents.
What happens at the close
Every meeting sends three promises out of the room: owners, dates and the thing checked next. Post them into the meeting thread while the room still agrees. Consensus decays at a scandalous rate, and no one, anywhere, has ever mistaken the promise of “minutes to follow” for follow-through.
