You are in the middle of a report. A chat message asks for something. You have two choices. Stop working and handle the request. Or ignore it and risk forgetting.
Neither option works well. Handling the request breaks your focus. Ignoring it leaves you wondering if you missed something important.
The gap between these choices is where productivity dies. You lose focus on the report. You lose track of the request. Both suffer.
The cost of switching tasks
When you switch from one task to another, it takes time to refocus on the original work. Research from Gloria Mark at UC Irvine shows the average is 23 minutes. Not the time spent on the interruption. The time to get back to the same level of focus.
The cost is not just the 23 minutes. Part of your attention stays on the first task while you work on the second. Sophie Leroy at the University of Minnesota calls this attention residue. Your performance on the new task is degraded because you are not fully there.
You lose focus on both tasks. The switch cost compounds throughout the day. Three interruptions mean you spend over an hour refocusing instead of working.
What actually works
Protect your focus by capturing the interruption without switching tasks. Here is the approach.
Record the request in seconds. Pull out your phone or open a note. Write down what was asked. “Lisa needs the budget numbers for the board deck by Friday.” You are back to your report in two seconds. The request is captured. You will not forget it.
Recording the request is not the same as switching tasks. You are not engaging with the new work. You are parking it. The 23-minute refocus cost does not apply because you never actually left your original task.
Process the captured requests in batches. Set two reminders during the day. One at lunch. One at the end of the workday. When the reminder fires, review what you captured. Handle the requests in a focused block instead of scattering them throughout the day.
Batching turns interruptions into planned work. You handle the requests when you are ready, not when they arrive. The people who asked get their answers. Your focus stays intact.
Communicate the delay. If the request is urgent, the chat message will say so. If it is not, a quick reply sets expectations. “Captured. I will get to this after my report. Expect an update by 3 PM.” The requester knows you heard them. You know when to handle it.
This takes about two seconds per interruption plus 15 minutes for each batch. The trade-off is clear. You lose two seconds instead of 23 minutes per interruption.
The cost of unprotected focus
Unprotected focus creates a cycle of scattered work. You switch tasks. You lose focus. You switch again. By the end of the day, you worked on everything and finished nothing. The problem compounds when personal tasks compete with work tasks for the same mental bandwidth — every errand in your head is a piece of attention not on your work.
The cost shows up as missed deadlines and rushed work. You spent all day responding to requests. The report you were writing is still incomplete. The requests you handled were minor. The work that mattered did not move forward.
The insight
Staying focused is not about avoiding interruptions. It is about handling them without switching tasks. Capture the request in seconds. Process it in a batch. Communicate when you will respond.
Two seconds to record a request. Twenty-three minutes saved on refocusing. The math is clear. Protect the focus by capturing first and acting later.