How to make a task easier to resume after interruption

What makes returning expensive

The task itself is often small. The return is what costs. When you come back to something after an interruption, you have to remember where you stopped, what was waiting on someone else, what the next move was, and whether anything went wrong while you were away. If you cannot answer those quickly, opening the work feels like opening a problem.

ADHD is a neurodevelopmental condition with functional impairment. Whatever lies behind it for you, the design answer is the same: do not make the returning person rebuild the picture from memory. Write it down while it is fresh.

The state note

You write the state note's three lines right as you stop.

Current

Draft done through section two, waiting on the finance figures.

Next

Open the figures email and paste the totals into table 3.

Check

Thursday after the team meeting.

Each line has one job, and the Current, Next, Check guide explains all three. In short: what is true now, one visible action, and when you will look again.

Weak note, strong note

A weak note scolds you and offers no action:

Finish this tomorrow. Do not procrastinate.

The strong version saves you the rebuilding:

Current: the draft states the problem and the recommendation. Next: check the second figure against the source file. Check: 9:00 tomorrow, before opening email.

When you find yourself writing a paragraph, your Next line still needs sharpening. Name the exact file, question, object or person.

Put it where you will look first

The restart marker is the spot where the note sits in plain view: the first line of a document, a sticky note stuck to a tray, your phone's lock screen. Name it once and use the same place every time.

Writing it in a notebook you will never open again does not help. Part of you knows that notebook is where things go to die, so your mind keeps carrying the context just in case. The note has to be seen again and say enough to act on.

When you are already interrupted

Sometimes you did not get to write a note. Use a Restart version. Locate the most recent version of the work you can trust. Put a state note at the top of it. Skip going back over everything that came before, unless the next action depends on it.

Return to your single Now item before choosing again. With one Now item, there is somewhere to land each time you get pulled away, so you are not choosing all over again.

Measure restart latency

Restart latency is the figure to keep an eye on. It runs from the moment you realize the work has slipped away to the moment you can trust where things stand: you know what matters today, what to do next and what is fine to leave. No formal tracking is needed, a rough guess will do. A project that takes two days to get back into is asking for better state notes.

Priya, in the book, has a restart latency of two weeks, almost all of it dread, even though the work itself took ten minutes once she began.

Test it with a controlled interruption

On a day when nothing urgent depends on it, close one project cold and return the next morning using only the state note. Then answer four questions. Could you identify the current truth? Was the return path obvious? What information was missing? What would you add to the note next time? Run this once, not as a daily ritual.

Failure modes

• The note becomes a diary. Keep it to three lines.
• The restart turns into a rebuild. Leave your tools alone while you are still disoriented. Get the current state back first.
• One skipped note is taken as proof the method fails. Interruptions were never going to stop. What counts is whether the system made coming back easier.