When someone interrupts you, you notice the interruption. What sneaks right past you is the trip back: the minutes spent finding your place, remembering what you were thinking and deciding what comes next. Let's shine a light on that trip, and then make it a whole lot shorter.
The part nobody counts
Ask anyone how long an interruption took and they'll tell you about the interruption. A two-minute question. A quick reply to a message. A call that ran ten minutes.
That's the visible part. The invisible part begins when the interruption ends. You turn back to your screen and the work isn't waiting where you left it. The window has slid behind another one. The sentence you were building has evaporated. Something else caught your eye on the way back, and now that's open too.
Here's a scene you might recognize. You're halfway through a proposal when a teammate pings: "Can you send me that link?" Easy! You hop into your browser, find the link, paste it, and notice a few new emails. You answer one. You glance at your calendar. A while later you're back in the proposal, staring at a half-finished paragraph, wondering what point you were about to make.
The return trip rarely feels like a cost, because it's spread across small moments of looking and remembering. It can easily end up longer than the interruption itself.
What one field study measured
In 2007, Shamsi Iqbal (then at the University of Illinois) and Eric Horvitz (Microsoft Research) logged how 27 people at Microsoft used their application windows over two weeks, paying close attention to what happened after an email or instant message alert arrived. Their paper, Disruption and recovery of computing tasks, is one of the clearest pictures we have of the return trip.
- After an alert pulled them away, people spent nearly 10 minutes on average on the switch, then another 10 to 15 minutes, depending on the kind of alert, before getting back to focused work on the task they had left.
- The detour was often indirect. People frequently visited several other applications besides the one that had alerted them.
- After about 27% of alerts, people didn't get back to the window they had been working in for more than two hours.
- In interviews, people blamed those long delays on losing the context of what they had been doing.
A few other details from the paper might make you smile in recognition. Once people switched over to their email, they tended to use the moment to check other messages too. Participants said getting their bearings back was harder when several tasks had been left hanging at once. And many of them already left themselves little markers, like a cursor parked in the right spot or a highlight, to help them pick up where they left off.
It was one company, a small group and the email and chat tools of 2007, so the exact minutes won't match your day. The shape probably will.
Three things you have to rebuild
Getting back isn't one step. It's three, and each one takes a little effort.
- Finding it. Which window was it, and where did it go? This is the physical search: cycling through apps, squinting at thumbnails, opening the wrong file first.
- Reloading it. Once you're looking at it, what state was it in? Which paragraph were you editing, which layer was selected, which test was failing?
- Re-deciding. Knowing where you were isn't the same as knowing what comes next. The plan you had in your head before the interruption has to be rebuilt.
Here's the encouraging part: each step has its own fix. A visible, easy-to-spot window shortens the first. A quick marker in the work shortens the second. A one-line note about your next move shortens the third. You won't need all three every time, but together they turn a long trip into a short hop.
Most advice about interruptions is about preventing them. That helps, and we'll get to it. But some interruptions are simply part of the job, so let's focus on making the trip back shorter.
Make the return trip shorter
Leave a note before you leave
Before you turn away, type one line at the top of the document or on a sticky note: what you were doing and what the next step is. It takes seconds, and it answers the third question for you. "Next: tighten the intro, then add the pricing table" beats staring at the page trying to remember.
Stop at a known next step
When you get to choose when to break, stop just before an easy action rather than right after finishing a hard one. Restarting is so much easier when the first move is obvious.
Handle the interruption in a new window
If a colleague needs a link, press ⌘ N for a fresh browser window instead of navigating away from the page you were working in. Your work stays exactly where it was, and when you're done, ⌘ W closes the detour.
Keep the work in sight
This one comes straight from the study. Iqbal and Horvitz found that windows less than a quarter visible took significantly longer to get back to than windows more than three quarters visible. Several participants also said a suspended window left in view on their main display nudged them back sooner. So resist the urge to minimize or bury the thing you plan to return to. We dug into why open work gets buried in your work is already open.
Keep related windows together
If a task spans a browser window, a folder and a document, getting back means finding all three. Treat them as a set, and bring them back as a set.
Try it: the tiny exit ritual
Here's a little routine to practice this week. It takes less time than making a cup of tea, and it pays you back every time you return.
- Freeze the spot. Leave your cursor where it is, or highlight the line you're on.
- Write the next move. One line, right in the document or on a sticky note. Start it with "Next:".
- Leave it visible. Don't minimize. If you need room, open a new window for the interruption instead.
- Handle the interruption. Answer the question, send the link, take the call.
- Close the detour. Close whatever you opened for the interruption, so it doesn't become the next thing sitting on top.
- Read your note first. Back at your work, read the "Next:" line before you touch anything else. Then go!
After a few days it starts to feel automatic. The idea is simple: your next step is waiting for you like a bookmark, instead of hiding somewhere in your memory.
Let your setup carry the context
The common thread is simple: the less you have to hold in your head during an interruption, the less you have to rebuild afterward. Notes, visible windows and sets of related windows all do some of that holding for you.
Iqbal and Horvitz sketched a version of this idea in their own paper. Among their design suggestions: a recovery tool could save the broader context of a task, every application involved, so people could bring it all back together and pick up where they left off.
That's a lot like what Canopy's workgroups are for. You name the windows that belong to one piece of work, and picking the group brings them forward together. If you closed one along the way, it stays in the group marked Restore, and ↵ reopens it. Canopy never moves or resizes your windows; it just helps you get back to them. Our workgroups guide walks through setting one up.
When prevention is the better fix
Shortening the trip back is great, but the shortest trip is the one you never take. If the same kind of alert pulls you away over and over, it's worth asking whether it needs to reach you right now. Checking email at set times, muting chat during a focused block, or turning on a Focus on your Mac can clear out a lot of detours before they start.
Just don't expect perfection. Colleagues will still have questions, and some of those questions will matter more than whatever you were doing. That's okay! Interruptions will keep coming. The return trip is the part you can shorten.
Quick answers
How long does it take to get back on task after an interruption?
It varies a lot. In Iqbal and Horvitz's study, people spent on average another 10 to 15 minutes after the switch itself before returning to focused work on the task they'd left. That was one company with its own tools and habits, so treat it as a sketch, not a rule.
Is it better to answer messages right away or later?
In the same study, the time people took to get back to their task after replying was, on average, about the same whether they answered right away or waited a bit. One wrinkle: when people put a reply off, they were less likely to be back on their original task within two hours. So whichever you choose, the thing you can control is leaving your work in a state that's easy to pick up again.
What's the single most useful habit?
Writing a one-line "Next:" note before you step away. It's quick, it fits any kind of task, and it answers the hardest question, "what was I about to do?", before you even have to ask it.
