Skip to content

A little more clarity

Context Switching: Why Returning to Work Takes Effort

6 min readPublished

Context switching means moving between activities that require different information, rules or goals. You leave a draft to answer a message, move from a spreadsheet into a meeting, or return to an application after handling an urgent request. The switch may be necessary, but it still asks you to reconstruct what you are doing.

In this guide
Hands using a laptop on a wooden table beside teal headphones, a mint folder, a phone and coffee

You cannot remove every transition from a working day. You can examine which switches are optional, make necessary ones clearer, and leave yourself a useful route back. The aim is to reduce avoidable friction while keeping the flexibility your life and work require.

What changes when you switch tasks?

Different activities ask you to select different goals and responses. Checking a calculation, discussing a customer concern and drafting an argument are not simply three interchangeable uses of time.

Task-switching research reviewed by Monsell found that responses immediately after a switch are often slower and more error-prone. Preparation can reduce these costs without eliminating them. These findings come largely from controlled tasks; they do not establish that each office interruption costs a fixed number of minutes.

The practical implication is modest: changing activities is not always instantaneous. If your schedule assumes that every minute between appointments is immediately usable for demanding work, it may leave out the time needed to understand and resume that work.

Attention residue: when the previous task stays with you

Attention residue describes thoughts about a previous activity continuing while you try to work on the next. In Leroy's experiments on work-task transitions, leaving an unfinished task could affect subsequent performance.

This is related to switching, but it is not identical to a brief reaction-time cost. You might understand the next task perfectly while still mentally rehearsing an unresolved discussion or remembering the paragraph you left incomplete.

It also does not mean that you must finish every task before moving on. That would be impossible for many projects. Instead, ask whether you can make the unfinished work easier to put down: identify its current state, preserve the next step and decide when it needs attention again.

Separate optional switches from necessary ones

An incoming cue is not automatically an instruction to change activities. Sometimes you can choose when to respond; sometimes the request genuinely takes priority. Distinguishing the two helps you change the part of the day you can influence.

Kind of switchExampleA response to consider
OptionalOpening a news tab while a document loadsCapture the urge or idea and return to the document
ScheduledA meeting beginning in ten minutesStop at a useful point and leave a restart note
Necessary and urgentA safety issue or time-critical service requestSave your place if possible, then respond
Necessary but flexibleA colleague needing an answer todayAgree a response time that fits both tasks
DeliberateWaiting for information before continuingRecord the dependency and choose another activity

Some roles require rapid response. A plan for those roles should support clear handovers and reliable cues rather than assume long periods of isolation. Where optional interruptions dominate, a shared agreement about availability may help more than changing another personal setting.

Leave a ready-to-resume note

Before changing activities, record enough information for your future self to restart. A useful note answers three questions: where am I, what comes next, and what still needs a decision?

Leroy and Glomb studied a ready-to-resume intervention in the context of interruptions and anticipated time pressure. Briefly planning a return reduced the effects they observed across four studies. The following note is a practical adaptation of that idea, rather than a promise that all interruptions become harmless.

You could write: “I have compared options A and B against the brief. Next: check delivery terms for C. Unresolved: whether the deadline is negotiable. Resume after the team meeting.” Include a link or page number if finding the material again would otherwise become another task.

Keep the note at the point of return: in the document, on the relevant task or beside the materials. A detailed note in a forgotten app is less useful than a short one you will encounter.

A worked example: a request in the middle of analysis

You are examining survey responses when a colleague asks for a decision needed before a client call. Ignoring the request would delay someone else's work, but you are in the middle of checking an unusual result.

Before responding, mark the row you were checking. Write: “Check whether duplicate responses explain the change in column D; use the filtered export, not the raw sheet.” Save the file. Then turn to the colleague's question and clarify exactly which decision is needed.

After the call, open the saved view and read the note. You still need to reorient yourself, but you do not have to reconstruct the unfinished question from scratch.

Later, consider whether similar requests could be anticipated. A short shared decision window or clearer responsibility might reduce future interruptions. The personal note helps with the transition; the team discussion addresses the recurring condition.

Batch selectively, not automatically

Grouping similar administration can reduce the number of times you move into and out of it. You might answer nonurgent messages during a planned check-in or complete several straightforward expense entries together.

But batching is a choice, not a rule that overrides other people's needs. Waiting too long can create delays, missed information or more urgent interruptions later. Agree the acceptable response time first, and preserve an appropriate route for urgent contact.

For tasks that need sustained reasoning, deep work with interruptions explores how to protect a realistic stretch. For the reminders and external cues involved in returning, see cognitive offloading.

Review the pattern, not just the number of switches

A count of open tabs or interruptions cannot tell you whether your day worked. A single unresolved request may matter more than several brief, well-managed transitions.

Ask which switches were useful, which were avoidable and which exposed a missing agreement. Did you have a clear next action when you returned? Was the workload realistic? Did the same uncertainty interrupt several tasks?

Choose one recurring transition to improve this week. Leave a restart note before it, or agree when a nonurgent request will be handled. Our guide to focusing at work helps you connect that change with a concrete outcome. If you need to understand the wider pattern first, try Clear Mind or explore attention management.

Sources and further reading

Clear Mind