🧭 what this is

the loop where an interruption breaks my focus, the task-thread drops, and returning to the original thing suddenly feels much harder than it should.

the interruption may be small, but the re-entry cost can be huge. one question, one message, one sudden demand, and the task is now standing across a ravine holding a tiny clipboard.

🔁 loop pattern

  1. i am working or almost working
  2. something interrupts me
  3. i lose the thread of what i was doing
  4. returning feels unclear, annoying, or impossible
  5. i drift into avoidance, scrolling, another task, or emotional fog
  6. the original task becomes heavier
  7. restarting requires extra effort

🔍 what it feels like

  • irritation
  • mental static
  • “where was i?”
  • sudden tiredness
  • resentment toward the interruption
  • task feels unfamiliar again
  • urge to check messages or scroll
  • urge to switch to something easier
  • difficulty remembering the next step

🧩 common triggers

  • phone calls
  • people asking questions
  • urgent emails
  • unexpected messages
  • needing to leave the desk
  • switching tabs or apps
  • someone needing a quick thing
  • being pulled into a different decision
  • stopping before i have a clear checkpoint

🪤 the trap

the loop says:

“you lost the thread, so the task is gone now.”

but the task is not gone.

it just needs a re-entry point.

without one, my brain treats returning like trying to reload a crashed video game with no save file and ominous menu music.

🧷 interruption anchor

before switching away, leave a breadcrumb:

  • save the file
  • leave the tab open
  • write the next step
  • say the filename or task out loud
  • add a quick note: “return here”
  • mark the exact place i stopped
  • write one ugly sentence or placeholder

🛑 interrupt question

what was i doing, where was i, and what is the smallest visible next step back in?

🪜 return ladder

  1. pause

    • do not immediately flee into another task
  2. locate

    • what file, page, email, or tab was i in?
  3. name

    • what was the task?
  4. recover

    • what was the last visible step?
  5. restart small

    • do one tiny action, not the whole task
  6. protect

    • avoid switching again until momentum comes back

🧰 what helps

  • leaving notes before stepping away
  • keeping the active file open
  • using short restart phrases
  • returning to the last visible action
  • reducing tabs after interruption
  • writing a “next step” before answering someone
  • doing a 2-minute re-entry instead of restarting the whole task
  • treating momentum as fragile but rebuildable

💬 useful scripts

when interrupted

one second, let me leave myself a note so i don’t lose my place.

when returning

i do not need to feel ready. i only need to find the thread.

when the task feels gone

the task is still here. i just need the last visible step.

when i want to switch tasks

switching will feel easier, but returning now will cost less than returning later.

🧠 reminder

interruption does not mean the task is gone.

it means i need a re-entry point.

momentum can be rebuilt, but it needs a handle.