Meeting Load: How to Measure It and What to Cut

Meetings are the largest single block of recoverable time in most knowledge organisations, and almost nobody knows how much of it there is. The number is available in your calendar system, it takes an afternoon to extract, and it usually surprises the leadership team that authorised it.

For further product context on how Microsoft Teams tracks activity, consult here.

Work-design and worker-wellbeing resources are available through the NIOSH Total Worker Health program.

Get the number first

Do not start by cutting meetings. Start by measuring, because the argument for change is the number and because you will need a baseline.

From your calendar platform, for one representative month:

Hours in meetings per person per week. Average, and the distribution — the average conceals the people at thirty hours.

By role and level. Meeting load usually rises steeply with seniority, and then those people set the norms for everyone else.

Recurring versus one-off. Recurring meetings are where the recoverable time is, because nobody re-authorises them.

Average attendance. A weekly hour with twelve people is twelve hours.

Fragmentation. How many uninterrupted blocks of two hours or more exist in a typical week. This is the number that matters most for work requiring concentration, and it is usually shockingly low.

Meeting cost. Attendees multiplied by duration multiplied by loaded hourly cost. Crude, and effective in a leadership conversation.

What the pattern usually shows

Four findings recur in almost every organisation that runs this exercise:

Recurring meetings dominate. Most of the load is standing meetings that were created for a reason that has since gone away, and that nobody has authority to cancel.

Attendance is defensive. People attend because not attending is read as disengagement, or because they fear missing a decision. Neither is about the meeting's content.

Seniority multiplies. A director's calendar becomes the template. If leadership schedules back-to-back, everyone else does.

Deep work has nowhere to live. Meetings scattered through the day leave no block long enough for concentrated work, so that work moves to evenings — which for non-exempt staff is a wage and hour problem as well as a productivity one. See off-the-clock work and context switching.

The audit

For every recurring meeting, ask four questions:

1. What decision does this produce? If the answer is "we share updates," it is a document, not a meeting.

2. Who actually needs to be here? Distinguish people who decide, people who contribute, and people who are informed. The third group does not need to attend.

3. What happens if we cancel it for a month? The most useful question available, because it can be tested rather than argued.

4. Is the frequency right? Weekly meetings created when something was urgent frequently outlive the urgency.

The changes that recover the most time

Ordered by effect per unit of effort.

Cancel for a month and see. The single most effective intervention. Suspend every recurring meeting for four weeks, and reinstate only those that someone actively asks for. Most are not asked for.

Make attendance genuinely optional for anyone not deciding or contributing, and make declining socially safe. This requires a leader to decline visibly and repeatedly before anyone believes it.

Default to 25 and 50 minutes rather than 30 and 60. It creates recovery time between meetings and it costs nothing.

Require an agenda with a stated decision. No agenda, no meeting. This one rule eliminates a meaningful share of them by itself.

Convert status meetings to written updates. A written update takes less time to produce than a meeting takes to attend, is available to people who were not there, and is searchable later.

Protect blocks. A no-meeting day, or a protected morning. The value is in the uninterrupted block, not in the total hours saved — see below.

Cap attendance. A limit forces the "who actually needs to be here" question to be asked every time.

Record and share. Reduces defensive attendance, because missing a meeting stops meaning missing the information.

The fragmentation point

Cutting total meeting hours is worth less than consolidating them, and this is frequently missed.

Four one-hour meetings spread through a day leave four short gaps, none long enough for work requiring sustained concentration. The same four hours in a single block leaves a usable half-day.

Measure the number of uninterrupted two-hour blocks per person per week, and treat that as the target — not total meeting hours. Consolidating meetings into defined windows recovers usable time without cancelling anything, which makes it politically far easier.

What not to do

Do not mandate a cut without changing the work. "Reduce meetings by 30%" produces the same coordination happening in messaging apps, which is worse — it is continuous rather than scheduled.

Do not cancel the meetings people rely on for information without replacing the information flow. The predictable result is more one-to-one interruptions.

Do not exempt leadership. If the executive team keeps its meeting load, nothing changes anywhere else.

Do not use meeting analytics for individual performance assessment. Aggregate patterns are useful; a per-person meeting-hours score in a review is surveillance with extra steps. See productivity surveillance.

Measuring whether it worked

Re-run the same extract a quarter later:

• Meeting hours per person per week
• Uninterrupted two-hour blocks per person per week
• Recurring meeting count
• Average attendance per meeting

And one qualitative question in your next engagement survey: do you have enough uninterrupted time to do your work?

If meeting hours fell and the qualitative answer did not improve, the coordination moved somewhere else rather than disappearing — usually into messaging, which is the outcome to watch for.