Open a typical engineering manager's calendar and you will see the problem immediately. Stand-ups, syncs, retrospectives, planning sessions, one-to-ones, stakeholder check-ins, all-hands, demos, and the twenty-minute recurring meeting that nobody is quite sure who created. Add it up and there is often less than two hours of uninterrupted time in a working day. For the engineers on your team, the picture is frequently just as bad. When meetings consume the time that should go on focused work, output slows, quality suffers, and frustration builds quietly.
Meeting overload is rarely caused by one bad decision. It accumulates gradually, one recurring invite at a time, until the calendar looks more like a schedule than a working day.
Why meeting overload happens
Most meetings are created with good intentions. A new project needs coordination, so a weekly sync goes in the calendar. A stakeholder asks for more visibility, so a fortnightly update gets scheduled. A team member struggles with a handover, so a standing slot is added. None of those decisions are wrong in isolation. The problem is that meetings almost never get removed. They accumulate silently, one at a time, until the calendar is so full that any new work has nowhere to land.
How it starts
Reasonable. A few hours a week.
Six months later
The calendar fills. Nothing ever gets removed.
- Meetings are easy to addCreating a recurring calendar invite takes thirty seconds. Cancelling one requires a decision, a message to attendees, and the implicit admission that it was not needed. The asymmetry means calendars only ever grow in one direction.
- Declining feels riskyRemoving yourself from an invite can feel like a signal that you do not care about the project or the person who organised it. Many managers and engineers accept meetings they will not benefit from because the social cost of declining feels too high.
- Projects end, meetings do notRecurring meetings created for a specific project regularly outlive that project by months. The original attendees forget why the slot exists, but nobody takes the step of cancelling it. It becomes habit rather than purpose.
- Coordination is the defaultWhen something needs attention, the first instinct is often to schedule a conversation. Async alternatives, a short written update, a recorded walkthrough, or a decision captured in a shared document, rarely feel as immediate and rarely get used instead.
Running a meeting audit
Before you can fix the problem, you need to see it clearly. A meeting audit is a structured review of every recurring meeting your team is involved in. It takes less than an hour and consistently surfaces meetings that nobody would defend if asked to justify them. The goal is not to cut everything - it is to be intentional about what stays.
Questions to ask for each recurring slot
- List everythingPull up every recurring meeting your team is involved in, not just the ones you own. Include meetings where you are listed as optional. The full picture is often more alarming than the partial one, and it is the only basis for making a fair assessment of the total load.
- Categorise honestlyFor each meeting, decide whether it is essential (produces a necessary output), marginal (has value but could be less frequent or shorter), or redundant (nobody would notice if it stopped). Most audits find that a significant proportion of recurring meetings fall into the redundant category.
- Involve the teamSend a short message or survey asking your team to rate each meeting on value. People are often reluctant to raise this unprompted, but when given a clear way to share their view, they consistently identify the same low-value meetings. Their signal makes the audit much faster and the decisions much easier to defend.
- Repeat quarterlyA one-off audit has limited effect if new meetings accumulate at the same rate as before. A brief review every quarter, five minutes at the end of a retrospective asking which meetings are no longer earning their slot, is enough to keep the calendar from drifting back.
What to cut, shrink, or convert
Once you have a clear picture of what is on the calendar, the next step is deciding what to do with each meeting. Not every low-value slot should be cancelled outright. Some should be made shorter, less frequent, or replaced with an async equivalent. The goal is to reduce total meeting time without breaking the coordination the team genuinely needs.
- Cancel ruthlesslyMeetings with no clear output, no agenda, and no owner are candidates for immediate cancellation. Send a brief message explaining that you are removing the slot and invite anyone with concerns to raise them. Most of the time, nobody does. If someone raises a genuine need, you can decide whether a new, better-defined meeting is warranted.
- Halve the frequencyMany recurring meetings started weekly because the project was active, but the pace has since slowed. A fortnightly cadence often provides enough alignment without consuming as much time. Pilot the change for four weeks before making it permanent and check whether anything actually breaks.
- Shorten aggressivelyThe default calendar slot is sixty minutes. Most coordination meetings do not need that long if the agenda is tight and the facilitator keeps things moving. Forty-five minutes signals that time matters and creates a natural break before the next meeting. Thirty minutes works for many routine sync conversations.
- Convert to asyncStatus updates, project summaries, and decisions that do not require real-time debate are strong candidates for async communication. A short written update sent to a shared channel replaces a thirty-minute meeting without losing the information, and it creates a searchable record that the meeting never would.
- Reduce attendeesNot every meeting needs every attendee. A planning session with seven people, only three of whom contribute to the discussion, is a poor use of the remaining four participants. Review invite lists on recurring meetings and remove anyone whose presence is passive rather than necessary.
Protecting focus time
Cutting meetings is only half the solution. The other half is actively protecting the time that you free up. Fragmented time - two thirty-minute blocks scattered across a day - is often as unproductive as a meeting-heavy schedule because the cost of context switching makes serious work difficult. Deep work requires sustained attention, and that requires uninterrupted blocks long enough to actually matter.
Common patterns for protecting focus time
- Model it yourselfIf you want your team to protect focus time, you need to do the same visibly. Block your own deep work time in your calendar and decline meetings that encroach on it unless they are genuinely urgent. When the team sees you treating focus time as a real commitment, they feel more comfortable doing the same.
- Agree as a teamFocus time protections work best when the whole team agrees on them together. A few minutes in a retrospective deciding on shared meeting-free windows creates norms that are easier to uphold than individual preferences, and reduces the discomfort of declining an invite that falls in a protected slot.
- Communicate externallyLet stakeholders outside the team know about any new availability constraints you are introducing. A brief message explaining that the team is protecting certain windows for focused work is usually well received. It also prevents the assumption that unavailability means avoidance rather than intentional design.
Making fewer meetings stick
The hard part of reducing meeting overload is not the initial cut. It is preventing the calendar from drifting back over the following weeks. Without deliberate habits, new meetings accumulate at the same rate as before and the improvement fades. Sustaining a lighter calendar requires ongoing decisions, not a one-off intervention.
Connecting your meeting notes and actions in one place means fewer things fall through the gaps that would otherwise require a follow-up sync. A weekly planning habit also helps, because it gives you visibility over what is building up before the calendar becomes overwhelming again.
- Set a default cadenceAgree that new recurring meetings start fortnightly rather than weekly, with a clear review point after six weeks. This raises the bar without blocking new meetings entirely. Many meetings created at a fortnightly cadence will naturally stop after a few cycles when they have served their purpose.
- Assign a meeting ownerEvery recurring meeting should have an owner responsible for its agenda, its cadence, and its continued existence. When an owner leaves or moves on, the meeting either transfers ownership or ends. Meetings without owners drift from purpose into habit.
- Use meeting notes wellOne reason meetings proliferate is that decisions and context are hard to find when they are needed later. When you capture clear notes with decisions and actions, there is less need for a follow-up meeting to re-establish what was agreed. Good notes replace the meeting that would otherwise be scheduled just to share the information.
- Celebrate the reductionWhen the team audits its meetings and removes a cluster of recurring slots, treat that as a genuine win. The instinct to see fewer meetings as less engagement is counterproductive. Show clearly that focused, high-quality work is the goal, and that a lighter calendar is part of achieving it.
Frequently asked questions
Never lose track of what was agreed
Capture actions from every meeting in one place. No more follow-up syncs just to find out what was decided.