An interruption takes time to handle and can also make the original work harder to resume. Protecting a block of time helps, but a team also needs a practical way to manage the interruptions that genuinely cannot wait.
- 01Name the work that needs continuity
- 02Define an interruption route
- 03Leave a return note
- 04Review the source of interruptions
Name the work that needs continuity
Identify tasks where losing context is costly: writing an argument, debugging a system or making a complex design decision. Reserve time for those tasks with a clear outcome, not simply a calendar label that says “deep work”.
Sophie Leroy's research on attention residue examines how attention can remain with a prior task after switching. That is a useful reason to treat transitions as part of work design.
Define an interruption route
Agree what qualifies as urgent, how it should be raised and who can handle it. If every message arrives through the same channel with the same implied urgency, the recipient has to make that judgement repeatedly.
Keep a way to respond to real incidents. Focus practices that depend on being unreachable can move the burden onto colleagues.
Leave a return note
Before switching, record the current state and the next action. A few specific lines can be enough: the failing test, the paragraph's missing evidence or the decision still unresolved. Avoid writing a second project plan.
Review the source of interruptions
If the same question keeps returning, improve the reference, ownership or workflow behind it. The aim is not perfect isolation. It is a system in which necessary communication happens and difficult work still has a reasonable chance of reaching completion.