How to refocus after an interruption: a short restart routine

A message arrives, a meeting starts or someone needs an answer. When you return, the file is still open—but the reasoning that made it obvious five minutes ago is not. Public discussions from students, office workers and software developers describe the same frustrating gap. Those discussions establish recognisable audience language, not prevalence, diagnosis or a universal solution.

Why unfinished work can follow you into the next task

In two experiments published in 2009, Sophie Leroy found that people switching away from unfinished work could retain thoughts about the first task while performing the next one—a pattern described as attention residue. The studies support a transition problem under their experimental conditions; they do not establish that every interruption has the same effect or that one routine works for everyone.

A later four-study paper by Leroy and Theresa Glomb examined interruptions under anticipated time pressure. Briefly planning how to resume the interrupted task reduced attention residue and protected performance on the interrupting task in those studies. This “ready-to-resume” finding supports leaving a specific return cue. It does not show that a music or frequency app improves work performance.

Another controlled study found participants completed interrupted tasks faster without a measured quality difference, but reported more stress, frustration, time pressure and effort. That is a useful caution against repeating the popular but unsupported claim that every interruption costs exactly 23 minutes.

1. Before switching: leave a ready-to-resume note

When the interruption gives you even 30 seconds, write enough for your future self to re-enter the work without reconstructing the entire context. Keep it operational, not inspirational.

1. Where I stopped: name the exact section, file, client or decision.
2. What is unresolved: write the question still open.
3. Next action: describe one visible verb—compare, draft, call, test or calculate.
4. Needed material: list the one document or source required next.
5. Return point: set a realistic time or event for coming back.

If the interruption is urgent, save the work and leave the shortest safe cue you can. The goal is not a perfect note; it is a reliable bridge back.

2. Capture the new demand so it stops competing for rehearsal

Put the message, question or follow-up into the system you actually review. That may be a calendar, task list, job record or written note. Do not leave it as five open tabs and a promise to remember.

Then close or silence the channel that delivered it when your role allows. If your work requires continuous availability, agree on escalation rules and focus windows with the people affected rather than pretending notifications can always be ignored.

3. On return: rebuild only the context you need

Read the restart note before scrolling through messages. Reopen the named file and the one supporting source. State the next action in plain language, then do the smallest part that changes the work: write one sentence, run one test, compare one number or mark one decision.

This is deliberately different from “get back into flow”. You cannot command a mental state, but you can create a clear first action and remove unnecessary switching.

4. Give the restart a bounded work block

Choose a period that fits the task and your real availability. It does not have to be 25 minutes. Five minutes may be enough to rebuild context; a longer block may suit complex analysis. Put the end point on a timer or calendar so the task has a boundary.

• Phone face-down or out of reach when safe and appropriate
• Only the required file and reference visible
• Status set to focus or unavailable when your workplace supports it
• A written parking place for unrelated thoughts
• One finish line for this block, not the entire project

5. Use optional listening as a cue, not proof of performance

Tihna's current Focus programme is presented as a 25-minute listening theme within a four-week structure, with eleven nature soundscapes or Pure Tone and progress tracking. If the installed app shows a suitable Focus session, starting it while you are stationary can mark the boundary between the interruption and the next work block.

The cited interruption studies did not test Tihna, binaural beats, soundscapes or a 25-minute session. Tihna does not monitor attention or guarantee better focus, speed, accuracy or productivity. If audio competes with reading, irritates you or masks something you need to hear, work without it.

Use stereo headphones as directed, keep volume comfortable and do not listen while driving, cycling, crossing traffic, operating machinery or supervising a hazard.

Make interruptions easier to recover from next time

After the block, improve the system rather than blaming yourself. Was the interruption genuinely urgent? Was the task missing a written next step? Did a notification need a different rule? Was the work block unrealistically long?

One useful measure is not “minutes perfectly focused”. Track whether you returned to the intended task, completed the written next action and needed fewer context-rebuilding steps over time. That is process feedback, not a clinical assessment or evidence that an app caused the result.

Evidence, problem signals and limits

• Leroy (2009), Why is it so hard to do my work? — two experiments on switching and unfinished tasks. Supports the attention-residue explanation under the study conditions; it did not test Tihna.
• Leroy and Glomb (2018), Tasks Interrupted — four studies supporting a brief ready-to-resume plan under anticipated time pressure. It does not establish a universal routine or audio benefit.
• Mark, Gudith and Klocke (2008), The Cost of Interrupted Work — controlled study reporting faster completion with no measured quality difference alongside greater stress, frustration, time pressure and effort. It does not support a fixed 23-minute recovery claim.
• Public discussion about coding interruptions — reviewed 8 October 2026 as audience language only. It is anecdotal and not prevalence, diagnosis or treatment evidence.
• Public discussion about writing the first return task — reviewed 8 October 2026 as a practical audience example only. It does not validate the intervention.

Disclosure: this article is published by Tihna. Tihna is a wellness app, not a medical device, attention monitor or treatment. The cited research did not test the complete Tihna app and does not guarantee an individual concentration, performance, safety or health outcome.