When an interruption breaks your focus, you don't need a fresh hour to recover. You need a 15-minute reload routine that hands the cold-start work to AI, so you're rebuilding context instead of staring at your screen. Stop treating "getting back to work" as a single willpower moment. Treat it as a short sequence you run the same way every time.
I built this because my afternoons kept dying the same death. A Slack ping, a quick question from someone at the door, a phone buzz, and then twenty minutes of scrolling before I even remembered what I was doing. The gap wasn't the interruption. It was the recovery.
Why interruptions cost more than the minutes they take
An interruption doesn't just steal the 90 seconds you spent answering it. It wipes your working memory. Before the ping, you were holding the shape of the problem in your head. The half-written paragraph, the three edge cases, the reason you opened that file. After, that structure is gone, and rebuilding it is slow and unpleasant. So we avoid it. We check email instead. That's the real cost.
The fix is to make the rebuild fast and mechanical, so the path of least resistance leads back into the work instead of away from it.
The 15-minute focus recovery playbook
Here's the full sequence. It fits in the time you'd otherwise waste recovering, and it ends with you actually typing again.
Minutes 0–2: Capture the interruption, don't act on it
Whatever pulled you away, write it down in one line and close it. Not "deal with it" — just park it. "Reply to Dana re: invoice" goes on a list. You want the intrusive thought out of your head so it stops competing for attention. If you act on it now, you've chosen a second task over your first one.
Minutes 2–7: Have AI reload your context
This is where AI earns its place. Instead of re-reading your whole document to remember where you were, paste in what you had and ask the AI to summarize the current state of the work and name the very next concrete action. A good context-reload prompt does three things:
- Restates what the work is trying to accomplish, in one sentence.
- Summarizes where you left off — what's done, what's unfinished.
- Names one small, specific next step you can start immediately.
That last part matters most. "Keep writing the intro" is vague and stalls you. "Write the second sentence of the intro, which should give one example" is a starting line. AI is good at turning a fuzzy state into a crisp next move, which is exactly the thing your interrupted brain struggles to do on its own.
Minutes 7–12: Rebuild the mental model out loud
Read the AI's summary, then correct it. Tell it what it got wrong or missed. This back-and-forth isn't busywork. The act of correcting the summary is how you reload the model into your own head. You're not outsourcing your thinking. You're using the AI as a sparring partner to reconstruct it faster.
Minutes 12–15: Start before you feel ready
Do the small next step the AI named. Type the sentence. Open the file. Write the first line of code. Starting is the whole game. Momentum comes back within a minute or two of doing real work, but never during the deliberation about whether to start.
Why the prompts have to be pre-written
Here's the part people miss. If you have to compose a good reload prompt in the moment, you've already lost. A scattered, interrupted brain is the worst possible state for writing careful instructions. You'll write something lazy, get a generic answer, and give up.
So the prompts need to already exist, tuned for this job, ready to paste. That's the difference between a routine you actually run and a nice idea you abandon by Wednesday. If you'd rather not spend a weekend building and testing your own set, the Focus Defender Deep Work Prompt Pack is the Notion template I built for exactly this. A ready-to-run set of deep work prompts, including context-reload ones, so your 15-minute recovery is copy, paste, go.
Making it a default, not a decision
Run the same sequence every time and it stops being a choice. The interruption happens, you reach for the same list and the same prompts, and recovery becomes reflex. That consistency is what protects your afternoons over a full week. Not heroic focus, just a reliable way back in.
Keep the capture list visible and the prompts one click away. Friction is the enemy. Every extra step between "interrupted" and "reloading" is a step where you drift toward email instead.
FAQ
What if the interruption was urgent and I have to handle it?
Then handle it, but still run the reload afterward. The 15-minute sequence works whether the gap was two minutes or two hours. The longer the gap, the more you need the AI to rebuild your context, because your memory of the task has faded more.
Won't asking AI to summarize my work take longer than just re-reading it?
For a short task, sometimes. For anything with moving parts — a document, a plan, a piece of analysis — the AI reload is faster because it hands you a named next action instead of leaving you to find one. The bottleneck isn't reading. It's deciding where to restart.
Can I use this for creative work, or just admin?
Both, but the prompt changes. For creative work you want the AI to remind you of your intent and constraints, not generate the content for you. The reload is about restoring your own thread, not replacing it.
Do I need a separate prompt for different kinds of tasks?
A little tailoring helps. A writing reload and a coding reload ask for slightly different things. That's why a small tuned set beats a single all-purpose prompt. You grab the right one for the work in front of you and skip the fiddling.