On the first working day of January 2023, Shopify pushed a bot into every employee’s calendar and deleted all recurring meetings with three or more people. Twelve thousand events, gone. COO Kaz Nejatian reported the result: 322,000 hours reclaimed, a 33% drop in time spent in meetings per employee, and a projected 25% increase in completed projects by year end. Nejatian said he received more positive feedback on this single decision than on anything else he’d done at the company.

Most managers don’t have the authority to nuke an entire organization’s calendar. But every manager has the authority to audit their own team’s meetings. And almost nobody does it.

Meetings Accumulate Like Inventory

Meetings are the one operational input that grows without anyone placing an order. A cross-functional project spins up a weekly sync in March. The project ships in June. The meeting continues into October because nobody clicks “delete series.” A manager inherits a team with a Monday standup, a Wednesday checkpoint, and a Friday wrap-up. Each one made sense to the person who created it. Together, they consume five hours of every team member’s week before any actual work begins.

Atlassian’s 2024 State of Teams research found that 72% of meetings are ineffective at their stated purpose: disseminating information, encouraging collaboration, or accomplishing tasks. Employees reported spending 31 hours per month in meetings they considered unproductive. That is nearly four full workdays of salary cost spent in rooms (physical or virtual) producing nothing.

The pattern compounds. Microsoft’s Work Trend Index found that the average employee now spends 57% of working time communicating (meetings, email, chat) and only 43% creating (documents, code, designs, plans). Sixty-eight percent of people say they don’t have enough uninterrupted focus time during the workday. The meetings aren’t just consuming hours; they’re fragmenting the hours that remain.

When I took over IT operations leadership at a mid-sized organization, I counted the recurring meetings on my team’s calendars during my first week. Seventeen standing meetings per week across a team of nine people. Some of those meetings existed because a problem surfaced two years earlier and nobody retired the fix once the problem was resolved. Others existed because someone wanted visibility into something they could have gotten from a shared dashboard. Three were status updates that duplicated information already captured in our ticketing system.

Nobody questioned them because nobody’s job was to question them.

The Cost Nobody Calculates

A Harvard Business Review survey of 182 senior managers found that 71% consider meetings unproductive and inefficient. Sixty-five percent said meetings prevent them from completing their own work. The study estimated that organizations spend roughly 15% of their total labor hours in meetings, with senior executives averaging 23 hours per week.

Bain & Company’s research on meeting economics adds a multiplier most people miss: every person added to a meeting beyond seven reduces decision-making effectiveness by approximately 10%. That eight-person “alignment meeting” running weekly for 90 minutes isn’t just costing eight person-hours. It’s producing worse decisions than a five-person meeting would.

Atlassian puts the aggregate number at $37 billion per year in salary costs wasted on unnecessary meetings in the United States alone.

But salary cost is the easy math. The harder cost is fragmentation. A day with six hours of open time but four scattered meetings is functionally worse than a day with four unbroken hours and zero meetings. The scattered day produces shallow work: checking email, responding to Slack, skimming a document. The unbroken day produces the thinking, planning, and problem solving that moves projects forward. Every meeting on the calendar doesn’t just consume its own time slot; it degrades the slots around it.

Running the Audit

A meeting audit takes one afternoon and pays for itself within a week. Here is the process I’ve used across multiple teams, in my own operations roles and in fractional COO engagements through Ops Harmony.

Pull the inventory. Export your team’s recurring meetings for the past month. Every standing sync, every recurring 1-on-1 (those are exempt from cuts, but include them for completeness), every weekly review, every cross-functional touchpoint. For a team of eight to twelve people, you’ll typically find between 12 and 25 recurring events.

Classify each meeting. Sort them into four categories:

Decision meetings exist to make a specific choice with the people who have authority and context. These have a clear outcome: the team walks out with a call made. These are your highest-value meetings, and they’re worth running well.

Information meetings exist to transfer knowledge from one group to another. Status updates, readouts, briefings.

Creation meetings exist to produce something together: design reviews, planning sessions, retrospectives.

Ritual meetings exist because they always have. Nobody can name what they produce, but removing them feels wrong.

In my experience, 40% to 50% of a team’s recurring meetings fall into the information or ritual categories. Those are your audit targets.

Apply the five-question filter. For each information or ritual meeting, ask:

1. What decision or output does this meeting produce that cannot be produced asynchronously?
2. If we canceled this meeting for three weeks, what would break?
3. Who on the invite list hasn’t spoken in the last three sessions?
4. Does this meeting exist because of a problem we’ve already solved?
5. Could a shared document, a dashboard, or a Slack update replace this meeting entirely?

If a meeting can’t pass at least questions one and two, it’s a candidate for elimination or restructuring.

Act on the results. For each meeting that fails the filter, choose one of three outcomes:

Kill it. Delete the recurring event. Tell the attendees why. If nobody objects within two weeks, it was dead weight.

Shrink it. Reduce frequency (weekly to biweekly), duration (60 minutes to 30), or attendees (eight people to four). The Bain research on decision effectiveness makes the attendee reduction especially valuable.

Convert it. Replace the meeting with an asynchronous alternative. A Monday status email. A shared document. A recorded walkthrough. A Slack thread with a standard template.

What Changes After the Audit

When I ran this process on my own team’s calendar, we eliminated five recurring meetings and converted three more to asynchronous updates. That freed approximately 11 hours per week of cumulative team time. Not all of that went to deep work; some got absorbed by other demands. But the qualitative shift was immediate. Two senior team members told me the following week that they’d completed a backlog item they’d been pushing for months, simply because they had a three-hour unbroken window on Wednesday afternoon that hadn’t existed before.

Shopify’s experience confirms this at scale. After their calendar purge, time per employee spent in meetings dropped 33% in the first two months. The company estimated a 25% lift in completed projects. And most of the deleted meetings never came back. The teams that needed coordination found leaner ways to do it. The teams that didn’t need coordination simply stopped pretending they did.

The key insight: meetings rarely get challenged because nobody owns the meeting calendar as a system. Individual meetings have owners. The aggregate load doesn’t. Your operating rhythm should include periodic reviews of what consumes your team’s hours, and meetings are the largest controllable expense on that list.

Making the Gains Stick

A one-time audit produces one-time results. Meetings accumulate again because the organizational forces that create them (new projects, new stakeholders, new processes) never stop. The managers who maintain clean calendars build three habits:

Sunset dates on every new recurring meeting. When you create a recurring meeting, set an end date four to six weeks out. When the end date arrives, the meeting dies unless someone actively renews it. This inverts the default: instead of meetings persisting until someone kills them, they expire unless someone argues they should continue.

Quarterly calendar reviews. Once per quarter, spend 30 minutes reviewing your team’s recurring meeting list. Apply the five-question filter. This takes less time than a single unnecessary meeting and prevents the slow creep that turns a clean calendar into a cluttered one.

Protect the time you recover. The hours freed by an audit will be consumed by other meetings within weeks unless you actively defend them. Block focus time on your team’s calendars. Establish no-meeting windows that your team can count on. The audit creates space; without deliberate time management, that space fills back in.

If you’re the bottleneck on your team and you’re in back-to-back meetings from 9 AM to 4 PM, the meeting audit is the fastest operational lever you can pull. Not because meetings are inherently bad, but because the meetings nobody evaluates always outnumber the ones that earn their place on the calendar.