“It’s Only 30 Seconds” — Why a Quick Interruption Can Cost Much More

Jonas has been absorbed in a complex problem for some time when Olek appears with a quick question.

— Got thirty seconds? Where’s the latest template?
— In the client folder, under “Final.”

Olek walks away satisfied. Jonas looks back at the screen and tries to find the exact point where his thinking broke off.

For Olek, the conversation cost half a minute. For Jonas, the cost has only just begun.

What really happened

Olek sees a simple calculation: thirty seconds of Jonas’s time saves him ten minutes of searching, so asking is obviously efficient. Jonas is paying a different cost. He is working through a complex problem, holding several dependencies in working memory, and a short answer does not return him automatically to the exact mental state he had before the interruption. He has to reconstruct the thread. Both men can therefore talk honestly about “how long the question took” while measuring different intervals. For Olek, the interruption begins with “Got a second?” and ends with the answer. For Jonas, it ends only when he has rebuilt the context and regained his previous level of focus.

What the research says

Research on task interruption shows that after being interrupted, people need time to recover the goal, context, and position in the activity they were performing. That recovery period is often described as a resumption lag. Classic work by Trafton and colleagues showed that even a brief opportunity to prepare for an interruption can make later resumption easier, while a systematic review and meta-analysis of 33 experiments found that interruptions impair task performance and that the way interruptions are managed can reduce some of that cost (Trafton et al., 2003; Chen et al., 2022). Part of attention may also remain attached to the previous task or the interruption itself — attention residue (Leroy & Schmidt, 2016). The practical point is simple: the length of the conversation does not tell you the full cost to the person whose work was interrupted.

How to handle it

There is no need to ban quick questions. The useful distinction is between questions that genuinely block progress and questions that can wait. Teams can batch small questions, protect agreed focus periods, and keep a separate channel for genuinely urgent issues. If you do need to interrupt someone doing cognitively demanding work, give them a few seconds to mark where they are before switching their attention. The general rule is: before interrupting, do not ask only “How long will my question take?”; also ask “How long might it take the other person to recover what they are doing?”

How Empatyzer and Em can help

Empatyzer can help Olek and Jonas see that “thirty seconds” is not the same cost for both of them. Olek is measuring the duration of the question; Jonas may place greater value on uninterrupted thought, structure, and the ability to complete a mental sequence without switching. Em can help them agree on a simple protocol: what counts as urgent, what should go into an asynchronous message, and what can be collected into one short question block. Olek still gets the help he needs quickly, but not automatically at the expense of someone else’s concentration. The team can adopt the same rules without labeling anyone as “unavailable” or “chaotic.” Micro-lessons reinforce the habit of evaluating communication not only by the length of the interruption, but by the cost of returning to the task afterward.