DEV Community

Cover image for Reduce meetings: a meeting audit for dev teams
Sascha Mirow-Stanitzok
Sascha Mirow-Stanitzok

Posted on Originally published at sascha-ms.de

Reduce meetings: a meeting audit for dev teams

Reducing meetings sits near the top of many team leads' to-do lists, yet it rarely gets done. Each meeting looks reasonable on its own: the daily, the sync with the business side, the architecture round, the regular check-in with the neighboring team. Only when you add them up do you notice that your developers' calendars barely have a three-hour block left anywhere.

I care about this topic because I know both sides: first as a developer who needed long stretches of concentration, now as a team lead who sends out invitations himself. In this guide I'll show you a meeting audit you can run with your team in four weeks, without everyone ending up talking past each other in chat.

In short

If you want to reduce meetings in your team, good intentions are not enough. A meeting audit reviews every recurring meeting for purpose, attendees and alternatives, then makes a deliberate call: keep, shorten, go async or cancel. The biggest win is connected focus time, not the minutes you save. The most common mistake: cancelling meetings without agreeing where decisions and conversations happen from now on.

What you will learn in this article

  • Why meetings cost developers more than the time spent in the room
  • How to run a meeting audit with your team in seven steps
  • Which five questions to ask about every recurring meeting
  • Which meetings you should not cancel, and why

Why too many meetings hurt developers

In 2009 Paul Graham wrote a short essay that still shows up in almost every discussion about meetings. His distinction: managers plan their day in hourly slots, so a meeting is simply the next slot. "Makers", people who build things, need long uninterrupted blocks instead. For them, a single afternoon meeting chops half a day into pieces too small for demanding work.

The second point in the essay is often overlooked. Just knowing a meeting is coming changes what you take on. If you know the next meeting starts at 3 pm, you rarely begin that tricky refactoring at 1 pm. Instead you close small tickets, answer emails and skim pull requests. It feels productive, but it doesn't move the team forward on the hard problems.

Interruptions mostly cost nerves

A study by Gloria Mark, Daniela Gudith and Ulrich Klocke (CHI 2008) adds an interesting finding. In their experiment, interrupted tasks were actually finished faster, with no measurable drop in quality. The price: participants reported more stress, more frustration, higher time pressure and more effort. In other words, people make up for interruptions by pushing themselves harder.

For leaders, that is uncomfortable news. A fragmented calendar may not show up in delivery numbers for a while. It shows up later, as exhaustion, as mistakes in complex changes, and as people who code in the evening "to finally get some peace". For me, people first therefore also means taking the team's focus time as seriously as the alignment a meeting is supposed to provide.

What Shopify's calendar purge shows

The best-known example of radical cleanup comes from Shopify. In early January 2023, the company removed every recurring meeting with more than two attendees from its calendars. According to Fortune, teams were asked to wait at least two weeks before adding a meeting back, and to be very critical about it. On top of that came a meeting-free Wednesday and a fixed Thursday window for large meetings of 50 people or more.

In May 2023, Shopify's COO Kaz Nejatian described the effect in a guest article for Fast Company: around 12,000 cancelled events, roughly a third less time in meetings, and a projection of 322,000 hours saved per year. These are the company's own figures, not an independent study. I still find them valuable as a signal.

What I would take from it

If you want to reduce meetings in your own team, you don't need to copy a large company's clean sweep. The mechanics behind it work in small teams too. First, the burden of proof flips: a meeting has to justify coming back, instead of someone having to justify removing it. Second, there is a real pause in which the team notices what it misses and what it doesn't. Third, there are clear focus-time rules that apply to everyone, leadership included.

An article in MIT Sloan Management Review is also worth a look here. The authors surveyed 76 large companies that had introduced one to five meeting-free days per week in the previous twelve months. Even one meeting-free day per week went along with more autonomy, better communication and less stress. The survey relies on self-reporting, but it works as orientation.

How to reduce meetings with a meeting audit, step by step

A meeting audit is a structured inventory of all of a team's recurring meetings. You look at each meeting individually and decide together what happens to it. Plan about four weeks: one week of preparation, two weeks of trial and one week for review and agreements. The actual effort is modest; two 60-minute sessions are usually enough. Yes, you need meetings to reduce meetings. We'll live with the irony.

Prerequisites

You need access to the team's calendars, or at least everyone's willingness to share their recurring meetings. A shared table helps too, for example a spreadsheet or a wiki page. Most important is backing from your own manager in case meetings owned by other departments are affected.

Step 1: List all recurring meetings

Collect every meeting that happens regularly and that at least one team member attends. Leave out one-off meetings; they are not the problem. For each meeting, record:

Meeting Cadence Length Team attendees Who invites? Purpose in one sentence
Daily daily 15 min 7 Team Plan the day, raise blockers
Business sync weekly 60 min 4 Business side Clarify requirements
Architecture round every two weeks 90 min 5 Team lead Technical decisions

This step alone is often revealing. Some meetings have a purpose nobody can state in one sentence. In other cases, it turns out that three team members attend when one would do.

Step 2: Make the cost visible

For each meeting, calculate person-hours per month: length times attendees times occurrences per month. A weekly 60-minute meeting with four team members therefore costs around 16 person-hours a month, roughly two full working days.

Also note when each meeting takes place. A meeting at 9 am right after the daily is much kinder to concentration than one at 11 am or 2:30 pm that splits the morning or afternoon in half. I like to call these the hidden costs. They don't appear in any table, but they are often bigger than the minutes in the meeting.

Step 3: Check every meeting with five questions

This is the core of the audit. Go through each meeting with the team and answer these questions:

  1. Which decision or outcome happens here that would not happen without the meeting?
  2. Who really needs to attend, and who could read the outcome afterwards?
  3. Could the content be handled asynchronously, for example with a short text, a video or a comment on the ticket?
  4. Do length and cadence still match the need, or have they simply stayed the way they were set up a year ago?
  5. What exactly would happen if the meeting were skipped for two weeks?

The last question is my favorite. It forces honesty. "Then we wouldn't know what the business side is planning" is a good answer. "Then we'd miss something" is not.

Diagram: five review questions for every meeting lead to the decisions keep, shorten, async or cancel

Five questions per meeting lead to one of four decisions.

Step 4: Decide to keep, shorten, go async or cancel

The answers lead to one of four decisions for each meeting. Record it in the table, together with one person responsible for making the change.

Decision When it fits Example
Keep The meeting produces decisions or relationships that wouldn't happen otherwise Retrospective, regular one-on-one
Shorten or less often The purpose is right, but length or cadence are too generous Architecture round cut from 90 to 50 minutes
Go async It's mostly about information, not discussion Status meeting becomes a short update in chat
Cancel Nobody can name an outcome, or another meeting already covers it Old check-in from a finished project

A small trick helps when shortening: schedule meetings for 25 or 50 minutes instead of 30 or 60. It sounds trivial, but it creates breathing room between back-to-back meetings. I described how a status update works without a meeting in my article on the async daily standup.

Step 5: Run a two-week trial

Suspend every meeting marked "cancel" or "async" for two weeks. Don't delete them for good yet; just cancel the series for that period. That lowers the barrier for anyone attached to "their" meeting. At the same time, ask the team to note in a shared document whenever something is missing: a decision that stalls, or information that arrived too late.

Make sure you also touch meetings owned by people outside the team. Talk to the organizers, explain the experiment and ask whether one team representative would be enough. The relief on the other side is often bigger than expected, because their calendars are usually just as full.

Step 6: Protect focus time

Reducing meetings only helps if the freed-up time is connected. So agree on fixed focus blocks, for example every morning until noon, or two completely meeting-free afternoons per week. Cluster the meetings that remain at the edges of the day, right after the daily or late in the afternoon. Paul Graham describes exactly this approach for office hours at Y Combinator: grouped at the end of the day so the rest stays free.

Put the focus blocks into calendars as real events. That way, people outside the team can see the time is taken too. As a leader, you set the example: if you send invitations during focus time yourself, the rule is dead within a week. How to protect that focus time against chat messages and ad hoc requests as well is covered in my guide on team focus time.

Step 7: Review after four weeks and write it down

At the end, look at the notes from the trial with the team. Which gaps appeared? Which meeting needs to come back in a new form? How did the focus time feel? Also compare person-hours before and after; that makes the effect tangible.

Capture the results as a team agreement, such as "focus time Monday to Thursday, 9 to 12" or "every new recurring meeting needs a one-sentence purpose and an end date". How to phrase such rules together is covered in my guide to team working agreements. Also schedule a repeat audit in six months, because calendars fill up again on their own.

Which meetings you should not cancel

Not every meeting that feels like an obligation is unnecessary. A few formats I would defend even in the strictest audit.

The regular one-on-one between a leader and a team member is one of them. That's where trust, honest feedback and early warning signs come from, and no chat message replaces it. The same goes for the retrospective, because it's where the team improves its own way of working, including its meeting culture. You'll find a guide in my article on how to run a retrospective.

Be careful, too, with meetings that mainly serve a social purpose. In remote teams especially, they are sometimes the only chance for people to meet without a ticket in between. Cutting these purely for efficiency saves minutes and costs cohesion. A relaxed coffee chat every two weeks can therefore stay, as long as it's voluntary.

Common mistakes when reducing meetings

The most common mistake is cancelling meetings without replacing what they did. If the weekly sync disappears and there's no new place for decisions, everything moves into chat. Then instead of one meeting you have fifty interruptions a day, and that's worse.

A second classic: the audit covers the team's meetings but not the leader's. If you as team lead keep calling spontaneous "quick five minutes", every rule looks like theater. So check your own habits as well, and explicitly ask the team which of your meetings they find disruptive.

Third, focus blocks often exist only on paper. They sit in the calendar but get overbooked at the first urgent request. A simple agreement helps: anyone inviting into a focus block asks first. It sounds petty, but it protects the rule during the first weeks until it becomes normal.

Finally, the audit sometimes happens once and is then forgotten. New projects bring new meetings, and six months later the calendar looks the same as before. A fixed date for the repeat, ideally with a calendar reminder, prevents that.

My take

I don't think meetings are the problem. Good meetings are one of a team's most important tools, because that's where decisions get made and people learn to understand each other. The problem is meetings nobody consciously chose anymore. They stay because they once made sense and nobody has the courage to question them.

That's why, for me, reducing meetings is above all a leadership task. The team can't cancel many meetings on its own, especially not those owned by other departments. You as a leader can. And you can show by example that declining a meeting is not rude but a sign of respect for everyone's working time.

I'm skeptical of blanket rules like "no more meetings". They quickly create shadow structures where the same conversations simply happen as a "quick call". I'd rather have a team with fewer but better meetings that knows exactly why each one exists.

FAQ

How many meetings are normal for developers?

There is no fixed number. A good rule of thumb is whether each person has at least one connected block of two to three hours without meetings on most days. If that block is regularly missing, a meeting audit is worth it.

What is a meeting audit?

A meeting audit is a shared inventory of all of a team's recurring meetings. Each meeting is checked for purpose, attendees and alternatives, then kept, shortened, moved to async or cancelled. For teams that want to reduce meetings, it's the most structured way to start.

How do I decline a meeting politely?

Thank the organizer for the invitation, briefly name the reason, such as a protected focus block, and offer an alternative: a written update, a stand-in or a slot at the edge of the day. That keeps the working relationship intact.

Are meeting-free days a good idea?

For many teams, yes, especially if they want to reduce meetings and do a lot of focused development work. What matters is that the day really stays free and applies to everyone. A meeting-free day that gets watered down by every urgent request achieves little.

Your next step

If you want to reduce meetings, start with yourself. Open your own calendar today and count the recurring meetings you invite others to. Write down the purpose of each in one sentence. Where that's hard, you have your first candidate for the audit. Then invite the team to a one-hour inventory, at a time that doesn't cut anyone's morning in half.

Over to you: which meeting in your team would you question first, and what has stopped you so far? Let me know in the comments.

Sources

This post was created with AI assistance.


👉 Next step: Preparing a first one-on-one? My question cheat sheet puts the best questions on one printable page.

📬 Stay updated: New articles on serverless, AI and leading tech teams via RSS, browser push or the weekly newsletter (in German).

Originally published on sascha-ms.de. More articles on serverless, AI in everyday development and leading tech teams: sascha-ms.de/en

Top comments (0)