Use a 3-step context switch: close (30s), gap (60s), load (60s) — 2.5 minutes prevents 15 of residue
When switching between cognitive contexts, implement a three-step loading protocol: (1) close the current context by writing a one-sentence summary and noting open loops (30 seconds), (2) create a transition gap of deliberate non-engagement (60 seconds), (3) load the new context by reviewing relevant notes and orienting before producing (60 seconds).
Why This Is a Rule
Leroy's attention residue research shows that 15-25 minutes of cognitive capacity are lost after an abrupt context switch — your brain is still processing the previous context while you're trying to engage with the new one. The three-step protocol invests 2.5 minutes of structured transition to prevent 15+ minutes of degraded performance.
Step 1 — Close (30 seconds): Write a one-sentence summary of where you are and note any open loops. This closes the Zeigarnik loop (Write a one-minute ready-to-resume note before every task switch) and gives your brain permission to release the previous context. Without explicit closure, the open loops persist in working memory, consuming the capacity the new context needs.
Step 2 — Gap (60 seconds): Deliberate non-engagement — look away from screens, take a breath, stand up. This creates a cognitive buffer between contexts, preventing the previous context's activation from bleeding directly into the next. Think of it as the palate cleanser between courses.
Step 3 — Load (60 seconds): Review relevant notes, reread the ready-to-resume note, orient yourself to the new context before producing anything. Loading context deliberately is faster and cleaner than reconstructing it through trial and error.
When This Fires
- Switching from one project to another
- Transitioning from a meeting to deep work (or vice versa)
- Any cognitive context shift where the previous and next tasks are substantially different
- Complements Insert 5-minute transition buffers between all calendar blocks (transition buffers) with a specific protocol for the buffer time
Common Failure Mode
Jumping straight from one context to another: closing the meeting and immediately opening the code editor. The first 15 minutes of "coding" are actually attention-residue processing from the meeting. The 2.5-minute protocol eliminates this waste.
The Protocol
At every context switch: (1) Close (30 seconds): write one sentence summarizing where you stopped and any open loops. (2) Gap (60 seconds): stand up, look away from screens, take three breaths. Non-engagement. (3) Load (60 seconds): review your notes for the new context, reread the ready-to-resume note if available, orient to the task before producing. Total: 2.5 minutes invested, 15+ minutes of residue prevented.