Resumption Lag

A simple explanation

Resumption lag is the strange heaviness of sitting back down at a task you stopped twenty minutes ago. The chair is the same, the screen shows the same words, but the thread is no longer in your head. You re-read the last paragraph. You stare at the cursor. You ask yourself what you were about to write, and the answer is fuzzy until — somewhere between the third re-read and the fifth — the thread comes back.

The minutes between sitting down and actually working are not laziness. They are the brain re-loading the working memory the previous you had built, and the re-loading is real cognitive work even when no new output appears.

An everyday example

You were drafting a section at 10:15 when a meeting interrupted. You said I will be back in twenty minutes. The meeting ran forty. You return at 10:55. You sit. You re-read the last paragraph. You scroll up. You scroll down. You re-read the brief. You realise you had been about to make a specific argument, but the shape of it is missing now.

By 11:10 the thread is back and the next sentence appears. Fifteen minutes after sitting down, you are finally writing again. The fifteen minutes were not procrastination. They were the lag — the cost of resuming, paid in full before any new sentence can be deposited.

Why returning is harder than starting

Three reasons the second start of the same task is harder than the first.

First, the working memory is not where you left it. When you started fresh in the morning, the channel was clean. When you resume after an interruption, the channel is partly occupied by the interrupting task, and the brain has to clear that residue before re-loading the original.

Second, the goal-state has faded. The specific micro-goal you held at 10:15 — finish this argument by showing the counterexample — was not written down. It has decayed. You can reconstruct it, but reconstruction is slower than recall.

Third, the body is in a different state. The morning's energy was fresh; the post-meeting energy is metabolically different. The same task lands on a different cognitive substrate, and the substrate matters.

These costs are small individually. Stacked across a fragmented day, they account for a sizeable fraction of the work that did not get done.

The behavioral loop

The shape that produces a day full of resumption lag:

1. You begin a task — working memory builds, goal-state forms, momentum starts.
2. Interruption arrives — meeting, ping, person at the door.
3. You switch away — the original task's state freezes; the interrupting task takes over.
4. Interruption ends — you return to the original.
5. The re-loading begins — re-read, re-orient, search for the thread.
6. The lag plays out — five to fifteen minutes before new output begins.
7. The block ends before depth is reached — because the lag ate the front of it.
8. The next interruption arrives — and the loop runs again.
9. End of day — many blocks attempted, few completed, most of the cost spent on resumption.

The defining feature is that the cost is at the front of every block, not the back.

Emotional drivers

Three feelings, layered:

• A small flicker of avoidance when sitting back down — the body knows the re-loading is coming and momentarily resists.
• A faint self-judgment at the slow re-start — why am I not just getting on with it? — which the loop-runner often metabolises as a problem of discipline rather than a problem of structure.
• A reluctance to ever fully close a task at end of day, because closing it would mean paying the resumption lag again tomorrow.

What your nervous system does

The transition back into focused work requires the brain to re-engage the salience and attention networks that the interruption pulled apart. The re-engagement is metabolically expensive. The prefrontal cortex re-loads goal-state with effort; the default mode network has to deactivate again; the anterior cingulate registers the gap between current state and the state the original task required.

The body often arrives at the desk before the brain does. Five minutes of staring at the screen is, somatically, the brain catching up.

The DojoWell interpretation

Resumption lag is a clean instance of residue_accumulation — the density signature in which residue from the previous task and the interrupting task both occupy the channel the current task needs, costing minutes before any new deposit can begin.

The Meaning System is asking for a block long enough that, even after the lag, the substantive work has time to settle. The Threat System, scanning for new input, keeps issuing the interruptions that produce the lag in the first place. The system answers the Threat System (interruptions feel urgent) and underpays the Meaning System (the lag eats the depth-block from the front).

The substitute is re-loading context — the felt-work of getting back to where you were. Real effort runs. Deposit per cycle is small because the lag consumed the front of the block before any new work could begin.

The equation is sharp. Effort: real. Deposit: starts late, ends early, totals little. Residue: persists from the interruption. The numerator collapses. Density: low. The fix is not to resume faster — it is to interrupt less, or to leave a richer breadcrumb the next you can use to re-load.

What can I do to make re-entry easier?

Three moves, in order of leverage.

First, write a re-entry note before you leave. One or two sentences: where I am leaving this; what comes next; the specific question I was about to answer. The note is the breadcrumb the future you uses to skip most of the lag.

Second, leave the work in a state the next you can resume. Mid-paragraph rather than mid-sentence; mid-section rather than between sections. The brain re-enters mid-paragraph faster than it re-enters at a chapter break.

Third, batch interruptions rather than scattering them. Three interruptions in a row cost roughly one lag; three interruptions spread across the day cost three lags. The math is brutal in the second case.

Practical steps

1. Write a one-line resumption note every time you leave a task. Where you are, what next. Twenty seconds of writing saves five minutes of re-loading.
2. Leave tasks mid-action, not at clean stops. A half-written sentence is a faster re-entry point than a finished section.
3. Stack interruptions into one window. One meeting block, one triage block, one writing block — rather than rotation. Each rotation is a fresh lag.
4. Block-protect the first 30 minutes of any depth task. If you cannot give it 30 unbroken minutes, do not start; the lag will exceed the available block.
5. Notice the resumption resistance. When sitting back down feels heavy, name it as lag, not as laziness. The naming changes what you do next.

Reflection questions

• How many minutes pass between sitting back down and producing new work — on a typical interrupted task?
• What would change if every task you left included a one-line breadcrumb?
• Which interruption issues the longest resumption lag for you — and what would it cost to defer it by an hour?
• When did you last finish a session at a clean stopping point, knowing tomorrow's re-start would be slow?

Frequently Asked Questions