Scale buffer time to cognitive distance

When This Fires

• When scheduling your day and planning transitions between different types of activities
• When you feel cognitively "stuck" in the mode of the previous activity for the first 10-15 minutes of the next one
• When emotional intensity from one interaction bleeds into subsequent work
• Complements Default to 25 or 50-minute meetings instead of 30 or 60… (25/50-minute defaults) with context-sensitive buffer sizing

Common Failure Mode

Uniform 5-minute buffers regardless of transition type. This works for same-type transitions but is grossly insufficient for mode-shifts or emotional recovery. After a difficult conversation, 5 minutes of buffer means you carry the emotional activation directly into your next task, degrading its quality.

The Protocol

(1) When planning your day, identify the transitions between activities. (2) Classify each transition: Same-type (two meetings, two coding sessions, two admin tasks) → 5-minute buffer. Different-type (meeting to coding, writing to admin, deep work to collaboration) → 10-15 minute buffer. Post-intense (after conflict, difficult feedback, high-stakes presentation, emotional conversation) → 20-minute buffer. (3) Build these buffers into the schedule explicitly — they're not empty time, they're transition infrastructure. (4) During buffers: close the previous context (write down where you left off, capture action items), physically move or stretch, and mentally prepare for the next context. (5) If you consistently need longer buffers than prescribed, that's data: either the transitions are harder than classified, or the previous activities are more draining than expected.