A full calendar used to make me feel important. Back-to-back meetings, always in demand, always "in the loop." Then I started actually measuring what those meetings cost — not in the thirty minutes they occupied, but in everything around them — and I realized my team's biggest productivity problem wasn't skill or effort. It was that we never had time to actually work.

The story

My team was busy and frustrated. People were online all day, clearly working hard, and yet things crawled. When I mapped out a typical engineer's calendar, the problem jumped out: their day was shredded into fragments by meetings. A 30-minute meeting at 10, another at 11:30, a standup, a sync at 2. Technically only two hours of "meetings." But there was no block longer than about 45 minutes anywhere in the day to do real, deep work.

That's the hidden cost. A meeting doesn't just take its scheduled time — it takes the focus on either side of it. Engineering is deep work; it needs long, uninterrupted stretches to get into the hard problem and stay there. A meeting dropped into the middle of the morning doesn't cost thirty minutes. It can cost the entire morning, because it shatters the only block where real progress was possible.

We were paying for those meetings in our most valuable currency — focus — and the bill was enormous. People weren't slow. They were never given a runway long enough to take off.

What we changed

We got ruthless about meetings. Every recurring one had to justify its existence; several didn't survive. We moved a lot of status-sharing to async writeups, which were faster to produce and read than the meetings they replaced. And we protected large blocks of "no meeting" focus time so engineers actually had runways to do deep work.

The change was dramatic and fast. The same people, the same skills — but now with the focus time to use them. Things shipped that had been stuck for weeks. And morale jumped, because nothing is more demoralizing than wanting to do good work and never being given the uninterrupted time to do it.

A meeting costs far more than its length. It costs the focus on both sides of it — and for deep work, that can be the whole day.

Key lessons

Meetings have a hidden multiplier. The real cost includes the fragmentation around them, not just the time inside them.

Deep work needs long runways. Engineering can't be done well in 30-minute gaps. Protect large blocks or accept that little gets built.

Most status meetings can be async. A short writeup is usually faster to produce and consume than the meeting it replaces — and it doesn't shred anyone's day.

Busy calendars hide broken focus. A full schedule can be the very thing preventing the work it's supposed to coordinate.

Action steps

  1. Audit your team's calendars for focus blocks. If there's no stretch longer than an hour, that's your real productivity problem.
  2. Make every recurring meeting justify itself. Cancel the ones that exist out of habit. Default to no.
  3. Move status to async. Replace update meetings with short written updates people read on their own time.
  4. Protect no-meeting time. Establish real focus blocks — half-days or specific days — and defend them as a team.
  5. Make meetings earn their cost. A meeting should need a decision or a discussion that genuinely requires people in a room. If it doesn't, it's a document.

Final thoughts

I used to wear a packed calendar like a badge. Now I see it as a warning sign. The most productive periods my teams have had came not from working more, but from meeting less — from giving people back the long, quiet stretches where real engineering actually happens.

Meetings aren't free, and they aren't cheap. They're one of the most expensive things you can put on a builder's day, and most of them don't earn it. Cut the ones that don't, protect the focus, and watch how much your team was capable of all along.