How Can I Reduce Meetings at Work? A Builder's Playbook

Cut meetings by defaulting to async: replace status updates with a written doc, require an agenda and an owner for every invite, and protect two no-meeting blocks each week. In a 2017 Harvard Business Review study, 71% of senior managers called meetings unproductive. Start by deleting recurring meetings for two weeks and restoring only the ones people actually miss.

What's the fastest way to reduce meetings this week?

The fastest reduction is a two-week meeting reset: cancel every recurring meeting on your calendar, then restore only the ones people actively ask for. Most recurring meetings run on inertia, not need — nobody ever scheduled a review of whether they still matter.

Run this exact sequence:

1. Export your last month of calendar events and total the hours spent in meetings.
2. Cancel every recurring internal meeting for the next two weeks.
3. Tell your team why, and ask them to flag any meeting they genuinely miss.
4. Restore only the flagged ones, each with a written agenda and a named owner.
5. Set a standing rule: no agenda, no meeting.

You will usually get back four to eight hours a week, and the meetings that return are the ones that earn their slot.

Why do most meetings waste time?

Most meetings waste time because they lack a clear decision, an owner, and a real agenda. A 2017 Harvard Business Review study of 182 senior managers found 65% said meetings kept them from completing their own work, and 71% called meetings unproductive and inefficient (Stop the Meeting Madness).

The pattern is predictable. Meetings expand to fill the invite list, status updates get read aloud instead of written down, and "quick syncs" replace decisions one person could have made and posted.

Volume is also rising. Microsoft's 2022 Work Trend Index reported that time spent in Teams meetings had more than doubled — up 252% globally — since February 2020 (Microsoft Work Trend Index). More meetings did not mean more shipped.

How do we run a low-meeting team as builders?

We keep meetings low at Botensten by defaulting every update to writing and treating a live meeting as the expensive fallback. We ship production software with AI every day, and the change that actually protected our velocity was killing the daily standup and replacing it with a written thread each morning.

Here is the trade-off we hit. When we first went async, decisions slowed for about a week because people were used to "deciding in the meeting." We fixed it with a rule borrowed from Amazon, whose leadership replaced PowerPoint with narrative six-page memos read silently at the start of meetings (Amazon's 2016 shareholder letter). Now anyone proposing a change writes a short doc with the decision, the options, and a deadline.

We only call a live meeting for three things: a real disagreement that text keeps looping on, a sensitive people conversation, or a live build session where we screen-share and code together. Everything else is a document. That single default — write first, meet only when writing fails — cut our meeting load by more than half without slowing a single release.

Which meetings should you keep, cut, or make async?

Keep meetings that require live human judgment; cut meetings that only move information; make async anything that is a status update or FYI. The test is simple: if the meeting has no decision to make, it should be a document.

Trim the ones you keep. A 30-minute default beats a 60-minute default, and a named owner beats an open floor.

What replaces a meeting?

Almost every recurring meeting can be replaced by a written artifact plus a clear owner and a deadline. The replacement is not silence — it is a document people actually read and respond to.

Practical swaps that work:

• Status meeting to a shared dashboard or a weekly written update.
• Decision meeting to a one-page proposal with options and a deadline to object.
• Brainstorm to a shared doc where people add ideas first, then one short live session to choose.
• Onboarding walkthrough to a recorded video plus a checklist.
• "Quick question" meeting to a threaded message with a clear ask and a response-by time.

Each swap does two things: it creates a searchable written record, and it lets people contribute on their own schedule instead of blocking a calendar slot.

How do you protect focus time without looking difficult?

Protect focus time by blocking it on the shared calendar as real, named events and setting your status to heads-down. Two protected blocks a week, treated as firmly as any meeting, is enough to change your output.

Make the blocks visible and specific. "Deep work — feature build" reads as legitimate; a vague "busy" invites people to book over it. Cal Newport argues in Deep Work that concentrated, distraction-free effort is the rare skill that produces the most valuable output — and it cannot survive a calendar sliced into 30-minute fragments.

Books like Michael Hyatt's Free to Focus, Nir Eyal's Indistractable, and Daniel Pink's When all land on the same operator move: decide in advance when your best hours are, and defend them on purpose. You are not being difficult. You are making your calendar match your strategy.

Related reading

• How Do I Manage My Calendar? A Builder's Honest System