How to Protect Deep Work From Constant Notifications

If your focus keeps breaking up, the usual advice is to try harder: ignore the phone, resist the inbox, be more disciplined. That framing puts the problem in the wrong place. Notifications are built to be noticed, so protecting your attention is easier when you change the environment and the agreements around your work than when you rely on self-control in the moment.

This guide takes a design approach. You will define what an interruption is, look at where yours come from, sort notifications into three groups, protect one or two focus blocks, and tell the people around you how it works. None of it requires an overhaul, and results will vary by role and workplace.

What counts as an interruption, and why it costs more than a minute

Interruption science uses a precise definition. An interruption is "the suspension of one stream of work prior to completion, with the intent of returning to and completing the original stream of work" [2]. The key feature is a primary task you intend to come back to.

That separates it from concurrent multitasking. Talking on the phone while driving is generally treated as concurrent multitasking, whereas stopping a data entry task to check email is generally treated as an interruption [2]. The second case matters here: checking your inbox mid-task is itself a suspension of work, even if nobody asked you to do it.

Why does that matter? Research generally finds that interruptions are disruptive to performance and induce errors [2]. In offices, where the stakes are lower than in aviation or medicine, interruptions have been linked with stress, anxiety and poorer performance [2]. That is a general finding, not a prediction about any one person, but it is a reasonable argument for treating each suspension of work as having a cost.

The numbers worth knowing, held lightly

Gloria Mark is quoted as saying that "the average knowledge worker switches tasks every three minutes, and, once distracted, a worker can take nearly a half-hour to resume the original task" [2]. A study of office workers is also quoted as finding that "each employee spent only 11 minutes on any given project before being interrupted" [2].

These are striking figures, and they are worth holding lightly. They come from particular workplaces and methods, and your own day may look quite different. Treat them as a sign that the cost of switching can be larger than the seconds it takes to glance at a message, and check the original studies before you quote exact numbers to anyone else.

There is also an older observation about why unfinished work lingers. The Zeigarnik effect describes people remembering uncompleted or interrupted tasks better than completed ones [2]. It is a plausible reason a half-finished report keeps tugging at you while you answer a message about something else.

Two further points from the same body of research are relevant to notifications specifically. Answering notifications impedes task performance and the ability to resume the original task, and even knowing that a notification has arrived can negatively affect sustained attention [2]. So silencing the sound is not always the whole fix. Where a notification is visible, it may still compete for attention.

Audit your interruptions before you change anything

Before changing settings, find out what you are dealing with. Office interruptions come from information technologies such as email, text messages and phone calls [2], and they also come from people and from yourself. Which of those dominates in your week is something only a short audit can tell you.

Exercise: the two-day tally

1. Keep a note beside your work, on paper or in a plain text file.
2. Each time you stop a task, add a mark.
3. Next to each mark, record the source: an app (name it), a person, or yourself.
4. Add one more note: did it need a reply within the hour? Yes or no.
5. At the end of day two, circle the three most frequent sources.

Include the interruptions you started yourself, such as reaching for your phone or opening a tab out of habit. Self-initiated switches are not a failing; they are simply data, and they respond to the same environmental fixes as everything else.

The "needed a reply within the hour" column is the useful one. It separates what is genuinely time-sensitive from what only feels urgent because it arrived with a sound.

Remove, batch or delay: a simple notification triage

For each source on your tally, choose one of three treatments.

• Off. Nothing is lost if you see it later, or at all. Promotional apps, social alerts and most badges belong here.
• Batch. You need to see it, but not now. Check at set times, such as mid-morning, after lunch and late afternoon.
• Immediate. Someone is relying on a fast response, or a delay would cause a real problem.

Batching works for a straightforward reason. Because checking email mid-task is a suspension of work [2], fewer checks means fewer suspensions. You still read everything; you simply choose when.

A caution is worth keeping in mind. One study cited in the interruption literature suggested disabling email notifications entirely, and noted that the downside is that it may create pressure to keep checking email accounts [2]. In other words, switching everything off without a plan can backfire. Batching with fixed check times gives your mind a reason to let go, because you know when you will look.

Exercise: the three-way sort

1. Open the notification settings on your phone and computer.
2. Go through every app and assign Off, Batch or Immediate.
3. Allow no more than three apps in Immediate. Write down, in one line each, why that app earned its place.
4. For Batch apps, remove badges and banners so there is nothing to catch your eye between checks.
5. Put your chosen check times somewhere visible.

Settings differ between devices, but most phones and computers offer a do-not-disturb mode, per-app controls and scheduled quiet hours. Those are the tools to look for.

Protect one or two focus blocks, not the whole day

Trying to defend an entire day against interruption tends to fail, and failure makes the system feel pointless. A smaller target is more realistic: one or two blocks for your most demanding task, each with a clear start and end.

There is no research-backed ideal length, so choose one that fits your work. Many people start with something they can reasonably expect to sustain, such as 45 to 90 minutes, and adjust from there. Schedule the block the way you would schedule a meeting, ideally at the time of day when you do your best thinking.

Self-interruption is the quiet leak. A stray thought, such as "I must reply to that invoice query", can pull you out as effectively as a ping. Keep a scrap page beside you and write the thought down in a few words. You have not dropped it; you have parked it.

Exercise: one block this week

Before the block starts:

1. Write the single outcome you want from it, in one sentence.
2. Close tabs and documents unrelated to that outcome.
3. Set your status to unavailable and switch on do-not-disturb.
4. Put a scrap page beside you for anything that pops into your head.

If you tend to drift at the start, a simple if-then plan can help you begin; there is a practical walkthrough in If-Then Plans: The Simple Trick That Makes New Habits Stick.

Make the boundary visible to other people

Many interruptions come from colleagues, clients and unspoken norms rather than apps. If nobody knows when you are focusing, they cannot work around it, and you end up absorbing every request as it arrives.

A short, polite script is usually enough:

"I'm blocking 9:30 to 11:00 for focused work on the proposal. I'll check messages at 11:00 and again at 1:00. If something can't wait, call me."

Three habits make this work. Say when you will be back, so the delay has an end. Give a route for genuine urgency, so people do not have to guess. And, where you can, agree a response-time norm with your team or manager, such as same day for email and within an hour for the chat channel marked urgent.

Teams can also reduce interruptions structurally. In one reported case, a team of programmers was interrupted through a technical support chat up to 150 times a day, and introducing a dispatcher role and a knowledge base reduced those interruptions [2]. The wider lesson is that routing and documentation can take pressure off individuals, though what is possible depends on your workplace.

Some roles cannot defer messages at all: on-call support, client-facing work, caring responsibilities. If that is you, triage rather than switch everything off. Keep a narrow Immediate list, for example one person or one channel, and batch the rest.

Notice how work actually feels, and adjust

Counting interruptions is useful, but so is the quality of the experience. Work psychologists have argued that the subjective experience of working is a legitimate topic of study in its own right [1]. You can apply a small version of that idea to your own week: notice when you felt interrupted and when you felt absorbed.

Exercise: the one-line debrief

At the end of each focus block, write one line: what interrupted me, and what would have prevented it? After a week, read the lines together and change one setting or agreement based on the pattern. One change at a time is easier to evaluate than five.

Keep the tone low-pressure. Some blocks will be broken by a real emergency, and partial progress still counts. Review your settings weekly, loosen anything that causes more worry than it removes, and tighten the places where the same interruption keeps recurring. For the other side of a demanding day, see Small Daily Habits That Help You Recover From Stress.

A concrete place to start

Today: run the two-day tally. Day three: do the three-way sort, with no more than three apps in Immediate. This week: protect one block, send one short message to the people who will notice, and write one debrief line afterwards. That is the whole system, and each piece can be changed if it does not suit your work.

This article is general educational information, not professional, medical or workplace advice. Your circumstances and obligations will differ.