Block focused work in windows protected from interruptions
Create protected time blocks where interruptions cannot occur — eliminating the source of residue.
Why it works
Residue is generated by switching; eliminating interruptions during key work periods eliminates residue at the source. Protected windows allow a task to build and maintain the deep engagement state in which working memory is fully allocated to the current task. Research on flow and deep work convergently shows that high-quality output depends on sustained periods of uninterrupted focus rather than accumulated hours with frequent interruptions.
How to do it
- Designate your highest-cognitive-demand window (typically 2–4 hours in the morning) as a protected focus block.
- Turn off all notifications: email, Slack, phone, calendar alerts.
- Communicate the block to colleagues in advance so requests route to a defined response window.
- Within the block, work on a single task at a time — don’t "quickly check" anything.
Evidence
Deep work research (Newport) and flow research (Csikszentmihalyi) convergently support the value of protected, uninterrupted work periods. The connection to attention residue specifically: eliminating interruptions eliminates residue-generating switches. Mark, Gudith & Klocke (2008) measured the cost directly: interrupted work was completed faster but at the price of higher stress and effort, quantifying what protected windows are protecting against. (observational)
Protected blocks require organizational permission and are harder to maintain in open-plan offices, high-urgency roles, or cultures with always-on expectations. Implementation depends significantly on context.
Sources
- Mark, G., Gudith, D., & Klocke, U. (2008). The cost of interrupted work: More speed and stress. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '08), 107-110.
- González, V. M., & Mark, G. (2004). "Constant, constant, multi-tasking craziness": Managing multiple working spheres. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '04), 113-120.
Common mistake
Declaring a focus block but keeping notifications "silenced but visible" — the visual presence of incoming notifications generates partial attention switches even without full engagement.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Attention Residue: Why Switching Tasks Costs More Than You Think
- Reach a clear stopping point before switching tasks
Before switching to anything else, get to a natural completion point so the previous task has a cognitive bookmark.
- Batch small tasks to completion before starting large ones
Clear the small, quick tasks from your queue before starting a large focused task — not after.
- Close browser tabs, apps, and documents between tasks
Close everything related to the previous task before starting the next — visual remnants sustain residue.
- Design transitions between tasks, not just the tasks themselves
Build a brief transition ritual between tasks — a 5-minute buffer — so residue dissipates before the next task begins.
- Signal clearly when you’re done with a request before moving on
Close collaborative loops explicitly — send a brief "done" signal so the other person’s attention residue also closes.
- Track your task-switching frequency for one week
Count how often you switch contexts in a day — the number is almost always far higher than people estimate.
Related concepts
- The Zeigarnik Effect: How Unfinished Tasks Occupy Your Mind
Why unfinished tasks won’t leave you alone — and what to do about them
- Deep Work, Made Practical
Focus blocks, attention residue, and the shutdown ritual — with the evidence
- Indistractable, Made Practical
Internal triggers, timeboxing, and pacts — with the evidence behind each