Back-to-back scheduling is the main source of meeting fatigue

What it is

Calendar days packed rim to rim — nine to ten to eleven, lunch on a call — are the dominant structural source of meeting fatigue. Any single meeting's drain is modest; what breaks people is zero recovery time: the previous session's residue uncleared and physiological arousal un-lowered as the next one begins, fatigue compounding meeting over meeting. Back-to-back is not a personal time-management failure but a product of calendar defaults: on-the-hour alignment, sixty-minute default, no buffer — the system manufactures stacking.

Why it happens

Two mechanisms make stacking far more damaging than the same total duration spread out. Physiologically, meetings are high-arousal events whose accumulated sympathetic activation needs gaps to subside — under consecutive meetings, stress climbs monotonically with session count instead of sawtoothing back down, which physiological measurement studies have observed directly; with short breaks inserted, the accumulation is markedly lower. Cognitively, switching from one meeting to the next inevitably leaves attention residue: unresolved items from the previous topic still occupy working memory, and the person sits in the new meeting with the old thread still running in the background. The gap's function is not just rest — it is also finishing the last session (notes, tidying, closure) and preparing the next (pre-reading, context switching); a zero-buffer schedule squeezes out both, so they colonize the first minutes of the new meeting, and every session opens on an uninitialized mind. On-the-hour alignment makes it worse: meetings get booked to start and end on the hour, a sixty-minute meeting fills its sixty-minute slot exactly, and lateness plus overruns eat the buffer that never existed.

Studying it

Wearable physiological measurement offers a direct evidential path: participants wearing heart-rate-variability or EEG devices across whole days, comparing stress-marker trajectories between buffered days and stacked days — monotonic accumulation under stacking versus sawtooth recovery with gaps has been demonstrated in field studies of this kind. Calendar analytics relate buffer-length distributions to self-reported fatigue to test the marginal returns of gap length. Methodological caveats: observational correlations between meeting load and fatigue are contaminated by self-selection — senior people have more meetings and also report more fatigue — so causal reading requires within-person, within-day comparisons; and the effect of a "break" depends on what fills it (scrolling a phone differs from leaving the screen), so interventions must log gap behavior, otherwise the effect of "having a gap" gets credited with what "rest quality" produced.

Where it stops holding

The value of gaps varies by meeting type: after meetings demanding focus and emotional labor (reviews, client calls), recovery needs are greatest; between listen-only broadcasts, short buffers suffice. Under flexible schedules some people prefer batching — meeting-dense blocks followed by long recovery — and forced fragmenting breaks their rhythm, so recovery structure should be personalizable. A minority of high-arousal individuals report flat fatigue growth across stacks; individual differences are large, so scheduling rules should be team defaults, not personal mandates.

Applying it

• Change the team calendar's default meeting lengths to 25 and 50 minutes, automatically leaving five to ten minutes of buffer per hour slot — eliminating stacking at the tool-default level.
• Enforce a fifteen-minute recovery block between consecutive high-intensity meetings (reviews, clients), written into the team scheduling norm.
• Build pauses into long sessions: any meeting over ninety minutes gets a five-minute away-from-screen break every fifty minutes.
• Reserve weekly no-meeting blocks (e.g., deep-work mornings), making "schedulable time" an explicit budget instead of a default-unlimited resource.
• Verification: from calendar data, compute per-person stacking counts (adjacent meetings with under ten minutes between them) and their correlation with self-reported fatigue; after shortening defaults, track the stacking rate and afternoon self-rated energy.

Related

• Same group: V5.11.2 Constantly seeing one's own video adds cognitive load · V5.11.3 No physical movement between scenes accelerates fatigue accumulation · V5.11.4 The always-on-camera expectation should be explicitly relaxable · V5.11.5 Fatigue shows up as reduced participation and decision quality in late meetings
• Nearby: V10.05 Boundaries and Sustainability · V5.09 Meetings versus Documents
• Search terms: meeting recovery · attention residue · back-to-back meetings · calendar default