Maya Ortiz had 37 minutes left to write a practice exercise for her company’s new-supervisor program.
That was the plan, anyway. At 4:47 on Tuesday afternoon, she was looking at a calendar that contained six meetings: a revenue forecast, a hiring calibration, a leadership review, a one-to-one, a customer escalation huddle, and a cross-functional launch call. Each invitation had a reasonable explanation. Two were marked required. One had been on the calendar for three years.
At 4:52, another invitation arrived: Q3 alignment. Maya accepted it before she had read the agenda.
Maya is fictional. Her calendar is not unusual.
Three months earlier, she had tried deleting one recurring meeting. The meeting returned as two shorter calls and a long string of chat messages. The scheduled hours went down. Her actual coordination work did not.
That experience changed the question she brought to her team. Instead of asking how to have fewer meetings, Maya asked what each meeting was supposed to make possible. She started a two-week meeting audit.
Start with the calendar Maya could not use
A meeting audit is a short, evidence-based review of scheduled meetings, their participants, their intended outputs, and the work that happens around them. It is not a hunt for the person with the most calendar blocks. It is a way to see where time is being spent and where coordination is being duplicated.
A useful first audit takes 10 working days to observe and one focused review session to interpret. Start with one team rather than the whole company. A team of eight to 12 people is large enough to reveal patterns and small enough to discuss them without turning the exercise into a corporate census.
Maya’s spreadsheet captured the following for every meeting, including optional invitations:
- scheduled length, actual length, and number of attendees;
- each attendee’s role and whether they contributed, decided, or only needed the result;
- the intended output: a decision, coordination, problem-solving, information sharing, or relationship and learning;
- preparation and follow-up work, estimated in minutes; and
- what would break if the meeting stopped for 30 days.
The basic cost calculation was simple. A 60-minute meeting with eight attendees represents eight scheduled attendee-hours. That is a more honest starting point than counting it as one meeting, though it still does not prove the time was wasted. Do not turn the number into a dollar figure using an arbitrary salary multiplier. The point is to compare patterns, not manufacture precision.
Maya also tracked the shape of each workday. Her team had 31.5 scheduled meeting hours over two weeks, but that figure missed an important detail: on four of the 10 days, the longest uninterrupted work block was 45 minutes. Six half-hour meetings spread across a day can do more damage to writing, analysis, or course design than one three-hour workshop, even when the total meeting time is identical.
Researcher Gloria Mark’s work on interrupted work helps explain why. The cost of a meeting is partly the meeting itself and partly the effort required to resume complex work afterward. The exact cost varies by person and task, so an audit should measure fragmentation locally instead of borrowing a universal productivity number.
Record two simple measures alongside meeting hours: the longest uninterrupted block of at least 60 or 90 minutes, and the number of separate meeting transitions before lunch. Those measures often reveal why a calendar feels full even when its total hours look defensible.
Do not read private meeting notes or score people’s performance from their calendars. Titles, roles, attendance, and short participant reflections are usually enough for a first pass. The audit is about work design, not surveillance.
Audit the work, not the invite
Maya’s first instinct was to rank meetings from useful to useless. That produced arguments. The person who organized the Monday metrics review considered it essential. The analysts who prepared the slides considered it an expensive ritual. Both views contained some truth.
A better review starts with the intended output. Meeting research associated with Steven Rogelberg places purpose, process, and outcomes at the center; duration alone cannot tell you whether a meeting deserves to exist.
Maya’s team found three very different sessions hiding under the same label of weekly sync. The Monday metrics review had 12 attendees, lasted 45 minutes, and generated nine attendee-hours before anyone counted slide preparation. It rarely produced a decision. A customer escalation huddle had four attendees and lasted 20 minutes. It regularly assigned an owner and a next action. A new-manager practice circle lasted 75 minutes with eight people, but it was the only place managers rehearsed performance conversations and received feedback on them.
The practice circle consumed more scheduled time than the escalation huddle. It was also the meeting Maya was least willing to cut.
That is the counterintuitive part of a meeting audit: a long meeting can be a high-value learning environment, while a short meeting can be a low-value broadcast. If the audit rewards brevity alone, it will preserve efficient-looking status calls and remove the sessions where people actually practice a difficult behavior.
For each recurring meeting, ask participants four questions:
- What work does this meeting make possible?
- What was the last concrete decision, handoff, or skill practiced here?
- Who must be present for that output, and who only needs the result afterward?
- What would break if we stopped it for 30 days?
The last question is more useful than asking whether a meeting is helpful. Most recurring meetings have a constituency that can describe their value in general terms. Few can name a specific failure that would follow a temporary pause.
The answers also expose unclear decision rights. If nobody can say who decides, who supplies input, and who owns the follow-through, the meeting may be compensating for an organizational problem. It could be covering weak documentation, unclear ownership, unreliable data, or a dependency between teams that has never been designed properly.
That distinction matters for meeting culture. Too many meetings are sometimes a symptom of too little clarity. Canceling the symptoms without fixing the handoff simply moves the work into private messages and side conversations.
Change meetings in place, then measure the trade-off
Maya did not introduce a company-wide meeting ban. She gave her team three possible dispositions for each recurring series: keep it with a clearer output, redesign it, or pause it for 30 days with a named owner and a check-in date.
The Monday metrics review became a written update followed by a 25-minute decision session only when the update contained an unresolved exception. That change came with a condition: the written update needed an owner, a deadline, and a clear route for escalating a problem. Otherwise, the meeting had merely been replaced by a document nobody read.
The customer escalation huddle stayed. Its organizer added the decision owner and the required pre-reading to the invitation, and ended the call when the next action was assigned.
The new-manager practice circle stayed as well, but its design changed. The first 15 minutes covered one live case, the next 45 minutes were used for role-play, and the final 15 minutes were reserved for feedback and commitments. It was now visibly a practice session rather than a discussion about developing managers.
That distinction is useful for workplace-learning teams. A meeting that helps people rehearse judgment, handle a difficult conversation, or review a real incident may be part of the learning system. Removing it because it has no formal decision can leave a gap that an online module will not fill.
A “no agenda, no meeting” rule can help with recurring sessions, but it should not become a moral test. An incident huddle may begin with incomplete information. A conflict conversation may need privacy rather than a polished agenda. The stronger rule is that every recurring meeting should state its purpose, expected output, participants’ roles, and conditions for ending the series.
Run the changes as a 30-day experiment. Track scheduled attendee-hours, but pair that number with measures of whether work still moves:
- the number of uninterrupted work blocks above the team’s chosen threshold;
- the time taken to make a few recurring decisions;
- decisions recorded with an owner and due date;
- rework, missed handoffs, or issues that appear after a meeting is removed; and
- a short weekly pulse asking whether people understood why they were invited and what they were expected to do next.
If meeting hours fall while decision time doubles, the audit failed. If attendance falls but the same coordination work appears in chat, the audit failed. If a team gains focus time and makes decisions with fewer people in the room, that is a useful result—but it still needs to be checked against the work.
Maya’s review found that one meeting could be paused, two could lose optional attendees, and one needed more time rather than less. The team recovered several usable work blocks, but one launch decision slowed after too many people were removed. Maya restored two contributors and kept the smaller forum. The audit produced a correction, not a victory lap.
When a meeting audit fails
A meeting audit fails when a leader treats the result as a target such as “cut 20 percent.” People will protect themselves. Visible meetings disappear, but coordination moves to direct messages, extra documents, or unrecorded conversations. The calendar looks healthier while the work becomes harder to see.
It also fails when every form of synchronous time is treated as waste. One-to-ones, onboarding conversations, incident debriefs, safety reviews, and manager practice may not produce a formal decision. They can still support trust, judgment, inclusion, and skill development. Protecting them requires naming their purpose, not pretending they are status meetings.
A company-wide meeting-free Friday has limits too. It can push the same meetings into Tuesday through Thursday, creating denser and more fragmented days. In a global team, removing live forums may also disadvantage people who have less access to informal decision-making. Written alternatives take time to produce and read, and they are not automatically accessible across time zones, languages, or working styles.
The evidence on meeting policies is not a universal recipe. Much of the available research relies on self-reports, observational studies, or organizations with very different kinds of work. Use published research to generate hypotheses, then test the policy against your team’s decision speed, rework, focus time, and experience.
By the end of the month, Maya stopped saying that her team had too many meetings. She could name the actual design problems: three recurring sessions had no clear output, two invited people who only needed a summary, and one important learning forum had been mistaken for a status call.
That is a more useful diagnosis than an empty calendar.
This week, choose one team, capture its next 10 working days, and ask the 30-day stop question for every recurring meeting. Schedule the review before the audit begins. The first change should be small enough to reverse—and specific enough that you can tell whether the work got better.