Meeting Bloat: Why Recurring Syncs Expand Until Output Stalls
Meeting bloat occurs when recurring calendar series accumulate more invitees, longer durations, and higher frequency than the underlying work requires.
1. The Default Slot Trap
Calendar tools default to 30 or 60-minute blocks and infinite weekly recurrence. By Parkinson's Law, discussions expand to fill the scheduled hour even when decisions take 15 minutes.
2. Defensive Invitee Inflation
Organisers add cross-functional peers “for visibility”. Over two quarters, a 4-person working session becomes a 12-person broadcast where 8 people multitask on mute.
Verified Research & Industry Sources on Meeting Overload
We distinguish strictly between independent academic research, platform telemetry reports, and company-reported initiatives:
Publisher: Microsoft WorkLab
Microsoft telemetry across Microsoft 365 users reported that time spent in Microsoft Teams meetings more than tripled globally since February 2020, and employees cited 'inefficient meetings' as their #1 productivity disruptor.
Publisher: Harvard Business Review (Leslie A. Perlow, Constance Noonan Hadley, Eunice Eun)
Survey of 182 senior managers across industries found that 71% considered meetings unproductive and inefficient, and 65% said meetings kept them from completing their own work.
Publisher: Bloomberg / Company-Reported Initiative (Shopify)
Company-reported initiative in which Shopify cancelled recurring meetings with more than two people and instituted Wednesday meeting-free norms to reduce recurring calendar overhead.
Publisher: Oxford University Press (Prof. Steven G. Rogelberg)
Academic research demonstrating that meeting bloat, Parkinson's Law in default 30/60-minute calendar slots, and poorly matched invitee lists degrade team engagement and deep-work capacity.
Publisher: Google Developers
Documents how Google Calendar models recurring events as a master series record with RFC 5545 RRULE definitions alongside expanded instance exceptions.
Publisher: Microsoft Learn
Specifies how enterprise calendar systems track seriesMaster events, occurrence instances, and attendee responseStatus metadata.