One 15-minute overflow buffer per 2-3 hours of scheduled activity — absorbs overruns and prevents cascading disruption

Why This Is a Rule

Schedules that allocate 100% of available time to activities are brittle: any single overrun — a meeting that goes 10 minutes long, an unexpected phone call, a task that takes longer than estimated — cascades through the rest of the day, making every subsequent activity late. By 3pm, you're 45 minutes behind "schedule," stressed from the accumulating deficit, and making worse decisions because of time pressure.

The solution is scheduled slack: unallocated buffer time that absorbs overruns without cascading. This is the same principle behind engineering safety margins (bridges are built to handle 3x expected load) and operational buffer stock (warehouses maintain inventory above expected demand). The margin exists not because you expect to use it every time, but because variation is guaranteed and the cost of no margin is system failure.

The 15-minutes-per-2-3-hours ratio (roughly 10% slack) is calibrated to typical daily variation. Most tasks have ~10-15% variance in execution time, and most days include 1-2 unplanned small interruptions. A 15-minute buffer every 2-3 hours absorbs these without accumulation. On the rare day when everything goes perfectly, the buffer becomes bonus time for whatever you want. On the typical day, it prevents the cascade.

When This Fires

• When planning your daily time blocks and wanting to build in resilience
• When your days consistently run behind schedule despite reasonable time estimates
• When a single overrun in the morning ruins the entire afternoon's plan
• Complements Default to 25 or 50-minute meetings instead of 30 or 60 — automatically create transition buffers without individual negotiation (25/50-minute meetings) and Scale buffer time to cognitive distance: 5 min between similar tasks, 10-15 min between different types, 20 min after intense interactions (transition buffers) with the macro-level overflow capacity

Common Failure Mode

Over-scheduling: filling every minute of the day with productive activities under the assumption that everything will take exactly as long as planned. This maximizes theoretical output but minimizes actual output because the first disruption collapses the entire structure. The "productive" schedule produces less real output than a looser schedule with slack.

The Protocol

(1) When planning your day, insert a 15-minute unallocated buffer after every 2-3 hours of scheduled activity. Label it "Buffer" or "Overflow" — not with a specific task. (2) During the day, when activities run over, let the overrun absorb into the next buffer rather than compressing subsequent activities. (3) If the buffer isn't needed (activities ran on time), use it for whatever feels right: a quick walk, processing captured tasks, or starting the next activity early. Do not pre-commit the buffer to a specific task — its value is in being unallocated. (4) If you consistently need more than 15 minutes of overflow per 2-3 hours, your time estimates are systematically too short — adjust the estimates, not just the buffer. (5) Track buffer utilization: how often do you use the full buffer vs. have it free? If free most days → you might be over-buffering. If used every day → you might need more.