Cutting Meetings on a Distributed Team: Start With the Ones That Exist to Answer Questions

Most meeting-reduction efforts are announced as a target: cut thirty percent, or declare a no-meeting day. Both produce a brief improvement and a return to baseline within a quarter, because neither addresses why the meetings were booked. Meetings are booked because people need something, and if the need survives the cut, so does the meeting.

"Calendar is full and nothing got decided."

Why blanket cuts fail

When a meeting is removed without removing its purpose, the purpose finds another route. Usually that route is direct messages, which is a worse outcome in three specific ways: it interrupts one person at a time rather than a scheduled group, it produces no record anyone else can read, and it concentrates on whoever is most responsive rather than whoever is most relevant.

So a team can genuinely halve its meeting hours and feel busier afterwards. The calendar improved and the working day got worse. This is the most common outcome of a no-meeting-day policy, which is why no-meeting days work until someone needs an answer.

Sort by purpose, not by length

Every recurring meeting exists for one of four reasons. Label each one honestly, using what actually happened in the last three instances rather than the calendar title.

• Decide. A choice gets made that would not have been made otherwise. Keep these, protect them, and give them a pre-read.
• Argue. A disagreement gets resolved. Keep these and hold them sooner than you currently do.
• Connect. People build the relationship that makes the other three possible. Keep these, make them rarer and better.
• Inform. Information moves from some heads to others. This is the category to attack, and on most distributed teams it is the majority of recurring hours.

The informing category includes status meetings, project updates, round-robin reports, and any meeting where one person speaks while others wait for their turn. It also includes the meetings booked so that someone can ask a question they have been carrying for two days.

A two-week meeting audit

Ask every meeting owner to answer three questions after each instance, in one line. What decision came out of this? Who could have skipped it? Could the content have been written?

Answer pattern	What it means
No decision, three times running	It is an informing meeting. Retire it.
Half could have skipped	Cut the invite list, keep the meeting
Content could have been written	Write it, and keep ten minutes for questions
A real decision, every time	Protect this slot, defend it from creep

Two weeks of this produces an evidence base rather than an argument, which matters because meeting defence is emotional. "We had no decisions in three sessions" ends a discussion that "I think we have too many meetings" does not.

What to cut, in order

First, any recurring meeting whose agenda is a round of updates. Second, any meeting where the same person speaks for more than half the time to people who could have read it. Third, the standing weekly that survives because cancelling it feels like a statement. Fourth, any meeting that exists so people can ask the attendees questions.

That fourth category is the interesting one, because the meeting is a scheduled opportunity to interrupt. It exists because between meetings, getting an answer is hard, so people bank their questions and wait for the slot. Removing the meeting without fixing that just converts banked questions into direct messages.

What has to exist between meetings

A meeting that exists to answer status questions can only be retired if those questions can be answered another way. Otherwise you are not cutting the cost, you are redistributing it onto individuals.

This is what StandIn is for. Each person spends ninety seconds at the end of their day confirming a brief, mostly pre-drafted from the work they already did. While they are off, their StandIn answers questions from that brief in their words, with a source under every answer, and never guesses. What moved, what is blocked, who owns the call: available at the moment someone needs it, without a meeting and without interrupting anyone.

With that in place, the informing meetings can genuinely go rather than merely move, and what remains on the calendar is deciding, arguing, and connecting. That is a much shorter week and a much better one. See StandIn for leadership teams.

Common Questions

How many recurring meetings should a distributed team have?

Fewer than most have, and the right number depends on decisions rather than headcount. A useful target is one protected decision slot per seam per week, one team connection slot, and nothing else recurring. Everything else should be booked when there is a reason.

What is the fastest meeting cut with the least risk?

Cancel the recurring status meeting for two weeks and see what breaks. Usually nothing breaks and a handful of questions surface, which tells you exactly what the meeting was carrying and how to replace it. Two weeks is long enough to be a real test and short enough that nobody panics.

Should we cut the invite list or the meeting?

Cut the invite list first, since it is politically cheaper and often gets most of the saving. A meeting with four people who are deciding something is fine. The same meeting with eleven people, seven of whom are attending in case something relevant comes up, is a broadcast with a high price.

How do we stop meetings coming back?

Require a stated decision for any new recurring meeting, and review every recurring slot quarterly against the three audit questions. Meetings return because nothing ever forces them to justify themselves twice.