The hidden cost of a 30-minute meeting is closer to four hours than thirty minutes

A product manager looks at her calendar on Monday morning. Four 30-minute meetings before lunch. "Quick syncs," she calls them. Two hours of her day, allocated.

It is not two hours. It is closer to four.

Every interruption costs a focus tax that doesn't show up in the calendar. The well-cited number is 23 minutes to fully refocus on the work you were doing before. That's not a quirky finding from one study, it's the conservative end. A 30-minute meeting in the middle of a deep-work block doesn't cost 30 minutes; it costs the meeting plus the 23 minutes before it spent half-distracted preparing for it, plus the 23 minutes after it spent reorienting. Closer to 50 minutes of productive time gone, for a meeting that only put 30 minutes on the calendar.

Multiply that by attendance. Five people in a 30-minute meeting isn't 2.5 person-hours; it's roughly four. For a team where the average loaded cost is €80 an hour, that one meeting costs the company a little over €300. A 60-minute meeting with seven attendees, normal for a roadmap review, lands somewhere north of €700. Per session. Recurring weekly, that's €36,000 a year for one meeting.

The number is uncomfortable, but it's also the wrong number to lead with. The bigger cost isn't on the invoice.

It's the decision that didn't get made because nobody had focused thought time to make it. It's the engineer who never finished the migration plan because every afternoon got fragmented. It's the strategy that drifted because the founder spent the quarter alternating between 25-minute prep sprints and 30-minute review meetings, and never had the four-hour block to actually think.

Shopify made this calculation visible in 2023, canceled every recurring meeting with more than two people, and reportedly recovered 322,000 hours of team time in the first year. The widely-cited internal projection was a 25% increase in completed projects. They didn't get there by training people to be more efficient in meetings. They got there by removing the meetings, full stop, and finding that most of the work the meetings were supposed to coordinate could happen without them.

The lesson isn't "cancel everything." Some meetings genuinely need to be live, in a room, with people pushing back on each other in real time. The lesson is that the cost of the meeting is consistently underestimated, and the alternative, prep happening before the call and the call existing only for the live trade-offs, is consistently undervalued.

If you're looking at next week's calendar, the test is not "can I cancel this one." It's: "if everyone walked in with their position already written down, would this meeting still need to exist, and if so, would it still need to be this long?"