← all posts

Most teams have run the same experiment: cancel the recurring ones, declare a no-meeting day, send the memo about async-first work. Six weeks later, the calendar looks exactly as it did before. The question of why teams default to meetings has a precise answer — and it isn’t that people are bad at following instructions.

The regeneration is structural. Each mechanism described below is a rational response to a specific gap in how the organisation operates. Remove the symptom without addressing the gap and the symptom returns.

The pattern: why teams default to meetings even after cuts

Meeting-reduction efforts fail at a consistent rate because they treat meetings as the problem rather than as the output of other problems. The no-meeting day doesn’t reduce coordination pressure — it compresses it into the remaining four days. The cancelled recurring sync doesn’t eliminate the need it was filling — that need now finds another venue.

Teams that successfully reduce meeting volume don’t do it by declaring intentions. They do it by changing the underlying conditions that make meetings the path of least resistance. To change those conditions, you have to name them accurately first.

Why teams default to meetings: trust gaps in async communication

When you can’t be sure your message landed

The most basic driver of meeting default behaviour is simple: people schedule meetings when they can’t trust that an async message will produce a result.

This is not paranoia. On teams without shared response-time norms, messages do get missed. Decisions do stall. The person who sent the Slack message at 9am and got no response by 3pm isn’t being neurotic when they schedule a meeting — they’re being accurate about their environment. The meeting is expensive, but it’s guaranteed to produce a response. The async channel isn’t.

The mechanism is a feedback loop. Async fails once, so a meeting gets scheduled. The meeting works. Async fails again, so another meeting gets scheduled. Gradually, meeting becomes the default channel for anything time-sensitive, and async becomes the channel for things that don’t actually need to happen.

Building the response-time norms that make async trustworthy is the prerequisite for async to work at scale — not the tool, not the platform, not the channel structure. The norm.

Concrete example: an engineer sends a decision request in Slack at 9am. By 3pm, no response. They schedule a meeting for tomorrow. The meeting happens. The decision gets made in twenty minutes. No one asks why the async request failed, because the meeting worked.

Ambiguous ownership forces synchronous resolution

When no one can decide unilaterally, everyone has to attend

When decision authority is unclear, the only safe venue for making a decision is one where every stakeholder who might be affected — or who might later claim they were overruled — is physically or virtually present. Meetings become the default decision venue not because they are efficient, but because no other venue has the standing to produce a decision that sticks.

This is a structural problem, not a communication one. The team doesn’t need better facilitation or a clearer agenda. It needs documented decision rights: which roles can make which calls unilaterally, which calls require sign-off, and from whom.

Without that, every non-trivial decision requires a meeting, because the meeting is the only mechanism that confers legitimacy. The senior person’s verbal agreement in a meeting means the decision is made. The same agreement in a Slack thread does not — because if something goes wrong, the Slack thread doesn’t carry the same weight.

Handoffs that include explicit ownership and decisions eliminate a large category of ambiguous ownership situations before they escalate into synchronous resolution.

Concrete example: a team debates which cloud provider to use for a new service. Three engineers have opinions. None of them know if they’re empowered to decide. A meeting gets scheduled “to align.” The meeting produces partial alignment and one unresolved concern. A follow-up meeting gets scheduled to address the concern.

Meetings as a visibility mechanism

Attendance as proof of contribution

In organisations without explicit visibility mechanisms, attending meetings is how people demonstrate that they are present, informed, and engaged. This is not performative in the pejorative sense — it is a rational response to an environment where the meeting is the primary venue for information sharing and professional presence.

The person who skips a meeting to do focused work faces a real cost: they weren’t there when decisions were made, they don’t know what was said, and they can’t weigh in when the topic comes up later. If their absence is noticed, it signals disengagement. If it isn’t noticed, they’ve missed information that may affect their work.

The incentive structure is asymmetric. Attending a meeting that turns out to be useless costs an hour. Missing a meeting that turns out to matter can cost professional standing. Rational actors attend the meeting.

This is a systemic problem, not a personality problem. The individual isn’t being paranoid or status-obsessed — they’re responding correctly to an environment that has no other mechanism for visible participation. Telling them to skip more meetings doesn’t change the incentive structure; it just tells them to accept costs they have good reasons to avoid.

Concrete example: a team member misses a planning meeting because it conflicted with a focused work block. The following week, decisions made in that meeting affect their work and they weren’t consulted. They attend every planning meeting after that, regardless of whether they have a direct stake in the agenda.

Decision debt accumulates into meeting load

Delayed decisions don’t disappear — they schedule themselves

Decisions that get deferred don’t disappear. They accumulate. And accumulated decisions have a property that individual decisions don’t: they can only be resolved synchronously, because each deferred decision has now generated downstream dependencies that themselves need to be resolved in the same session.

Three unresolved architectural questions that were individually manageable in sprint one become a two-hour architecture review in sprint four — plus the additional decisions that now depend on them being resolved first.

The causality runs in both directions. High decision debt produces more meetings because the only way to process accumulated decisions is synchronously. More meetings produce less time for decision-making. Less decision-making time produces more deferred decisions. The cycle is self-reinforcing.

Handoffs that include explicit ownership and decisions prevent decision debt from accumulating at handoff points, which is where the majority of deferrals happen. How to write the decisions that would otherwise need a meeting addresses the documentation gap that allows debt to build.

Concrete example: a project carries three unresolved architectural questions marked “figure out later.” Three sprints later, the team schedules a two-hour review. The review resolves two of the three questions and surfaces four more that depend on the third. Two follow-up meetings get scheduled.

Meeting attendance as organisational insurance

Blame-averse cultures create calendar-averse problems

In organisations where accountability is enforced through blame rather than through clear ownership, meeting attendance functions as a form of institutional insurance. Being in the room when a decision is made means you cannot later be held solely responsible if it goes wrong. You were there. You had the information. You were consulted.

This produces meeting inflation that is entirely independent of whether the meeting is useful. The value of attending isn’t information exchange or decision-making — it’s being on the record as having been present.

The signal that this mechanism is operating is distinct from other meeting-default causes. People attend meetings but don’t contribute. They ask to be added to invite lists for meetings outside their direct remit. They express concern about being left out that is not proportionate to their stake in the agenda. The concern isn’t about missing information — it’s about missing the protection that attendance provides.

Telling these people to stop attending meetings is functionally the same as telling them to accept more professional risk. They won’t, and they shouldn’t have to — the risk is real.

Concrete example: a senior manager asks to be included in a vendor negotiation meeting they have no direct role in. When asked why, they say they “like to stay in the loop.” The actual reason is that if this vendor relationship goes badly, they want to have been in the room when the terms were discussed.

These are rational responses to irrational systems

The common thread across all five mechanisms is the same: each one is a rational response to a real structural gap.

Teams schedule meetings when async channels can’t be trusted to produce results. They schedule meetings when no one has the authority to decide unilaterally. They attend meetings when meetings are the only visibility mechanism available. They convene large synchronous sessions to resolve accumulated decision debt. They inflate meeting attendance when the culture punishes being absent from decisions that go wrong.

None of these causes are addressed by telling individuals to schedule fewer meetings. The memo doesn’t change the async trust level. It doesn’t clarify decision authority. It doesn’t create a visibility mechanism that doesn’t require attendance. It doesn’t resolve the accumulated decisions. It doesn’t make it safer to be absent.

What changes the output is changing the structural gap. Not the symptom.

This is the distinction between treating coordination as a systems problem versus treating it as a behaviour problem. A behaviour intervention — the memo, the no-meeting day, the audit that identifies “unnecessary” recurring syncs — acts on individuals in a system that continues to produce the same pressures. A structural intervention changes the conditions that generate those pressures.

If you’ve already run a structured meeting audit and watched meeting volume recover, you have evidence that the problem is structural. The audit named which meetings could go. What the audit didn’t address is why they came back.

The structural meeting audit that addresses these conditions starts from each mechanism named here and asks what would have to change for that mechanism to stop generating meetings. That is a different question than “which meetings can we cut.”

Continuum Scheduler is built on the premise that coordination problems are scheduling problems — and scheduling problems are systems problems. When a team has to hold a meeting because the async channel failed, that’s a coordination failure with a detectable cause. The tool is designed to surface those causes, not just to manage the calendar that results from them.

The mechanisms in this article aren’t cultural. They’re not personality-dependent. They’re structural, which means they’re changeable — but only if you’re working at the structural level.