You block off your morning to finish the quarterly capacity plan before it goes to leadership. You open your inbox to pull up the notes from your last planning meeting so you can get the context you need to start.
There’s another email that looks like it might be urgent: an FYI from your boss about the project you’re on. It’s a thread, 16 replies deep, so you scroll through it, stitching together context as you go.
Then a Slack message lands: "Hey, do you have a sec?" You hop on a huddle and talk through a proposal that’s in review, your boss adding comments as you scroll. A follow-up email arrives with the changes. Asana pings you — a task just moved to "In Review" — but you still have two more due today. One of them is actually done already, you just forgot to update the status. You open Asana to fix it, and it makes you log in again because your session expired. You reach for your phone to grab the two-factor authentication code, and there’s a text from your partner asking about dinner, and you got an email reminder about an upcoming dentist appointment. Your colleague drops by your desk and asks if you have any weekend plans.
Your phone and your desktop both send you a notification to remind you that you have a meeting in fifteen minutes.
Now, what were you doing again? Every switch is a reset; you’re rebuilding context you already had.
Some version of this is playing out for almost every employee in your company, every single day. Multiply the lost momentum across your headcount and a full work year, and task switching stops looking like a personal annoyance and starts looking like a line item.
The real cost of task switching
The modern workday is built for switching. The average employee now uses 23 different apps a day and toggles between them around 1,200 times a day, roughly 2.5 switches every minute. Every one of those switches leaves behind what researchers call attention residue: your focus is still partly stuck on the last thing while you try to get oriented to the next. The reorientation is the tax, and you pay it 1,200 times a day.
This isn’t how work used to look. In 2019, employees used around six apps a day to do their work. Every new tool promises to make work easier, but instead, they’ve made work more fragmented.
The hit to workplace productivity is well-documented. The American Psychological Association estimates that the mental blocks created by shifting between tasks can cost as much as 40% of someone’s productive time. As you start to scale that across an entire organization, these minutes full of app switches start to compound.
And yet despite these circumstances, companies have responded by spending more on IT, not less. IT and software budgets keep expanding, layering on tools meant to close gaps and drive output. Productivity, at least when measured as the share of projects that actually get completed, has stayed essentially flat. More spend, more tools, more switching for the same output.
We unpack that gap in detail in our whitepaper, Continuity is the New Productivity.
How to protect workplace productivity
The instinct is to fix this at the individual level, by introducing a time-management workshop or Pomodoro timers or giving people productivity hacks. But task switching is a system design problem, and it’s one that the operations team owns.
Here are four interventions that can move the needle:
1. Consolidate the tech stack. This is easier said than done, because every vendor is racing to absorb every adjacent feature: Slack does video, Asana does messaging, your email client does scheduling.
The goal isn’t fewer features, but rather fewer places to be. Audit what your team actually opens in a day and look for tools that legitimately cover multiple jobs so that people can log in once and stay in one context instead of bouncing between five.
2. Make "notificationless" the default. Protect focus by designating one channel everyone understands is for genuine, respond-now situations, and then giving people explicit permission to mute everything else.
The evidence here is strong: UC Irvine researcher Gloria Mark found that once workers were pulled off a task, it took them an average of about 23 minutes to return to it.
Make it organizational rather than personal: Set company-wide collaboration hours when people are expected to be reachable, and treat the time outside those windows as protected focus time. When it’s a norm instead of an individual choice, no one feels like they’re hiding.
3. Account for the work that meetings create. Meetings are a huge source of context switching, especially because there’s so much work outside of the meeting itself.
Someone has to write up the notes, extract the follow-ups, update the project board, send the recap, and schedule the next one. This post-meeting translation work is real labor, and because it’s rarely tracked, it’s rarely managed; it just gets absorbed into the margins of everyone’s day as more switching.
Make it visible. Understand how much time actually goes into servicing a meeting, and account for it as part of the process instead of pretending the meeting was the whole cost.
4. Consolidate the system of record. A surprising amount of task switching comes from the same decision or update needing to live in three places at once: a chat thread, a project tool, someone’s inbox. Every one of those copies has to be created and kept in sync, and if it’s done manually, every update is another switch.
Designate a single source of truth per workflow so that a decision gets recorded once and everyone knows where to find it. The goal is to stop asking people to be the integration layer between your tools.
Attention is worth designing for
Notice what these interventions have in common: none of them is about working harder. They’re about reducing the number of times a day your people have to stop, switch, and rebuild their context. Every manual update, every recap, every "let me just log that in the other tool" is a switch that’s been designed into the system. But the good news is that means it’s a switch you can design back out.
The teams that win aren’t the ones that switch faster. They’re the ones whose work builds on itself instead of starting from zero.
