The meeting that was an email, and the three that were the same email

Treat the sections below as a sequence. With unnecessary meetings, getting the early decisions right makes the later ones much easier.

The organiser pays none of the cost

Scheduling a meeting costs the organiser about twenty seconds, and costs the room the number of attendees multiplied by the duration. Nothing in a standard calendar tool shows that total, so the person making the decision never sees the number their decision produces. A tool that displayed collective hours next to the send button would change behaviour immediately, which is roughly why none of them do it prominently.

The result is entirely predictable, because any resource that is free at the point of use gets consumed until something else breaks. What eventually breaks is the individual working day, which is now assembled from the gaps between other people's decisions.

Default durations invented the thirty-minute update

Calendar software defaults to thirty or sixty minutes, and work reliably expands to fill whatever the default was. A conversation with eight minutes of content becomes a half-hour meeting purely because the booking widget offered a half-hour first. Organisations that changed the default to twenty-five or fifty minutes generally report the meetings still ending on time, which is a striking result.

On hold for the fourth time, the change also creates a gap between meetings, which is when people actually write things down and travel between rooms. It is one of the very few workplace interventions that is free, instant and reliably effective, which is why it remains rare.

Status meetings are the clearest waste

A round-robin status update is a broadcast in which each participant is relevant for two minutes and present for forty. The same information written down is faster to produce, faster to consume, searchable afterwards and readable by people in another time zone. The usual objection is that nobody reads the written version, which is a statement about accountability rather than about the format.

Teams that switched successfully generally did so by making the written update the only source, so attending a meeting stopped being a substitute for reading. Where a meeting genuinely helps is for decisions with disagreement, which is a much smaller category than the calendar suggests.

Attendance inflation has its own logic

People are invited to meetings defensively, because being left out reads as a signal about status rather than about relevance. Optional attendance labels are supposed to solve this and rarely do, since optional in practice means attend unless you enjoy explaining why you did not. Each additional attendee reduces the chance that any individual speaks, which makes the meeting feel less useful and lengthens it simultaneously.

On hold for the fourth time, a named decision-maker and a short list is the standard fix, and it fails whenever the culture treats exclusion as an insult.

That is a management problem wearing a calendar problem's clothing, which is why calendar tools have never solved it.

The recurring meeting nobody can kill

A recurring booking is created once and then survives indefinitely, because cancelling it requires somebody to take a visible decision. The person who set it up has frequently left, and the remaining attendees each assume it matters to somebody else in the room. A simple audit that expires every recurring meeting after a fixed period, requiring active renewal, removes a surprising amount of the calendar.

Three clicks later, the ones worth keeping get renewed in thirty seconds, and the ones nobody defends simply stop existing without a difficult conversation. Defaults do the work that confrontation would otherwise have to, which is the general lesson of most successful process changes.

If a charge looks wrong, the boring route — written complaint, then the ombudsman or regulator — still works better than a review.

What to do when you cannot change the culture

Ask for the agenda and the decision required before accepting, since roughly half of the requests quietly resolve themselves at that point. Block your own focus time as an actual calendar event, because an empty slot is treated as available and a booked one is not.

Somewhere in the release notes, leave when your part is finished if the culture permits it, and if it does not, that is useful information about the organisation. Write the summary yourself when you can, because whoever writes the record decides what the meeting concluded. None of this fixes anything structural, and all of it buys back a couple of hours a week, which is not nothing.

The takeaway

Change the default duration first, then argue about the agenda.

None of this is an accident. Somebody drew this flow and somebody approved it.