Focus Tips

How to stop context switching at work and stay on one task

The expensive part of a work interruption is the restart, not the ping itself. Practical ways to stay on one task: name it, park stray thoughts, batch chat, and change the plan when your stamina runs out.

How to stop context switching at work and stay on one task

You were in the middle of a paragraph. Then Slack lit up, a "quick question" turned into a thread, and when you opened the doc again the sentence you were writing was gone. That is context switching. It is not a character flaw, and it is not quite multitasking. You left one task, paid a restart cost, and came back with part of your attention still on the thing you left.

The practical version of how to stop context switching at work is almost dull. Cut the open loops, and keep a cheap place for the ones that still arrive. Then get honest about fatigue, because a lot of switching is fatigue hunting for something easier.

The cost is the restart, not the ping

Gloria Mark's research is the source of the number people repeat: after an interruption, it takes about 23 minutes to get back to the original task. You rarely lose those minutes in one dramatic block. You lose them in false starts. You reread the last paragraph. You hunt for the file that had the draft, then try to remember why a variable was named that way.

Sophie Leroy called the leftover attention residue. An unfinished task keeps a grip. The sharper the switch, and the fuzzier "done" was, the more of you stays behind. Five small checks can wreck a morning that looked empty on the calendar.

For people with ADHD this is often heavier, and not because they care less. Changing gears is an executive-function job. Each switch spends some of that budget. By the middle of the afternoon the budget is thin, and the newest small task wins.

Fatigue pushes the same way. A hard task feels heavier when stamina is low, so you graze: inbox, a ticket, the doc, the inbox again. It feels like work. Most of it is switching.

Name the task you are on

"Work on the proposal" is not a task. It is a neighborhood. Attention leaves a neighborhood as soon as something more specific appears, like a message you can answer in one line.

Before you start, write two plain lines:

  • The next physical action. Open the doc and draft the pricing section. Not "make progress."
  • What done means for this sitting. Three paragraphs, the bug reproduced, or the outline sent.

If you cannot write those lines, you are not ready to focus. Shrink the task until the next action is obvious. The ambitious version can wait until the first move is boring enough to begin.

Keep that one task visible. A sticky note is enough. A single card in a Doing column is enough. "What am I on?" should have one answer. On Flowa's Kanban board, that limit is the point: one card in progress, everything else waiting. A new idea has to displace the current task on purpose. It does not get to join a quiet pile of half-started work.

Catch the distraction without following it

Most switches begin as a fair thought. You remember the invoice. You wonder whether the API changed. You owe someone a reply. The thought is not the failure. Opening a second project to honor it is the failure.

Park it somewhere that costs less than switching. One line, then back to the task. Do not sort it and do not estimate it. Sorting is a different job, and a tired brain will hide in it.

That parking spot is a brain dump. Flowa's Brain Dump HUD sits over the work for that moment: you capture the stray thought, and the screen you were using stays put. If your notes already live in Obsidian, vault sync keeps the dump from turning into another inbox you never open.

Capture fails when it is slower than giving in. If parking a thought means launching a notes app, making a page, and picking a tag, you will check Slack instead. One field. Clean it up later, during a block you set aside for cleaning.

Pick when chat is allowed

Some interruptions are legitimate. The deploy is broken, the school is calling, a decision is due before a meeting in ten minutes. Most of the rest are other people skipping their own queue.

Pick two or three times of day for chat and email. Outside those, close the app or silence it. If your team will respect a status, set one: "heads down until 11:30, ping me if the deploy is blocked." It will not stop every person. It stops the ones who only wrote because you looked free.

When something does break the wall, leave a short handoff before you go:

  • Where you stopped: the section, the file, or the exact sentence.
  • The next action, already worded.
  • Whether you are coming back in ten minutes or after lunch.

You can leave the task. If you want it back, leave a trail.

Make the other apps annoying to reach

Willpower is a weak lock. The other apps are one click away, and they are built to be more interesting than your paragraph.

For a focus block, open only what this task uses. One browser window. If you need a reference, open that page and come back. Fullscreen helps some people and makes others feel stuck. Try it for a single block before you decide.

A start ritual beats a foggy plan to "be focused." Flowa's Deep Work mode is a drawer for the block: the apps you meant to use, with audio and haptics if a physical cue helps you notice that the block started. The sound does not hand you discipline. It marks a boundary, which is worth more on days when attention is slippery.

AI assistants need the same boundary. One planned question is fine. A chain of "one more prompt" is context switching with a polite interface. Leave the chat closed beside the doc or you will keep drifting. There is a longer take on that habit in the complete guide to AI productivity.

Treat meetings as switches you scheduled

A meeting in the middle of a block is still an interruption. You just put it on the calendar. Stop five minutes early and write the restart line before you join. Do not squeeze in one last edit. You will join the call already elsewhere, then come back unsure which sentence was live.

If you can move things, put focus time next to focus time and calls next to calls. Work, call, work, call, all day, is a schedule made of restarts. A run of calls, then a run of time on one task, can hold the same meetings and cost less.

Leave a few minutes between calls. When bookings sit flush against each other, the restart line never gets written, and whatever the first call stirred up walks into the second.

Check stamina before you promise a long block

A lot of "I can't focus" is "I am cooked, and novelty is taking the edge off." Switching hands you small completions. The hard task hands you none until the end, so a tired brain defects.

Before a long block, ask a blunt question. Do I have the energy for this specific task, or am I about to imitate focus for 20 minutes and then bolt?

If the answer is no, do not open a scatter of medium tasks and call it balance. Change modes on purpose. Use a shallow list you wrote earlier (expenses, bug triage, file renaming, the replies you already parked) and stay with that until some stamina returns. Random grazing is the habit you are cutting. A chosen easy list is still one task at a time.

Flowa's Burnout Guard tracks stamina so this is not a hunch you override every afternoon. When the tank is low, take the smaller task or take a real break. Another tab "for a second" is the pattern you already know.

A break you chose can help: a walk, water, or ten minutes at a window with no podcast. A break that is secretly Slack is more switching. If the phone is the leak, put it in another room. It is annoying, which is why it often does not happen, and it still beats negotiating with a lit screen.

When the job is the interruption

Support queues, incidents, and days of back-to-back screens are made of switches. Being told to "just focus" does not fix that work.

You can still shorten the residue.

Batch similar tickets. Bouncing from a billing bug to a copy question and back costs more than clearing the billing cluster first.

Keep a restart line at the top of whatever you are in. One sentence: "Waiting on the customer for logs. Next, check the retry path." You should not have to rebuild the plot from open tabs.

If you cannot handle the new request now, write it down. An unwritten "I'll get back to that" sits in working memory and taxes the next ticket.

After a rough interrupt, an outage or a hard call, take two minutes before anything that needs depth. Write the restart line, then stand up. Going straight into prose while you are still braced for the incident is how one sentence gets reread six times.

If you manage people, your casual meeting is someone else's switch. They pay the restart on top of the minutes on the invite. Group your asks. Stay async when you do not need them live.

A routine that still works on a bad day

Complicated systems fall over on irritable days. Use a short sequence.

  1. Check stamina. If it is poor, pick the shallow list and stop reading.
  2. Choose one task. Write the next action and what done means for this sitting.
  3. Everything else waits. One thing in progress.
  4. Silence chat outside your windows. Open only the apps this task needs.
  5. Start. When a thought or a ping shows up, capture one line and return.
  6. If you get pulled away, write the restart note before you leave.
  7. When you stop, note where you stopped. Do not sort everything you captured. That sort is its own block.

Messages will keep arriving, and so will stray thoughts. You get quicker at refusing the next ping, and more willing to admit you are too tired to stay.

If the day comes apart, go back to two lines: what was I on, and what is the next action. Begin again from there.

Flowa
Flowa Team Verified Editorial & Research Team

Product, Cognitive Psychology & Deep Work Research

The Flowa Team is a multidisciplinary group of deep work researchers, neurodiversity advocates, and software engineers. We study cognitive performance, ADHD focus protocols, and minimal workflow architecture to design distraction-free tools that help knowledge workers focus, flow, and finish.

Cognitive Science & ADHD Protocols
Privacy-First Architecture
Distraction-Free UX

Related Articles