Handling external interruptions
Use the inform–negotiate–schedule–call-back protocol to protect the sprint.
Key takeaways
- What it is: Use the inform–negotiate–schedule–call-back protocol to protect the sprint.
- Why it works: External interruptions feel non-negotiable in the moment, but most can be deferred by minutes. A scripted response — acknowledge, propose a later time, agree, follow up — converts an immediate demand into a scheduled one, preserving the sprint while still honoring the request.
- Evidence: Plausible mechanism, limited direct outcome data.
- Avoid: Saying "give me a minute" and then immediately context-switching anyway. The protocol only works if you actually defer the task, not just delay the conversation.
Why it works
External interruptions feel non-negotiable in the moment, but most can be deferred by minutes. A scripted response — acknowledge, propose a later time, agree, follow up — converts an immediate demand into a scheduled one, preserving the sprint while still honoring the request.
How to do it
- 1When interrupted, inform the person you’re mid-task.
- 2Negotiate a specific time to address their need.
- 3Schedule it, then return to the sprint.
- 4Call back at the agreed time so people learn the boundary holds.
What the evidence says
MechanisticThis is a practitioner protocol from Cirillo. It is supported indirectly by interruption research showing that resuming an interrupted task is costly and error-prone, so deferring interruptions protects performance.
Honest caveat: The four-step script itself is unstudied; the underlying cost-of-interruption finding is what is established.
Common mistake
Saying "give me a minute" and then immediately context-switching anyway. The protocol only works if you actually defer the task, not just delay the conversation.
IX Coach helps you set realistic focus windows and pre-draft the boundary language so deferring an interruption feels routine rather than rude.
Practice this with IX Coach →