top of page

The Hidden Productivity Costs of Switching Between Multiple Apps

Oct 20
12 min read
Illustration of a worker switching between multiple productivity apps

App switching, also called context switching or the toggle tax, is the time and focus lost every time you move between tools such as email, Slack, Microsoft Teams, a CRM, and a project board. Research shows the average knowledge worker toggles between apps and websites nearly 1,200 times a day, losing just under four hours a week, or about 9% of working time, to reorientation alone. The deeper costs, including attention residue, slow recovery, more errors, and fatigue, push the real figure higher.

Key takeaways

  • Workers switch between apps and websites about 1,200 times a day.

  • Each switch costs around two seconds, which adds up to roughly five working weeks a year.

  • After an interruption, people take an average of about 23 minutes to return to the original task.

  • Workers lose about 59 minutes a day searching for information spread across different apps.

  • Part of your attention stays on the previous task after each switch, an effect called attention residue.

  • The most effective fixes are fewer tools, clear rules about where information lives, scheduled message checks, and protected focus blocks.

Open your laptop on a normal workday and start counting. Email. Slack or Teams. A project board. A shared drive. A CRM. The calendar. A browser holding fourteen tabs, three of which you meant to close yesterday. By lunch you have probably jumped between these windows hundreds of times.

Each jump feels free. It takes a second, maybe two. Nobody budgets for it, and no timesheet has a column for it.

That invisibility is exactly why it matters. One switch costs almost nothing. The same switch repeated across a day, a team, and a year costs a great deal, and the minutes you can measure are only part of the bill. Constant app hopping also thins out attention, invites small mistakes, scatters information across systems, and leaves people drained in a way they struggle to explain when they log off.

This article looks at what the research says about switching between apps, why the real cost is larger than the stopwatch suggests, how companies ended up with so many tools in the first place, and what individuals and teams can realistically do about it.

One note on evidence before we start. Some of the most repeated numbers in this field get stretched as they travel from paper to blog post to slide deck. Where a figure carries caveats, you will find them here rather than buried.

How much time does app switching cost?

The clearest measurement of app switching comes from a 2022 study that tracked 137 people across 20 teams at three large companies for five weeks, logging every move between applications and websites.

The average person toggled nearly 1,200 times a day. Each switch cost a little over two seconds of reorientation. That sounds harmless until you multiply it out: just under four hours a week spent finding your place again, which works out to roughly five working weeks a year, or about 9% of annual time at work.

Two other findings from that study deserve more attention than they get. First, after 65% of switches, people moved to yet another app within 11 seconds. In other words, many visits to an app were barely longer than the cost of getting there. Second, the extremes were far worse than the average. At one consumer goods company, a single employee working across 22 applications and websites could toggle more than 3,600 times in a day.

Other workplace research points the same way, even though it measures different things:

  • A 2022 survey of knowledge workers found people move between nine apps a day, and linked that sprawl to lower efficiency and missed messages.

  • A 2021 study run with university researchers found people lose 59 minutes a day hunting for information spread across tools like Google Workspace, Dropbox and Slack. That is about five hours a week spent looking, not working.

  • A 2025 analysis of workplace software data described workers being interrupted roughly every two minutes during core hours by meetings, emails or chat, with the average employee receiving 117 emails and 153 Microsoft Teams messages a day.

A caveat on that last figure. The widely shared number of 275 interruptions a day has been described as a count for the most heavily pinged users, not a universal average. It is a strong signal of communication load, not proof that every worker faces 275 breaks a day.

The more important caveat runs the other way. The 9% estimate only counts the two-second reorientation after each switch. It does not count what happens to your concentration afterwards. That is where the higher cost sits.

Why does context switching hurt productivity?

Moving your cursor to another window is mechanical. Moving your mind there is not.

In a set of four experiments published in 2001, researchers asked people to alternate between tasks such as solving math problems and classifying shapes. Switching always cost time. The researchers proposed that the brain does it in two stages: first deciding to change goals, then switching off the rules of the old task and loading the rules of the new one. That second stage took longer when tasks were complex or unfamiliar.

One of the researchers later estimated that the mental blocks created by switching can eat up to 40% of a person's productive time. That number is quoted everywhere, usually without its context. It is an extrapolation from the lab work, an upper bound for complex tasks rather than a figure measured in the experiments. The direction of the finding is solid. The precise percentage should be held loosely.

The second mechanism is subtler. Researchers call it attention residue, a term introduced in a 2009 paper. When you move from Task A to Task B, part of your attention often stays behind with Task A. You are technically answering the client email, but some of your mind is still on the spreadsheet you left half-finished. That leftover attention means fewer resources for the thing in front of you.

Ethan Richardson, CMO of Exquisite Timepieces, explains how this plays out in everyday work: "The frustrating part about switching between apps isn't the few seconds it takes to open another window. It's having to remember where you left off, what you were thinking, and what you were about to do next. When that happens repeatedly throughout the day, even straightforward work starts taking longer than it should."

Residue is strongest in exactly the conditions app switching creates: unfinished tasks, interruptions, and the nagging sense that you will have to rush when you get back. The underlying problem is a gap between what we ask the brain to do and what it can actually do. We assume attention goes wherever we point it. It does not move that cleanly.

Then there is recovery time. Field studies of knowledge workers in real offices found people switched activities about every three minutes, and that after an interruption it took an average of 23 minutes and 15 seconds to get back to the original task, usually after visiting two other tasks first. A related peer-reviewed paper from 2005 reports a similar mean of about 25 minutes, with very wide variation between people.

That figure is also easy to misread. Those 23 minutes are not spent staring blankly at a screen. People are doing other work in the meantime. The cost is that the original task sits abandoned, and returning to it means rebuilding context from scratch. In practice, many people no longer have workdays so much as a string of work minutes that last all day.

Put these three findings together, and the two-second switch looks like the visible tip. Each app switch triggers a reload cost, leaves residue behind, and, if it pulls you into a different task, delays your return to the work that actually matters.

What are the hidden costs of switching between apps?

Lost minutes are the easiest cost to talk about because they can be counted. The harder costs are the ones nobody tracks.

More small mistakes

When part of your attention is still on the previous window, the current task gets less of you. In practice, that looks like a figure copied from the CRM into the proposal with one digit wrong, a reply sent to the wrong thread, or a file uploaded to the wrong client folder. None of these feels like a productivity problem in the moment. Each one becomes a correction, a follow-up email, or an awkward call later.

Jeffrey Zhou, CEO and Founder of Fig Loans, highlights the hidden cost of small mistakes: "A wrong number or missed detail might take seconds to enter, but fixing it can take hours. In financial services, that extra work can also delay things for the customer."

The task-switching research makes the stakes concrete with a driving example: half a second lost to switching between a phone conversation and the road is enough distance to cause a crash. Office work is rarely that dangerous, but the principle holds. Switching costs grow with complexity, so the work that most needs care is also the work most damaged by fragmentation.

Stress and fatigue

Interruption research has linked frequent switching to a build-up of stress, and found that people already prone to stress tend to switch more, which can make the cycle worse. Self-reports match. In the 2021 study mentioned earlier, 45% of workers said constant toggling made them less productive, and 43% called it mentally exhausting.

That exhaustion is easy to misread as a personal failing. Someone ends the day tired and feels they achieved little, without seeing that they spent it being pulled between eight windows. The work felt busy. It did not feel finished.

Scattered knowledge

When a decision lives in a chat thread, the supporting file sits in a shared drive, the task is on a project board, and the client's latest request is buried in email, nobody has the full picture. People spend time searching, and when search fails, they interrupt a colleague. Each of those interruptions creates a fresh switch for someone else.

This is how app sprawl spreads its cost across a team. One person's missing information becomes another person's broken focus. The survey that counted nine apps a day tied higher app counts directly to missed messages, which is the same problem viewed from the other side.

Work that never switches off

Recent workplace data describes what some now call the infinite workday. Around 40% of employees check email before 6 a.m., evening meetings after 8 p.m. rose 16% year on year, and nearly a third of active workers are back in their inboxes by 10 p.m. Part of this reflects global teams and flexible schedules. Part of it reflects days so fragmented by pings and switches that focused work gets pushed into the hours when the pings stop.

David Finberg, CEO of Peaks Digital Marketing, points to a common problem behind these extended workdays: "I've seen how easily a full day can disappear into answering messages, checking campaign updates, and jumping between client requests. You're busy the entire time, but the work that actually needs your attention keeps getting pushed back. That's when people start opening their laptops at night just to finish what they couldn't get to during the day."

That is the quietest cost of all. When the workday cannot hold deep work, people borrow from their evenings to get it done, and the true price of a crowded app stack shows up as burnout rather than as a line item.

Why do workplaces use so many apps?

Nobody sets out to build a workplace that requires 1,200 switches a day. It happens one reasonable decision at a time.

A team adopts a chat tool to cut down on email. Marketing picks a project board that suits its workflow. Sales already lives in the CRM. Finance needs its own approval system. Someone adds a note-taking app, someone else a whiteboard tool, and a client insists on their own portal. Each tool solves a real local problem. Nobody owns the total.

The pandemic accelerated this. Industry analysts note that the number of ways workers stay in touch digitally rose sharply during that period, and that many workers now use six to eight apps to complete a single business process. Many of those tools were adopted in a hurry, to solve an urgent problem, with little thought about how they would fit together.

Shadow IT adds another layer. As commentators pointed out after the 2022 toggling study, some of the apps people toggle between were adopted by individuals or departments without IT ever being involved. Those tools rarely integrate with anything, so every piece of information inside them has to be carried across by hand.

The study's authors identified one more cause that is easy to miss: rollout decisions often reflect the experience of power users rather than average ones. A tool that feels fast and flexible to the person who chose it can feel like one more window to monitor for everyone else.

The result is a stack that grew by addition and rarely by subtraction. Their own conclusion was blunt: poor work design and a pile of applications have made the way we work a distraction in itself.

How to reduce app switching and protect focus

The goal is not zero switching. Some switches are the work. Interruption research has found that interruptions related to the task you are already doing can actually help, and that routine, low-thought tasks suffer little from being broken up. The target is the unrelated, unplanned switch that drags you out of something demanding.

For individuals

  • Check messages on a schedule, not on arrival. Set specific times to clear email and chat, and turn off notifications that do not need an instant reply. Most of them do not.

  • Write a ready-to-resume note. Research on attention residue found that taking a minute before an interruption to jot down where you are and what comes next significantly reduced attention residue and improved performance on the new task. One or two lines is enough.

  • Group work by tool. Do all your CRM updates in one block and all your document reviews in another, rather than weaving them through the day.

  • Protect focus blocks. Put 60 to 90 minutes on the calendar with chat closed and the phone out of reach. Treat it like a meeting you cannot skip.

  • Finish before you leave, when you can. Residue is strongest when tasks are left half done. Closing a small loop before switching costs less than reopening it later.

For teams and managers

  • Audit the stack. List every tool the team uses and map which ones touch each core workflow. Look for overlaps, such as two places where tasks get tracked or three where files get shared, and retire the weaker option.

  • Agree where things live. Write down a simple rule set: decisions go here, files go there, urgent requests come through this channel. Half the searching problem is uncertainty about where to look.

  • Integrate what stays. Where two tools must coexist, connect them so updates flow between them instead of being carried by hand. Bring notifications into one place where possible.

  • Design for the average user. Before rolling out a new tool, test it with the people who will use it occasionally, not just the enthusiast who requested it.

  • Set response-time norms. Workplace researchers recommend that teams agree on response-time expectations so nobody feels pressure to answer in the evening. A shared understanding that a chat message can wait two hours removes a large share of reflexive switching.

  • Measure before you buy. Ask how many apps a new tool will replace before asking what it will add. If the answer is none, it will probably add switching.

"When employees have to jump between different apps just to check schedules, find job details, or share updates, they're spending more time managing information than doing their actual work. Businesses should focus on keeping essential information in one place so employees can get what they need without constantly switching tools," says Andrew Bates, COO of Bates Electric.

None of these steps needs a large budget. Most need someone to decide that the cost of switching is real, and to own the problem across the team rather than leaving each person to cope alone.

Frequently asked questions about app switching

What is app switching?

App switching is moving your attention between different software tools during the workday, such as jumping from email to Slack to a spreadsheet. Each move forces your brain to reorient, which costs time and focus even when the switch itself takes only a second or two.

What is the difference between app switching and context switching?

Context switching is the broader idea of shifting your mind from one task or topic to another. App switching is one of its most common forms at work. Not every app switch changes the task, but many do, and those carry the highest cost.

How much productivity is lost to context switching?

One large study found that reorienting after app switches takes just under four hours a week, or about 9% of annual working time. Lab research suggests that switching between complex tasks can cost far more, with some estimates reaching up to 40% of productive time, though that upper figure is an extrapolation.

How long does it take to refocus after switching apps?

Workplace field research found that people take an average of about 23 minutes to return to an interrupted task, usually after handling two other tasks in between. The time varies widely from person to person and depends on how complex the original task was.

What is attention residue?

Attention residue is the part of your attention that stays on a previous task after you move to a new one. It is strongest when the first task is unfinished, and it leaves fewer mental resources for the work in front of you.

Sharon Amos, Director at Air Ambulance 1, highlights why this can be particularly problematic in time-sensitive work: "You can move on to the next task without being mentally finished with the last one. In work where timing and accuracy matter, that divided attention can lead to missed details or decisions that take longer than they should. Finishing one important task before picking up another can make a real difference."

How many apps does the average worker use?

Surveys of knowledge workers report people moving between around nine apps a day, and using six to eight apps to complete a single business process. Large organizations can have far more in their wider stack.

How can teams reduce app switching?

Start by auditing every tool the team uses and retiring overlaps. Then agree where decisions, files, and requests should live, connect the tools that must coexist, set response-time norms, and protect regular blocks of uninterrupted focus time.

Conclusion: fewer switches, better work

App switching hides its cost well. A single toggle takes two seconds and feels like nothing. But the evidence points to a much larger total: around 9% of working time lost to reorientation alone, plus attention residue, slower returns to important work, more small errors, an hour a day spent hunting for information, and a workday that leaks into evenings.

The fix is rarely another tool. More often it is fewer tools, clearer rules about where work lives, and a few personal habits that protect stretches of real focus. Teams that treat switching as a design problem, rather than a willpower problem, are the ones most likely to win back the time.

Start small. Count the apps you opened yesterday. Then ask which of those switches you actually chose.

Give every agent the context to do better work

Connect your agents to the knowledge, decisions, and history already organized in remio.

remio currently supports Windows 10+ (x64) and Macs with Apple silicon.

Your AI Partner at Work
Get more done with remio

Plan. Create. Deliver.
All in one place.

bottom of page