Remote-first was supposed to trade the open-plan office for quiet, focused time. For a while it did. But five years into mainstream distributed work, calendars at remote companies look suspiciously like the ones people left behind: standups, syncs, check-ins, pre-meetings for other meetings. The commute disappeared. The meeting load came back.

How the meetings crept back

Nobody decides to over-schedule a team. It accumulates. A project hits a rough patch and gets a temporary daily sync that never ends. A manager wants visibility and adds a weekly check-in. Two teams miscommunicate once and institute a recurring alignment call. Each meeting is individually defensible. Together they fragment the day until the deep-work hours remote work promised no longer exist.

Video calling made this worse in a subtle way: a meeting costs one click, so the friction that used to limit meetings in an office, booking a room, walking somewhere, is gone. The easiest way to feel like collaboration is happening is to schedule some.

The test most recurring meetings fail

A recurring meeting earns its slot if it reliably produces decisions or unblocks work that async communication could not. Most fail that test. They exist for status, and status is exactly what written updates, dashboards, and a decent decision log do better, cheaper, and without freezing eight calendars at once.

What actually reduces the load

Frequently asked questions

Why do remote teams end up with more meetings than office teams?
Scheduling a call is the lowest-friction way to create a feeling of alignment, and remote work removed the natural friction that used to keep meeting counts down.

What is the fastest way to cut a team's meeting load?
Put expiry dates on all recurring meetings and move status reporting to written updates. Most calendars shrink noticeably within a month.

More in this section Business →