Meeting Overload: What the Research Says Actually Cuts Meeting Time

Corrected October 3, 2026: an earlier version of this article was written as the first-person account of an engineering manager. No such person or experiment existed; meetingstack.io is a desk-research publication. We rewrote the piece as a summary of published research, removed the invented results and charts, corrected a misdated Microsoft statistic, removed two statistics we could not source, and updated tool prices. See our corrections page.

Meeting load exploded after 2020, and most of the published evidence says it has not come back down. The fixes that get the most attention, like no-meeting days and blanket bans, work only with strong backing. The approach with the best case behind it is narrower: replace specific meeting types with something cheaper, one at a time.

What the data says

Microsoft's 2022 Work Trend Index found that for the average Teams user, the number of weekly meetings rose 153% between February 2020 and February 2022, and weekly time in meetings rose 252%. These are Teams telemetry figures, so they describe Teams users, not all workers.

The 2023 edition found people in "3x more Teams meetings and calls per week (192%)" than in February 2020, and that the heaviest meeting users (top 25%) spend 7.5 hours a week in meetings. The average employee spends 57% of their time communicating and 43% creating. Sixty-eight percent of people said they lack enough uninterrupted focus time, and respondents ranked inefficient meetings as the number one productivity disruptor.

The fragmentation point matters as much as the totals. If the meetings that remain are scattered across the day, the gaps between them are too short for focused work. That is why several of the tools below target the shape of the calendar, not just the number of meetings.

Fixes that tend to fail

No-meeting days without enforcement. A no-meeting day depends on everyone honoring it, and one exception can erode the norm. The best-documented success had heavy backing: Shopify paired its January 2023 company-wide calendar purge with a No Meetings Wednesdays rule, and its COO told NPR that 85% of employees were complying. The lesson is that the policy can work, but it needs executive sponsorship, not a team-level request.

Meeting audits that feel like judgment. Asking people to justify each recurring meeting can land as criticism of how they run their teams. Shopify sidestepped this by deleting all recurring meetings with three or more people at once and asking employees to wait two weeks before adding anything back, which put the burden on re-adding a meeting rather than on defending one.

Shorter default lengths alone. Cutting 30-minute meetings to 25 and 60 to 50 changes the shape of meetings, not the demand for them. If the underlying need remains, people may simply book more short meetings. In our analysis, length limits help only when paired with a way to meet the need without a meeting.

What replaces meetings instead of banning them

The common thread in the approaches below: each one gives people a cheaper way to meet a specific need, rather than telling them to meet less.

Async status updates. A recurring status meeting can become a short recorded video or written update from each lead, watched or read on each person's own schedule. Tools like Loom let viewers speed up playback and comment in threads. The trade-off is real: some people lose the social contact of a live standup, so many teams keep one short live check-in a week. (If you are evaluating async video tools, our analysis of that market covers the options.)

AI summaries for optional meetings. If you are invited as "optional" to catch a few minutes of relevant content, an AI notetaker such as Fathom, Otter or Fireflies can record the meeting and produce a summary you read afterward. Summaries miss nuance and can get action items wrong, so they suit meetings where you need the gist, not the detail. Check your recording consent obligations first; our guide to recording laws by state covers them.

Written decisions. Non-urgent decisions can move to a shared doc in Notion, Confluence or Google Docs: post the proposal, set a comment window, then resolve in writing and call a meeting only if the comments do not converge. The meetings that remain tend to be shorter because everyone has read the proposal.

Protected focus time. Calendar tools like Reclaim.ai block focus time on your calendar and move it around incoming invites. They do not reduce meetings directly. They make sure the gaps between meetings are long enough to use, which addresses the 68% of people in Microsoft's survey who said they lack uninterrupted focus time.

The math, with real prices

We have no measured before-and-after data, so here is a break-even calculation instead. Take a 10-person team at an assumed fully loaded cost of $75 per hour. Prices below are list prices on monthly billing, checked October 3, 2026:

• Loom Business: 10 users x $18 = $180 (Loom pricing)
• Fathom Team: 10 users x $19 = $190, or $15 per user on annual billing (Fathom pricing)
• Reclaim.ai Starter: 10 users x $12 = $120, or $10 per seat on annual billing (Reclaim pricing)
• Docs tool: assumed already in your stack

Total tool spend: $490 per month. At $75 per hour, that equals about 6.5 person-hours per month, or roughly 1.5 person-hours per week across the whole team. If the tools save more than that, they pay for themselves. Shopify's purge freed hours at a scale its COO likened to adding 150 employees, but your result depends on how many of your meetings are status updates and optional attendance, and on whether people actually watch the videos and read the docs. Measure your own baseline before and after.

Fathom was acquired by Superhuman in September 2026 (TechCrunch), so check its plans before you commit.

If you want to try this

Do not lead with a "meeting reduction initiative." People can hear "your meetings are bad" and get defensive. Shopify framed its purge as a reset for everyone, not a review of individuals.

Start with one meeting type. Status updates are the most obviously replaceable. Pick the meeting that costs the most collective time and replace it before moving to the next.

Do not force 100% adoption. Some people will prefer live conversation. A short optional call alongside the async update costs less than a fight over the format.

Protect 1:1s. They are the meeting type where the relationship matters more than the information exchange. Shorten them with a shared agenda if you need to, but do not cut them.

Expect an adjustment period. People worry about missing things and may schedule catch-up calls that undo part of the savings. Shopify asked employees to wait two weeks before re-adding any meeting, which gave the new rhythm time to settle.

Measure before you start. Count your meeting hours for a month before you change anything. A baseline turns "I think we have too many meetings" into a number people can act on, and it tells you afterward whether the change worked.