Too Many Meetings: How to Take Back Your Time

What is meeting overload?

Meeting overload is the point where meetings stop being a way of getting work done and become the reason the work is late. It is a problem of totals rather than of individual bookings: almost every invitation can be justified on its own terms, which is why the total escapes examination. The measure worth watching is what the meetings leave behind - how long the remaining stretches are, and whether any of them is long enough for the work you are accountable for.

The largest share is usually recurring. A series gets created for a live reason - a project that needs weekly coordination, a launch with moving parts - and the reason ends long before the series does. Nothing in a calendar expires on its own. The invitation renews every week without anyone re-approving it, and it keeps being attended out of the same courtesy that stops people asking whether it is still needed. That is where the hours are: not in the meeting booked yesterday, but in the ones that repeat until somebody cancels them.

The second source is the attendee list. Adding a name costs the organizer nothing and buys a sort of insurance: nobody can complain about being left out. The cost lands on the other side, multiplied by everyone who accepted, and most of it is paid by people invited to be informed rather than to contribute. Those are the hardest invitations to decline, because refusing a courtesy seems to need a reason. A list built from who might want to know is how one short conversation becomes several hours of company time.

The third source is the shape of what is left. A calendar reads as a total - hours booked, hours free - and the total is the wrong number. What decides whether a day is usable is its longest uninterrupted interval, and meetings spread evenly through a day can leave most of it unbooked with no interval worth starting anything in. The gaps are shorter than they look, too. The stretch before a meeting loses its front end to preparation and its back end to the reluctance anyone feels about opening work they will shortly have to drop; the stretch after it begins late, because the meeting ran over.

None of the three announces itself. Invitations are accepted one at a time, by someone looking at a single free slot rather than at a week, so the accumulated load is nobody's decision. What usually makes it visible is a deadline slipping for no other reason: the work was understood, the person was willing, and there was nowhere left to do it.

None of this is an argument that meetings are waste. Some work only happens with people in the same conversation: a decision several teams have to own, a handover where the questions cannot be predicted in advance. The complaint is about defaults - to book, to invite widely, to accept the length the software offers - because defaults are what produce a calendar nobody chose. The rest of this page takes those in order: reducing the number of meetings you attend, then running the ones that survive. What to do with the hours that come back is a planning question, holding attention inside them a focus one, and the hub holds the full method index.

How do you reduce meetings?

The moves that reduce meetings sort by how much agreement each one needs. The first are yours to start alone. The middle ones need a reply from whoever called the meeting. The last needs a whole team to agree, which is the slowest to arrange and worth the most. Work down that order, because the moves needing least agreement are the ones that survive a week when nothing else gets settled.

Start with the recurring invitations, because recurrence is where the arithmetic sits: leaving one series costs a single conversation and removes a slot from every week after it. Read down the series on your calendar and ask two things of each: what has changed since it was created, and would anyone set it up today? A fair number were built around a project that has since shipped. For the ones that answer well, ask for an end date rather than a cancellation, since a series that has to be renewed gets re-examined once and a series with no end date never does.

Then put an agenda test on anything new. No agenda, no attendance is the blunt version; the polite one does the same work: reply asking what the meeting needs to decide and what you should read first. If an agenda comes back, the meeting is better than it would have been and you can see whether you are needed for all of it. If nothing does, the organizer has often just worked out, without being told, that what they had was a topic rather than a meeting.

Could this meeting have been an email deserves rescuing from its career as a joke, because as a test it has a real answer. A meeting earns its slot when the work needs people in one conversation at one time: a decision a group has to make and then own, or a disagreement that will not resolve in writing. It loses the slot when the content travels in one direction - a status round, an update everybody will nod at. One-directional content is a document, read at the reader's speed and skipped by whoever it does not concern. Write first, and book the room when writing is the wrong shape for the work.

Declining is the move most people are worst at, and the shape that works is consistent: agree with the purpose, decline the slot, offer a substitute. The message is short - you are not needed for all of this, and you will send your notes on the one item you own beforehand. That concedes nothing about the meeting and still returns most of the hour. Send it early, while the organizer can still act on it, and keep the reason specific rather than apologetic: a long apology reads as an opening offer. For a standing invitation you rarely contribute to, ask to be marked optional instead: one message, and it holds for every occurrence.

Meeting-free days only work as a team rule. Declared alone, a quiet Thursday is a day other people book into, and defending it costs more goodwill than it returns. Agreed together - one day, or the same morning each week - it becomes something everyone can plan around. Two things decide whether it lasts: a named exception for the work that truly will not keep, and a size modest enough to be defensible, since a recurring morning is easier to hold than a whole day. The logic runs the other way too: gathering the unavoidable meetings into fewer days leaves the remaining days whole, which is Task Batching pointed at other people's calendars; its method page suggests the day-scale version outright, naming Meeting Mondays and Focus Fridays.

Getting the number as low as possible is not the goal. Cut meetings without changing anything else and the decisions still have to be made somewhere, reappearing as message threads that are slower to close. Reduction pays off only when what remains is worth attending.

How do you run the meetings that remain?

A meeting that survives the cut owes the people in it five things, all of them settled before it starts: a purpose, an agenda, an owner, a named end product, and a length taken from the work rather than the calendar's default. Together they cost the organizer a few minutes, which is the awkward part, because meetings rarely go badly for want of effort inside the room.

Purpose and end product are the same question asked twice. What will exist afterwards that does not exist now: a decision recorded, a plan people have agreed to, an answer to something blocking. If nobody can state it, the meeting is a habit rather than a piece of work, and cancelling one occurrence to see whether anybody misses it is a cheap experiment. Naming it also settles the invitation list without an argument: the people needed to produce that outcome are a much shorter list than the people who might find it interesting.

The agenda is the working half of the invitation, and it reads best as items with verbs. Decide the launch date, review the open risks, unblock the handover: each tells a reader what will happen and whether they are needed for it. Headings cannot: budget, roadmap and update name territory rather than work. Attach anything that has to be read and expect it to have been read: a meeting that opens with everyone reading has spent its most alert stretch on something people do faster alone. Take the decision early, rather than leaving it as the last item to compete with the clock.

One person has to be accountable for the meeting, and it is whoever called it rather than the most senior person in the room. The job is unglamorous: hold the agenda, notice when the conversation has drifted, say the decision out loud once it has been made, and write it where the people who missed it can read it. Meetings with nobody in that role overrun as a matter of course and end with everyone holding a slightly different account of what was agreed, which is how one meeting produces the next.

Length is the setting nobody actually chooses: the software offers a default slot, the slot gets accepted, and the agenda expands until it fits. This site files that observation under Parkinson's Law, as a rule of thumb and not something anybody has measured. Taking the length from the agenda instead usually produces something shorter, and it exposes the arithmetic: a meeting costs its length multiplied by the people in it, so shortening and shrinking pull the same lever. Timeboxing formalizes the stopping, and the pitfall named on its page is the one meetings fail on: letting the time run out and carrying on regardless. When the same item overruns every week, it wants a slot of its own.

Most meetings on your calendar are not yours to design, which leaves a smaller set of moves. Asking what a meeting needs to decide is rarely resented. Sending your part in writing beforehand sometimes removes the need to attend and otherwise improves what you contribute. Asking to be scheduled for your item, then leaving once it is done, reads as rude only when it has not been mentioned in advance. What comes back is unbroken time, and it is worth claiming deliberately: give it a block before another invitation finds the gap. That is the case Time Blocking makes for your own work - what holds a slot is defended, and what does not is available.

Methods that protect the rest of your week

This site has no dedicated meeting methods yet; articles will land in this cluster as it grows. Until then, three existing methods do the most for a meeting-heavy calendar: Timeboxing, Task Batching and Time Blocking.

Frequently asked questions