Compress meetings into contiguous blocks on designated days — even distribution across the week destroys maker time on every day
Compress meeting schedules into contiguous blocks on designated days rather than distributing them evenly across the week to preserve multi-hour maker time blocks on remaining days.
Why This Is a Rule
This is the operational implementation of Consolidate meetings into 1-2 designated days — meeting distribution destroys more capacity than meeting duration (consolidate meetings to 1-2 days). Where Consolidate meetings into 1-2 designated days — meeting distribution destroys more capacity than meeting duration establishes the principle, this rule specifies the compression mechanism: meetings within designated days should be contiguous — back-to-back with minimal gaps — rather than scattered with 30-60 minute gaps between them.
Scattered meetings within a meeting day produce the same fragmentation problem as scattered meetings across the week: a 1-hour gap between two meetings isn't long enough for deep work but is long enough to feel like wasted time. You spend the gap checking email, handling small tasks, and watching the clock for the next meeting. Contiguous compression eliminates these phantom gaps: meetings run 9am-12pm as a solid block, freeing 1pm-5pm as a solid maker block. The day has two clear modes rather than a patchwork of fragments.
The deeper principle is batch processing applied to coordination work. Just as manufacturing batches similar operations to minimize setup time, contiguous meeting compression batches all coordination into a single continuous session, paying the "meeting mode" setup cost once rather than repeatedly throughout the day.
When This Fires
- When implementing Consolidate meetings into 1-2 designated days — meeting distribution destroys more capacity than meeting duration's meeting-day strategy and deciding how to arrange meetings within those days
- When meeting days still feel fragmented despite having "designated meeting days"
- When gaps between meetings produce dead time rather than productive time
- Complements Default to 25 or 50-minute meetings instead of 30 or 60 — automatically create transition buffers without individual negotiation (25/50-minute defaults) by ensuring even shortened meetings are packed together
Common Failure Mode
"Spreading meetings out for breathing room": scheduling meetings with 45-minute gaps between them, believing the gaps provide recovery time. In practice, the gaps are too short for deep work and too long for genuine rest, producing a day that's neither productive nor restorative. Better to compress meetings tightly and create one large recovery/maker block than to distribute small useless gaps.
The Protocol
(1) On designated meeting days, stack meetings consecutively: 9:00-9:50, 10:00-10:50, 11:00-11:50. Use Default to 25 or 50-minute meetings instead of 30 or 60 — automatically create transition buffers without individual negotiation's shortened durations to create 5-10 minute micro-buffers between meetings without creating unproductive gaps. (2) Aim for a single contiguous meeting block (e.g., morning = meetings, afternoon = maker time) rather than meetings scattered throughout the day. (3) When scheduling, offer times that extend the existing meeting block rather than creating a new one: "I have meetings 9-11, could we do 11?" rather than "I'm free at 2." (4) Protect the non-meeting portion of meeting days as fiercely as you protect non-meeting days. (5) Accept that meeting days will feel intense — that's the cost of compression. The benefit is that non-meeting time is genuinely uninterrupted.