When there are too many meetings to do the work

The complaint about too many meetings is usually filed under total hours, and that is the wrong number. Three hours of meetings in a day is survivable when it runs as one block. The same three hours split into six half hour calls leaves five hours that cannot hold anything demanding. The pain is in the fragments, not the sum.

What follows is a way to measure the actual damage, a method for deciding which meetings can go, and what to do about the ones that cannot.

Meetings multiplied because they became cheap to create

Treating meeting overload as a failure of individual discipline aims the fix at the wrong place. Meetings grew because the cost of creating one collapsed. No room to book. No one has to walk anywhere. Adding a person to the invitation takes two clicks, so people get added just in case. Most calendar tools default new events to thirty or sixty minutes, which means a twelve minute question routinely occupies a thirty minute slot on four people's calendars.

The calendar itself reinforces this, because an event marks its time as taken the moment it is created. The standard that defines calendar data states plainly how an event appears to anyone looking for open time.

Generally, an event will take up time on an individual calendar. Hence, the event will appear as an opaque interval in a search for busy time. Source: rfc-editor.org

The inverse matters more. Time that has no event on it looks free to everyone else. A calendar with meetings on it and nothing else looks empty for the entire rest of the week, no matter how much work is planned for those hours. The difference between people who collect meetings and people who do not is often not seniority or workload. It is what they put on their calendar.

Count three things before arguing about it

"Too many meetings" cannot be negotiated in that form. Open last week's calendar and count three specific things instead.

Measure	How to count it	Threshold worth acting on
Total meeting hours	Add up every meeting in the week	More than half of working hours
Fragments	Gaps between meetings shorter than 60 minutes	More than three per day
Longest run	Consecutive meetings with no break	Four or more in a row

The second measure predicts exhaustion better than the first. Work that requires holding a problem in mind takes time to get into, and a forty five minute gap only fits tasks that finish inside it. Two people with identical meeting totals can have completely different weeks depending on whether those meetings are stacked or scattered.

Once the counting is done, sort the meetings into three kinds: meetings that decide something, meetings that only distribute information, and meetings where people work together on the actual thing. This sorting is faster and more honest than hunting for meetings that feel pointless.

Which meetings can actually go

The distribution-only category is where the room is. A meeting that ends with several attendees having said nothing can usually be replaced by a written update without slowing any decision down. Decision meetings are worth defending, because agreement reached live tends to hold, and reversing a bad asynchronous decision costs more than the meeting did.

When negotiating, changing the terms of a meeting lands better than proposing to kill it.

Cut the attendee list. Anyone who could read the notes instead does not need to be required. Making attendance optional is a much smaller ask than cancelling.

Halve the frequency. Moving a weekly to a fortnightly frees twenty six slots a year without anyone losing the meeting they asked for.

Shorten the default. Sixty becomes forty five, thirty becomes twenty five. The five minutes at the end is what stops the next meeting from starting late.

Move it to writing. Status reporting made of numbers and short paragraphs survives the transition intact. Discussion of trade offs generally does not.

For meetings owned by somebody else, proposing that attendance become optional is far more likely to succeed than proposing cancellation, because the other person keeps their meeting.

Defending the work when the meetings cannot go

Plenty of meeting load sits outside anyone's control. In that case the useful move is not negotiation. It is putting the work on the calendar as events, before anyone else fills the space.

Two hour blocks, two or three of them, placed at the start of the week. As established above, unscheduled time reads as free to everyone else, so a block alone reduces the odds of a meeting landing there. Naming the block for the actual task, "draft the launch post" rather than "focus time", also removes the small decision about what to do when the block arrives.

Batching helps as much as blocking. Pushing meetings into the afternoon and keeping mornings clear cuts the fragment count without changing the number of meetings at all. Which half of the day gets sacrificed depends on the work. What matters is that meetings are not scattered evenly, because evenly scattered is the arrangement that destroys the most usable time.

The gaps deserve events too. The five to ten minutes after a meeting is when decisions get written down and the next agenda gets opened. Without that on the calendar, that work happens during the first five minutes of the next meeting instead.

Calendar settings that do real work

Separate from habits, a few settings change outcomes immediately.

Shorten default meeting lengths. Google Calendar has a speedy meetings option that ends thirty minute events at twenty five and sixty minute events at fifty. Applied across a team, this recovers time from every meeting anyone books.

Set working hours. Invitations outside them warn the organizer before they send, which quietly prevents a share of the worst placements.

Use focus time and out of office event types. They behave differently from ordinary events and can decline incoming invitations automatically.

Use appointment schedules for the meetings that are requests rather than commitments. Anyone who needs a conversation books inside a window that was chosen deliberately, rather than wherever a gap appears.

None of these reduce the number of meetings people want. They reduce fragmentation and stop meetings from appearing in places that were never workable. The setup takes about ten minutes and the effect repeats every week.

The cost of a meeting is not its length

A calendar shows the scheduled block and nothing else, yet the time a meeting consumes extends past both ends of it. Preparing material beforehand. Reloading the context in the minutes before it starts. Writing down what was decided and passing it on afterward. Add the preparation and the follow up and a thirty minute meeting routinely occupies closer to fifty.

None of that surrounding time carries an event, which is exactly why it disappears from any estimate. The calendar shows the gaps as available, and the gaps are already spoken for by the meeting either side of them. Counting only scheduled hours and concluding that there is room left is how a day that looks half empty ends with nothing finished.

Three things reduce the per meeting cost without touching the meeting count. Circulate the agenda and materials in advance, which removes the opening stretch where everyone is brought up to speed. Write the decisions during the final five minutes rather than afterward, which converts a task done from memory into one done with the context still present. Group meetings with the same people or about the same project close together, because the reload cost is paid every time the subject changes, not every time a meeting starts.

All three are available to someone with no authority over the schedule at all, which makes them worth doing before any negotiation begins.

Rules a team can agree on

When individual adjustments are not enough, shared rules carry further. Three of them are easy to agree to and keep working over time.

Decline invitations with no agenda. An empty agenda field usually means the decision to be made has not been identified yet, and those meetings run long and settle nothing.

Standardize on twenty five and fifty minute meetings across the team. Applied by everyone, this creates the recording gap between back to back sessions rather than leaving it to whoever remembers.

Circulate documents at least twenty four hours ahead, on the understanding that they will have been read. The read aloud portion of the meeting then disappears entirely.

None of these reduce how many meetings people want to hold. They cut fragmentation and per meeting weight, which is what the week actually feels like. Keeping the list to about three, and reviewing compliance once a month rather than continuously, is what stops the rules themselves from becoming another meeting.

Travel is what breaks a back to back day

On a fully remote day, the gap between two meetings is real. On a week that mixes office days and outside appointments, travel consumes as much of the calendar as the meetings do, while appearing nowhere on it.

Most calendars offer a travel time field per event. It reserves a buffer before that event and knows nothing about where the previous event ended. A meeting finishing at the office at 15:00 and another starting across town at 15:20 can each carry a perfectly configured buffer while the pair is physically impossible, and no warning appears. Treating travel as a property of the day rather than of one event is the approach set out in Travel time.

The busier the week, the harder this is to catch by eye. A dense calendar looks equally dense whether or not any of it is achievable.

Entry speed decides whether the defense survives

Most advice about meeting overload concentrates on how to decline. Tracing the failures backward leads somewhere earlier: the defensive events never got created in the first place.

Blocking work time only helps if the blocks exist, and they exist only when creating one is fast enough to do between two meetings. If placing a block means opening a calendar, picking a date, picking two times, and typing a title, it will not happen in the ninety seconds available. Where a calendar app for Mac accepts a spoken or typed sentence such as "draft the report tomorrow morning for two hours" and turns it into an event, the defense becomes something that survives a busy week rather than a habit that lasts until Wednesday. How that sentence parsing works is described in Entering events, and the wider set of what a native Mac calendar handles is listed in Features.

The second failure is travel not counted as time, which turns apparent gaps into gaps that do not exist. Which products address either of these, stated as facts about features rather than verdicts, is what Compared with other calendars lays out.

What to change first

Count the fragments in last week before touching anything else. More than three a day means the fix is batching and blocking, not declining. Fewer than that, while still finishing the week exhausted, points at travel or at the weight of individual meetings instead, and Caltimate is aimed at the first of those two.