DEV Community

Cover image for Where did our focus time go? Running a meeting audit with your team
Sascha Mirow-Stanitzok
Sascha Mirow-Stanitzok

Posted on Edited on Originally published at sascha-ms.de

Where did our focus time go? Running a meeting audit with your team

Try this with your team: ask everyone to open their calendar for next week and look for one uninterrupted block of three hours. In many development teams, a surprising number of people come up empty. No single meeting is to blame. The daily makes sense, the business sync makes sense, the architecture round makes sense. It is the sum that leaves no room for deep work.

As a team lead I now send invitations myself, so I have had to look at this from both sides. In Reduce meetings: a meeting audit for dev teams I describe a four-week process for cleaning up recurring meetings. Here is the short version.

The real cost is fragmentation

Paul Graham's essay on maker and manager schedules from 2009 still explains the core issue well. Managers think in hourly slots, so one more meeting is just one more slot. People who build things need long stretches, and a single meeting in the middle of the afternoon breaks that time into pieces too small for hard problems. Even knowing a meeting is coming makes you pick smaller tasks.

Research by Gloria Mark and colleagues (CHI 2008) adds a twist: interrupted people in their experiment actually finished tasks faster, but reported more stress, frustration and effort. The damage does not show up in delivery numbers right away. It shows up later as exhaustion and mistakes. That is why I treat protecting focus time as part of leading with people first.

Flip the burden of proof

Shopify famously cleared all recurring meetings with more than two attendees from calendars in January 2023 and asked teams to wait before adding any back. The company later reported around a third less meeting time. Those are its own numbers, not an independent study, but the mechanics are useful even for a small team:

  1. A meeting has to justify coming back, not the other way around.
  2. A real pause shows what the team actually misses.
  3. Focus rules apply to everyone, leadership included.

The audit in a nutshell

The audit itself takes about four weeks: one week to prepare, two weeks of trial and one week to review. First you list every recurring meeting with cadence, length, attendees and a one-sentence purpose. Then you make the cost visible as person-hours per month, and note when each meeting splits a morning or afternoon in half.

The heart of it is a short set of questions for each meeting. My favorite is: what exactly would happen if this meeting were skipped for two weeks? It forces honest answers. Each meeting ends with one of four decisions: keep, shorten or meet less often, move to async, or cancel. Instead of deleting anything for good, you suspend the candidates for a two-week trial and let the team note what goes missing.

Two practical tips I like: schedule 25 or 50 minutes instead of 30 or 60, and put focus blocks into the calendar as real events so people outside the team can see them too.

Don't cut the wrong things

Some meetings I would defend in any audit: regular one-on-ones, retrospectives and, especially in remote teams, voluntary social formats. And the most common mistake is cancelling a meeting without agreeing where its decisions happen now. If that answer is "in chat", you have traded one meeting for fifty interruptions.

The other trap sits with the leader. If I keep calling spontaneous "quick five minutes" calls, every rule looks like theater. Reducing meetings is first of all a leadership job, because only a leader can push back on meetings owned by other departments and show that declining an invitation is a sign of respect for everyone's time.

What the full article covers

  • All seven audit steps, including a template for the meeting inventory
  • The complete list of five questions to ask about every recurring meeting
  • A decision table with examples for keep, shorten, async and cancel
  • How to protect focus time and write the results down as a team agreement
  • Common mistakes, an FAQ and the sources behind the figures

Read it here: Reduce meetings: a meeting audit for dev teams

📖 This is the condensed version. The full article on sascha-ms.de goes deeper – with all code samples, diagrams and a short knowledge check.


👉 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)