What back-to-back meetings cost you
A full calendar looks like productivity and is often the opposite, because the larger cost is what happens to the time around the meetings.
The gaps are not spare time
Work that requires holding several things in your head at once has a start-up cost. You spend the first stretch rebuilding the context you had before you were interrupted, and that cost is paid again every time.
This is why a day with four meetings spread evenly can produce less than a day with four meetings stacked together. The stacked day leaves one unbroken block; the spread day leaves four fragments, none long enough to get back to depth.
Why back-to-back feels efficient
Scheduling tools optimise for fitting things in, and a calendar with no gaps looks like a calendar with nothing wasted. It is a convincing picture, but it measures how full the calendar is rather than how much gets done.
It also puts the cost on the person least able to refuse it. The organiser sees one slot filled, while the attendee sees the fifth context switch before lunch.
Find a time with a poll
Propose a few slots, share one link and let the group vote. Guests don't need an account.
The meeting that runs over is not free
Back-to-back scheduling removes all slack, so the first meeting that runs five minutes late makes you late to the next one, and the one after that. By mid-afternoon a single overrun has propagated through four meetings and everyone in them.
Ending five minutes early keeps a small overrun from becoming everybody's problem.
How to keep gaps between meetings
Default to twenty-five and fifty minutes instead of thirty and sixty. Most calendar tools can do this automatically, and it buys the gap without anyone having to negotiate for it.
Cluster meetings deliberately rather than spreading them. Two mornings with everything in them and three mornings with nothing beats five mornings with two each, even though the totals are identical.
When proposing times to a group, offer slots that respect this rather than filling every visible gap in people's calendars.
For people scheduling across time zones
Distributed teams tend to compress meetings into a narrow overlap window, which produces exactly the back-to-back pattern above, for everyone, every day.
Two things help. Move anything that does not need discussion out of the overlap window and into writing. And rotate which side of the world takes the inconvenient hour, so the cost is shared rather than always paid by the same people.