Editing work is serious work. It requires you to hold an entire document’s logic, voice, and structure in your head at once, ensuring you don’t lose your train of thought. That’s why getting interrupted mid-session is one of the worst things that can happen.
And most editors know this.
That’s why they close the door, put on headphones, and get as comfortable as possible. They try to do everything “right,” but then a Slack notification pings or an email lands. Or someone stops by with a “quick” question. So, they deal with it and come back to the doc. They reread the last sentence, trying to pick up where they left off.
But something feels off in a way that’s hard to name.
That unnamed feeling and discomfort don’t happen just because of the interruption. They are there because the editor now also has to recover from that interruption.
And that’s what we will cover today—interruption and recovery. What interruption and recovery look like, why editing work is especially vulnerable to hiatus, and what you can do to protect your deep work sessions and maximize output.
What context switching is
Context switching is what happens when your brain has to stop doing one cognitively demanding task and start another. It sounds pretty easy to do: you stop editing, answer an email, then go back to editing. However, your brain doesn’t work like a computer that can pause and resume cleanly. It takes time to rebuild the working mental model you had before the switch.
Research from the University of California, Irvine found that it takes an average of over 23 minutes to fully return to a task after an interruption. Not 5 minutes, nor 10. Over 20 minutes. And that’s a lot!
Now, imagine an editor who switches context four or five times during a working session. When you do the calculations, they get less deep editing time than their calendar suggests. And sure, the hours of editing are there, but productive editing is not.
And, as an editor, you want and need productive editing. You need that quality of attention.
A fully present editor catches the argument that quietly contradicts itself three pages later. They notice when an author’s voice shifts in a way that suggests the section was written on a different day in a different frame of mind. They sense when a conclusion doesn’t quite carry the weight the introduction promised. These are not things you can catch on a distracted pass.
That’s why context switching doesn’t just slow editors down. It makes them worse at the thing they’re supposed to be best at.
Editing and context switching, oil and water
Not all work suffers from context switching. Think of tasks that are repetitive or mechanical—they can surely handle context switching. Deep editing cannot, for three reasons specifically.
Reason no. 1: Editing involves a lot of mental work
When you’re editing a long document, no matter if it’s a dissertation, a manuscript, or a long-form article, you’re not fixing sentences in isolation. You’re tracking whether a point made in paragraph three still holds up after the revision you made in paragraph twelve.
You’re also objectively monitoring whether the author’s voice is consistent across sections written on different days.
You’re evaluating whether the argument builds properly toward its conclusion.
And the list goes on.
Editing requires a lot of mental processes at once. If you lose your focus, concentration and thread, editing becomes shallower, more mechanical, and you’re more likely to miss the structural problems that actually matter. That’s why context switching is dangerous.
Reason no. 2: The interruptions that hurt editors most are the ones that feel harmless.
Think of a Slack or Teams message from a colleague. An email that looks urgent but isn’t. A quick question from someone in the office.
None of these feel like serious interruptions, yet all of them break concentration in ways that are hard to recover from.
Reason no. 3: Editors often underestimate how much they switch
Most people overestimate how focused their work sessions actually are. Research consistently shows that knowledge workers switch tasks far more frequently than they recall, and that their estimates of how their time was spent are often inaccurate by a significant margin. For editors trying to understand why a project “took longer than expected,” the honest answer is usually somewhere in the switching.
The tax you pay due to context switching
Here’s a more practical way to think about the problem.
You block three hours for major editing work on a long document. During that session, you check email twice, respond to a Slack thread, take an unscheduled call, and glance at a browser tab you left open. And each one of these interruptions took two or three minutes.
That’s not so bad, right? Wrong!
Each two-minute interruption resets your concentration, and if the recovery time after each interruption is even half of what the research suggests—let’s call it 12 minutes instead of 23—five interruptions cost you an hour of deep editing time. When you do the math, out of a three-hour session you’ve lost a third of it to recovery, and because the interruptions felt minor, you didn’t notice.
Now, scale that across a full editing project, and the implications are significant. You’re losing hours, concentration, and focus.
What you can do about context switching
The good news is that context switching is a solvable problem. But in order to solve it, you need to take it seriously:
-
Protect your deep work blocks ruthlessly. A deep editing session should have notifications off, browser tabs closed to anything unrelated, and a clear signal to colleagues that you are unavailable. Something as simple as a Slack status “editing session in progress, back at 3pm” can set the expectation without requiring a single conversation. Your sessions shouldn’t be interrupted unless there’s a genuinely good reason.
-
Batch your low-concentration tasks. Email, admin work, invoicing, and brief client communications all belong in their own time blocks, most ideally at the beginning or end of the day, when your best concentration is either not yet available or already spent. Mixing these tasks into an editing session is what makes things messy.
-
Understand where your time is actually going. Protecting your concentration and focus is much easier once you have data on how your sessions are actually structured, like how much genuine deep editing time you’re getting, where the interruptions are coming from, and how your estimates of a project’s time requirements compare to reality. Automatic time tracking with Memtime gives you that picture without requiring you to log anything manually, so the data reflects what actually happened rather than what you remember.
-
Create a re-entry ritual. When you do get interrupted—and you definitely will—have a simple practice for re-entering the document. Re-read the last full paragraph you edited. Scan your most recent notes or margin comments. Give yourself two minutes to deliberately rebuild the mental model before you try to continue. All these steps may look small, but they’ll meaningfully reduce recovery time.
Conclusion
Deep editing is cognitively expensive work. It means that such work demands attention, a complex mental model, and the ability to evaluate a document at multiple levels simultaneously. Context switching is the enemy of all three.
The fix for context switching is not complicated. Protect your focused time. Batch your shallow work. Track your actual sessions honestly so you know what you’re working with. And when you look at a project that took longer or delivered less than you expected, consider whether the problem was the work itself or the conditions under which the work was done.
Most of the time, it’s the conditions, and those conditions are easily fixable.
Frequently asked questions
What is context switching, and why does it matter for editors?
Context switching is what happens when your brain stops one cognitively demanding task and starts another. For editors, it matters more than most because editing isn’t mechanical; you’re holding an entire document’s logic, voice, and structure in your head at once. Every interruption forces your brain to rebuild that mental model from scratch, which takes time and degrades the quality of your work.
How long does it actually take to recover from an interruption?
Research from the University of California, Irvine found it takes an average of over 23 minutes to fully return to a task after an interruption. Even if you use a conservative estimate of 12 minutes per interruption, five interruptions in a three-hour session cost you roughly an hour of productive editing time, which is a third of your session, gone.
What can I do to protect my deep editing sessions?
The most effective steps are: turning off notifications during editing blocks, batching low-concentration tasks like email and admin to the beginning or end of your day, tracking time, and creating a simple re-entry ritual for when interruptions do happen.
How do I know if context switching is actually affecting my work?
Most editors don’t know because their estimates of how they spent their time are often significantly off. Automatic time tracking tools can give you an accurate picture of how your sessions are actually structured, like how much genuine deep editing time you’re getting and where the interruptions are coming from, without requiring you to log anything manually.
