Say you’re checking a report when an urgent request comes in. You turn to the request, but your mind keeps going back to the conclusion you haven’t written. Later, back at the report, you can’t remember which figures you already checked.
Those are two different problems. The first is called attention residue: thoughts about the last task keep coming back while you work on the next one. The second is losing your place: you come back and aren’t sure where to carry on. A good routine helps with both.
You can’t always finish before someone needs you. What you need is a way to leave unfinished work with a clear next step, while still answering when you must and taking breaks that help.
This module is for working adults doing demanding work, or tasks whose steps have to happen in order. Use the checking routine only when the checks can wait and your duties to answer people allow it.
What you’ll get from this module
In this module
By the end of this module, you’ll know how to leave a task and find your place when you come back. We’ll draw on a planning experiment at a workplace, observations of interrupted work, lab tasks, two email studies and a review of breaks for problem solving. You’ll pick a situation from your daily life and write a plan for switching tasks, including what to do when a check can’t wait.
Ask Jing
Become a Jingius.
What changes when you leave one task for another?
Workplace experiment: leaving a plan for unfinished work.
Ward van Zoonen and Yuri S. Scharp’s 2025 study tested return plans at a Dutch technology consultancy. When an unexpected interruption came from outside their task, people in the study paused before turning to it. They wrote down where they had stopped, where they would pick up and what problems were still open. The comparison group got no such instruction.
The researchers put 58 people into the two groups at random. Of those, 50 reported on four workdays. The planning group reported less attention residue. They were less caught up in thoughts about the interrupted task while they worked on the new one.
Notice where the plan helped. It was about going back to the old task. But the benefit people reported was being less distracted by that task while they did the new one.
Why it matters: This was a small study in one company, and it relied on what people said about their own experience. Different ways of analysing the data gave different answers about exhaustion. So the finding about lingering thoughts does not show that people felt less worn out overall.
Read the workplace study of return plans.
Workplace observations: time away includes other work.
Gloria Mark, Victor M. González and Justin Harris followed 24 office workers for their 2005 study. They watched people at a company that offered IT and accounting services, including what happened between leaving a piece of work and coming back to it.
When people came back to interrupted work on the same day, it took 25 minutes 26 seconds on average. In that time, they worked on other things. The figure measured how long it was until people came back, not how long it took them to get their focus back.
So a long gap can include useful work on something else. Calling all of it lost focus would change what the researchers measured.
Why it matters: The average they saw is not a recovery timer you have to wait out.
Read the observational study of fragmented work.
Laboratory experiments: knowing the steps and keeping your place.
Erik M. Altmann, J. Gregory Trafton and David Z. Hambrick’s 2014 experiments asked university students to work through a repeating series of simple decisions. Now and then they were interrupted and had to type short strings of letters before going back to the series.
Short interruptions led to more mistakes about which step came next. The researchers found no clear rise in mistakes within the steps themselves. Knowing how to do a step and remembering which step comes next were two different jobs for the mind.
The experiments counted mistakes in a lab task. They did not measure every kind of mistake people make at work.
Why it matters: This is a different problem from thoughts about unfinished work getting in the way of the next task. It is about picking the right step when you come back.
Read the experiments on interruptions and sequence errors.
Everyday-life experiment: checking email less often.
Kostadin Kushlev and Elizabeth W. Dunn’s 2015 study compared two ways of handling email over two weeks. It included 124 people, mostly students, who could choose when to check their email. Each person tried both ways, one week each, in an order picked at random.
In one week, people checked less often, kept their inbox closed and turned off alerts. In the other, they checked often, kept the inbox open and left alerts on. People reported less stress day to day in the week they checked less. When they looked back on each whole week, there was no clear difference in stress.
Why it matters: The study changed three things at once: how often people checked, whether the inbox stayed open, and alerts. So it can’t tell us how much of the drop in daily stress came from checking less on its own.
Read the experiment on email checking and stress.
Workplace comparison: batching has to fit the job.
Indy Wijngaards, Florie R. Pronk and Martijn J. Burger studied a month-long email-batching challenge at a Dutch financial-services company in their 2022 study. Batching means checking email at set times instead of all through the day. Teams were put in the challenge group or the comparison group by where they worked, not at random.
The researchers compared how exhaustion changed in the two groups. Right after the challenge, the result leaned toward less exhaustion with batching. But the difference was not big enough to count as a clear finding by the usual statistical standard. At the later follow-up, this comparison also found no clear benefit.
Why it matters: People who expected to answer email quickly were among those more likely to drop out before the survey at the end of the challenge. That matters. The people who stayed in the study may not be like workers who have to reply fast.
Read the workplace study of email batching.
Research review: some time away can help a stuck problem.
Ut Na Sio and Thomas C. Ormerod’s 2009 review pulled together experiments on incubation: putting a problem aside for a while before trying to solve it again. Across the studies, time away helped people solve problems, though how much depended on the kind of problem.
For creative problems, studies where people did hard mental work during the break found smaller benefits than studies where people rested. What people did in the break mattered, not just whether they took one.
Why it matters: The finding is about problem solving under the conditions these studies tested. It does not mean checking messages is a reliably refreshing break, or that every interruption helps.
Read the review of incubation and problem solving.
What this means for you
Start with the problem you’re trying to solve. If thoughts about unfinished work keep coming back, a note can give that work a clear next step. If you lose your place when you come back, check what is really finished before you carry on. Your duties to answer people decide which checks can wait.
Choose a work segment and decide what can wait
Pick a part of the work worth finishing, such as checking the figures in a report. Decide what finished looks like: the figures checked, even if the conclusion isn’t written yet. Now you have a point where you can stop for routine checks, while urgent requests can still get through.
Sort the checks that can wait from the requests that need a quick answer. Where your duties allow it, gather the checks that can wait into realistic time slots around that part of the work. Agree on what counts as urgent with the people who rely on your answers.
If you don’t know how fast you’re expected to answer, find out before you hold messages back. If quick answers are part of the job, keep giving them, and use a return note for the switches you can’t avoid.
Choose your timing around the work and what you owe people. The time it took people in the study to come back to their work is not a timer you need to wait out.
Leave a specific next action before switching
Before a switch you can’t avoid, jot down where the work stands, what to do next and what is still unsolved. Write enough to understand the next action when you come back. The note should help with the work, not become another writing job.
In the made-up report example, “finish report” leaves the important choice open. A more useful note could say: “Figures checked. Next, draft the conclusion. Confirm the source for the final claim.”
The second note separates what’s done from what’s still needed. It also keeps the question about the source in view: writing the conclusion won’t, on its own, make the report ready.
You’re not trying to force yourself to finish everything before you answer someone. You’re leaving unfinished work in a state you can come back to. If keeping the note up becomes a chore, cut it down to the detail you really need.
Check your place when you return
Read the note, check where the task really stands and find the last step you finished before you carry on. A note can go out of date. What matters is whether its next action still fits the work in front of you.
In the report example, check that the figures really are all checked and the source question is still open. If something changed while you were away, update the next action before you follow the note.
This is the lesson of the lab experiments in everyday terms. Knowing how to check a figure doesn’t tell you which figures are already checked. Confirm your place before you do the next step.
Keep useful breaks available
When you’re stuck on a creative problem, think about stepping away to do something less demanding. The review supports keeping this option open. How much it helps still depends on the problem and on what you do in the break.
A break and a request you can’t avoid are for different things. Don’t fill every pause with another demanding task out of habit. Decide whether the moment calls for answering, carrying on with a useful part of the work or stepping away before you try again.
Assess the cost of the routine too
Over a few similar stretches of work, notice what happens. Do you finish the part you meant to, lose your place, keep up with the answers you owe, or spend too much effort on the routine? Look at those answers together.
If holding checks back gets in the way of an answer you have to give, change the time slots or stop batching those requests. If the notes take more effort than they’re worth, make them shorter or drop the part that’s a chore.
Keep a part of the routine when it helps with the work without making your answers too slow or taking too much effort. Feeling more organised is only useful if the routine also fits what you need to do.
How about your daily life?
Where do you leave something unfinished and keep thinking about it during another task? Where do you come back and wonder which step you finished?
You might choose checking a report, working through a spreadsheet or writing something that gets interrupted by requests you have to answer. A stuck creative problem could be a different situation to explore.
List the situations you’d like to handle with more care. One good idea is enough.
| A situation in my daily life | What I would like to handle better |
|---|---|
| ____________________ | ____________________ |
| ____________________ | ____________________ |
My chosen situation: ____________________
Take your chosen situation into the exercise below. You can change your mind. Choosing a situation doesn’t mean its messages can wait.
Plan your next switch
Start with your chosen situation. If you came straight here, choose demanding work or a task whose steps have to happen in order. Hold back only the checks that aren’t urgent, and only where your duties to answer people allow it. Interruptions you can’t avoid can still use the return-note steps below.
- Name a meaningful work segment. Write down the part you mean to finish and how you’ll know it’s finished.
Segment and completion point: ____________________ - Separate what can wait from what needs a prompt response. Agree on what counts as urgent and choose realistic time slots for the checks that can wait. If you’re not sure how fast you’re expected to answer, find out before you hold messages back.
If the checks can’t wait, keep giving the answers you owe. Plan for the switches you can’t avoid instead of forcing a checking slot that clashes with your duties.
Checks that can wait, checking windows and urgent exceptions: ____________________
Response expectation I need to clarify, if any: ____________________ - Prepare a return note before an unavoidable switch. Write only the detail you need: where things stand, the next action and the problem still open.
Current state: ____________________
Next action: ____________________
Unresolved obstacle: ____________________ - Confirm your place on return. Read the note, check where the task really stands and find the last action you finished. Update the next action if the note no longer fits the work.
Confirmed state and next step: ____________________ - Review usefulness and burden across comparable periods. Over a few similar stretches of work, note whether you finished what you meant to, how often you lost your place, the answers you had to give and the effort the routine took. Change or drop the parts that cost more than they give.
If you’re stuck on a creative problem, keep the option of a less demanding break before you try again.
What helped, what interfered and what I will change: ____________________
Ask Jing
Become a Jingius.
Your next step
You’ve finished the plan when you have a workable way to handle the switch, or a clear question about how fast you need to answer that you’ll settle first. After you’ve tried it, use what you noticed to decide what to keep, change or drop.
A note on the evidence
These studies measure different things: lingering thoughts, mistakes about which step comes next, stress, exhaustion, time until people came back, and problem solving. They don’t add up to one measure of focus or productivity.
The return-plan study at work was small and short. The email findings changed with the study and with what was measured. Use the routine in light of your duties, and weigh the effort it takes against any changes that help.
How we prepared this module
This module brings together research on switching tasks, email routines and breaks for problem solving. A made-up report example shows how to tell apart finished work, a next action and an open question. The exercise helps you plan one switch and check whether it was worth it.
Sources
- Ward van Zoonen and Yuri S. Scharp. (2025). Managing daily work intrusions: An intervention to reduce attention residue and exhaustion. International Journal of Stress Management, 32(4), 395–407. Accepted author manuscript; pp. 12–16, Method and measures; pp. 18–19 and Table 3, p. 40.
- Gloria Mark, Victor M. González, and Justin Harris. (2–7 April 2005). No Task Left Behind? Examining the Nature of Fragmented Work. Proceedings of CHI 2005, ACM, 321–330. Published paper; pp. 323–324, methods; p. 326, Resumption of interrupted work.
- Erik M. Altmann, J. Gregory Trafton, and David Z. Hambrick. (2014). Momentary Interruptions Can Derail the Train of Thought. Journal of Experimental Psychology: General, 143(1), 215–226. Published article; p. 218, Method; p. 225, General Discussion.
- Kostadin Kushlev and Elizabeth W. Dunn. (February 2015). Checking email less frequently reduces stress. Computers in Human Behavior, 43, 220–228. Author-hosted published article; pp. 221–222, Sections 4.1–4.2; p. 225, Section 5.2.
- Indy Wijngaards, Florie R. Pronk, and Martijn J. Burger. (7 January 2022; March issue). For whom and under what circumstances does email message batching work?. Internet Interventions, 27, 100494. Published article; Sections 2.1–2.2 and 3.3, Tables 2–3, Model 1 and footnotes.
- Ut Na Sio and Thomas C. Ormerod. (January 2009). Does Incubation Enhance Problem Solving? A Meta-Analytic Review. Psychological Bulletin, 135(1), 94–120. Published article; p. 97, selection criteria; pp. 102–109, results and discussion, including Tables 9–13.
