Six weeks ago we changed the default meeting length in Google Calendar from 30 minutes to 25. Nobody voted on it. Our head of ops flipped the setting on a Tuesday and sent a two-line note in Slack. We expected complaints. We got three, all in the first week, all from the same person.
What those five minutes were doing
We tracked what happened in the last five minutes of our standing 30-minute meetings for two weeks before the change. Someone volunteered to note the pattern at the end of every call they joined. The log lived in a Notion page called “tail time.” Here is what filled that window, ranked by frequency:
- Small talk about weekend plans or a Netflix show, roughly 40% of the time.
- Someone re-explaining a decision that had already been made, 25%.
- Waiting for a person to find the right Figma link or Linear ticket, 20%.
- Actual new work, 15%.
The contrarian read: those minutes were not a buffer for depth. They were a tax on focus, paid so nobody had to end a call early and feel awkward about it.
What we replaced it with
Every recurring meeting now ends with a two-line summary posted in the meeting’s Slack thread within ten minutes. Line one is the decision. Line two is the owner and the date. No preamble, no thank-yous.
Decision: ship the billing migration behind a flag on Nov 18. Owner: Priya, checkpoint Nov 15.
The wrap-up ritual moved from voice to text, and the small talk moved to the first two minutes of the next call, where it belongs and where late joiners do not miss it.
What we noticed after a month
Our engineering weekly used to run 30 minutes and consistently ended at 32. It now runs 25 and ends at 24. The Monday product review, historically our worst offender, dropped from 60 to 50. We booked 14% fewer follow-up meetings across the org in October, measured against September’s baseline, because the Slack summaries closed the loop that the tail time used to leave open.
The uncomfortable part: nobody misses the five minutes. We thought people would grieve the small talk. They did not. They grieved the recap, which is a different problem, and the two-line summary solved it in writing.
If you want to try it, do not announce a policy. Change the default, post one summary after your next meeting, and see who copies you by Friday.