How do I get back to work after an interruption?
The interruption is usually blamed for the lost block. Often the real damage happens one minute later, when the interruption is over and nothing tells you where to re-enter.
A message arrives. Someone asks a quick question. A delivery comes. You leave the document for two minutes.
Then the interruption ends. This should be the easy part. Instead, you check one other thing, reopen the wrong tab, answer another message or stare at the task without knowing where the thread went.
The interruption took two minutes. The return takes twenty.
The interruption is not the whole loop
Focused work contains more state than the screen shows. You know which sentence is wrong, which number still needs checking, which decision you were leaning toward and which next move was already forming.
When you leave without marking that state, the files remain open but the working position disappears. On return, you are not continuing. You are reconstructing.
Where it turns
The critical moment often happens before you leave. The interruption feels small, so you do not prepare the return.
You answer the question immediately. You stand up immediately. You switch windows immediately. The old task is left with no visible next step because you assume you will remember it.
You usually remember the topic. You do not reliably remember the exact point of re-entry.
The task stays open, but its live state is gone.
Why common fixes arrive too late
Trying harder to ignore interruptions can help, but some interruptions are real. The door still rings. The child still asks. The urgent call still comes.
A longer focus timer does not repair an undefined return. Neither does reopening every window and hoping recognition comes back.
The useful move is smaller: preserve the current position before contact breaks.
The move to test
Before switching away, leave one brutally short re-entry line where the work already is.
Not a summary. Not a new task list. One instruction to your returning self: “Check row 18 against invoice.” “Rewrite the second sentence.” “Decide between A and C.”
The line should remove the first decision after you return.
MARK THE RETURN BEFORE YOU LEAVE.
- 1Pause for five seconds when an interruption enters.
- 2Write the exact next physical or visible action.
- 3Leave the marker inside the active document, tab or workspace.
- 4When the interruption ends, perform that action before opening anything else.
This does not prevent interruptions. It tests whether the original task can keep a visible return path.
What to observe
You return and rebuild the task from memory.
You drift briefly, then notice and use the marker.
The first action after the interruption is the marked re-entry move.
The interruption changed the task itself or made the previous next step obsolete.
A task is easier to resume when the return was designed before the exit.
Serkan Elbasan
Serkan Elbasan is the founder of the Institut für Kognetik and an independent researcher working on recurrence, structural invariance, rule–state separation and the formal conditions under which systems can modify their own rules.