Here is a common scenario: 22 scheduled meetings in one week. Maybe 6 hours of actual coding across the entire five days. Not as a manager - as a senior engineer at a 200-person startup.

That kind of week is the trigger for change - but the challenge is reducing meetings without becoming “that person who never comes to meetings.”

Here is what actually works.

The Categorization Step

Before you can reduce meetings, you need to understand which ones are actually worth attending. Spend one week logging every meeting with one of four tags:

  • Essential - you are a decision-maker, you have unique information, or your absence would block others
  • Useful - you learn things or contribute, but you are not central
  • Catchup - you could have gotten the same information from a Slack summary or a doc
  • Attendance theater - nobody would notice if you were not there

In practice, most engineers have 30-40% of their meetings in the Catchup and Theater categories. That is the slack worth recovering.

Strategy 1 - The 5-Minute Email Test

Before accepting any new recurring meeting invitation, ask: “Could the organizer have sent a 5-minute email instead?”

If yes, reply to the invite with something like: “Thanks for the invite - to make sure I come prepared, could you share a quick agenda or the specific decisions you need input on?”

Two things happen. Either they send the agenda and you now know whether to attend, or they realize they could have just sent an email. About a third of meetings declined this way never happen - the organizer figures it out asynchronously.

Strategy 2 - Batch Your Meetings

Engineers lose more time to meeting context-switching than to the meetings themselves. Jumping from a coding session into a 30-minute meeting and back destroys your deep work block even if the meeting was useful.

A strategy that works well: move all meetings to Tuesdays and Thursdays, 11am-2pm. Monday, Wednesday, Friday become protected deep work days. Block the calendar explicitly: “Focus block - no meetings.”

The key is being upfront about it. Tell your manager: “I’m blocking Mondays for focused coding time - is there anything critical that would need to change?” Most managers support this when asked directly and when output visibility is maintained.

Strategy 3 - The Standing Agenda That Kills Recurring Bloat

Recurring meetings grow. Someone adds a weekly sync. Then a biweekly architecture review. Then a Wednesday morning standup that duplicates the Monday standup. Before long, your calendar looks like a hospital schedule.

For every recurring meeting you own or are central to, audit quarterly:

  • What decision has this meeting made in the last four weeks?
  • Could this happen asynchronously?
  • Is the frequency right - should this be biweekly instead of weekly?

A 30-minute meeting that happens weekly is 26 hours a year. Most weekly syncs could be biweekly with no loss.

Strategy 4 - Be Useful When You Are There

This sounds counterintuitive in a post about reducing meetings, but it matters. The engineers who successfully cut their meeting load are the ones who are known for being high-signal when they do show up.

If you come prepared, ask sharp questions, and help reach decisions faster - people want you in the room for the right meetings, not all meetings. If you show up distracted and half-participating - people add you to everything as a hedge.

Reputation for meeting quality gives you leverage to skip the ones that are not worth it.

Strategy 5 - The Async-First Offer

When someone requests a meeting with you for something that feels like it could be solved in writing, offer async first:

“I want to make sure I give you a useful response - could you drop the key question in Slack/email so I can think through it properly? Happy to jump on a call if it gets complex.”

This is not a rejection. It is offering a higher-quality interaction. Most people take you up on it, and you both save 30 minutes.

What Does Not Work

Setting your status to “busy” without actually communicating. People just add you to the next meeting anyway and resent the mystery.

Declining meetings without explanation. If you decline something, give a one-line reason and offer an alternative (“I have a focus block - can I read the notes after and follow up async?”).

Going fully async-only in a team culture that values meetings. You will be seen as uncooperative. Context matters. Match your team’s communication norms while nudging them toward less waste.

The Numbers After 6 Months

Engineers who apply these strategies consistently see their meeting load drop from 20+ meetings/week to 9-11. Output - measured by features shipped and code reviewed - goes up. Managers notice and call it out positively. Nobody says anything negative about attendance.

The key is being transparent about the approach and reasoning, not just quietly disappearing from calendars.

Bottom Line

You will not win meeting freedom by ignoring invites or being passive-aggressive about it. You win it by being genuinely useful in the meetings that matter, having an honest conversation with your manager about protecting deep work time, and systematically auditing which meetings you are actually essential for versus which ones you have inherited by inertia. Start with the audit. It takes an hour and the data usually surprises you.