Grivun

HomeGuides

How to stop getting distracted at work

Work distraction is rarely one big thing. It is forty small ones, most of them arriving through the same three doors: notifications, chat, and the browser. Close the doors and the blocks take care of themselves.

Updated 8 September 2026 · by Grivun

~23 minto get fully back into a task after an interruption (Gloria Mark, UC Irvine)
2deep-work blocks a day, on the calendar and marked busy, is the whole goal
2–3email and chat windows a day, instead of a tab that is always open

Interruptions cost more than they last

A two-minute question is not two minutes. Gloria Mark's team at UC Irvine, observing knowledge workers in their actual jobs, found it takes around twenty-three minutes to fully return to an interrupted task, and that people often complete two other things in between. Her later measurements put the average time on any one screen at 47 seconds.

The conclusion is not that colleagues are the problem. It is that a workday without protected time is a workday made entirely of recovery.

1. Triage notifications at the source

Notification triage Needs you Does not need you Now Later Answer A colleague is blocked, production is down, the client is on the line. Keep one channel for this and nothing else. Mute Channel chatter, reactions, "FYI" threads. Mute the channel, not the person. Batch Email, code reviews, approvals, questions that tolerate two hours. Handle them in your windows. Unsubscribe Digests, automatic notifications, tools announcing themselves. Turn off at the source.
Most notifications land in the bottom two boxes. Sorting them once, at the source, removes them from every future block.

Do this once, in the settings of each tool, and it holds for months. The test for each notification is simple: if it arrived at 10:04 instead of 11:30, would anything change? For nearly all of them, nothing would.

2. Two deep blocks on the calendar

A workday with two protected blocks Deep work Email Meetings Lunch Deep work Chat Small tasks 9:00 11:00 13:00 15:00 17:00 18:00 Deep work Meetings, small tasks Chat and email
Deep work first, with the tank full. Chat and email get thirty-minute windows before and after meetings. Small tasks go where the energy is lowest. Adjust the hours; keep the shape.

Put them in as busy so meetings land elsewhere, and treat them like meetings: you would not answer chat during one. Morning blocks are usually the strongest. If mornings are full of standing meetings, the afternoon block becomes the important one, and the calendar should say so.

Tell people once

"I do two focus blocks a day, 9 to 11 and 2 to 3:30. Chat is closed then; I check it at 11 and 4. If something cannot wait, call me." One message to the team, and the blocks stop being a mystery. Most people ask how to do the same.

3. Chat and email in windows, not as a background

A chat window that is always open is a slot machine with colleagues in it. Close it during blocks, set a status with the time you are back, and open it fully in the windows: read everything, answer everything, close it again. Thirty minutes of full attention clears more than four hours of glancing.

If the team's culture expects instant replies, the fix is a conversation about response times, not a browser tab. Almost every message tolerates two hours. The ones that cannot have a phone number.

4. Close the browser doors

The browser is where most self-interruption happens, because the same window holds the work and the escape from it.

Feed mode and focus sessions are free. Daily budgets, schedules and the strict lock are Pro, with a seven-day trial at install.

5. Working from home

Working from home
  • A start and an end. A short walk before and after replaces the commute as the switch.
  • One place for work, even if it is one side of the table, and nothing else happens there.
  • A separate browser profile with only work bookmarks and extensions. The personal profile stays closed until the day ends.
  • The phone in another room is easier at home than anywhere else. Use it.

Set it up this week

  1. Monday: notifications. Twenty minutes in the settings of chat, email and every tool that pings. Sort each one into answer, mute, batch or unsubscribe.
  2. Two blocks on the calendar for every day this week, marked busy. Send the one message to the team.
  3. First block: chat closed, status set, one browser window, phone elsewhere.
  4. Windows at 11 and 4. Everything read, everything answered, closed again.
  5. Friday: look at what got finished. Compare it with a normal week. Then keep the blocks.

Questions

My job is customer support or on-call. Blocks are impossible.

Then the block is shorter and the window is the job. Even support work has tasks that need twenty minutes of unbroken attention: writing the reply that will get reused, fixing the recurring issue. Protect those with a colleague covering the queue, and trade.

I work in an open-plan office and the noise is the distraction.

Headphones are the accepted signal, with or without sound. Book a room for the deep block if there is one. And the browser part still applies: most open-plan interruptions are self-inflicted.

The distraction is work itself: new tasks keep arriving.

Capture them on a list during the block and sort them afterwards. A task that arrives mid-block is almost never more urgent than the one you were doing; it is only newer.

Does Grivun block Slack or Teams?

It can block the web versions during a session if you add them, but that is rarely the point. The point is closing the feeds and the escape hatches so the chat window can be closed on purpose, in a window, by you.

Try it on the site that costs you the most

Grivun is free for up to three sites and feed mode on one platform, with seven days of full Pro to start. No account, and nothing leaves your browser.

Add to Chrome — free