What is context switching?
Context switching is shifting focus between tasks, tools or conversations. Each switch costs time to reorient, and work that is interrupted often waits a long time before anyone picks it up again.
How much context switching costs
The cost of context switching shows up in several well-known studies:
- About 1,200 app toggles a day. Researchers followed 137 people in 20 teams at three Fortune 500 companies for 3,200 working days. People switched between apps and websites nearly 1,200 times a day, and spent just under four hours a week reorienting after switches, about 9% of their working time (Harvard Business Review, 2022).
- Interrupted work waits. In Gloria Mark’s studies at UC Irvine, an interrupted task was resumed on average 23 minutes and 15 seconds later (Gallup interview, 2006). Her 2005 paper found that 57% of people’s working spheres, the larger units of work they juggle, were interrupted (Mark, Gonzalez and Harris, CHI 2005).
- Up to 40% of productive time. The American Psychological Association reports that switching between tasks can cost as much as 40 percent of someone’s productive time (APA, Multitasking: switching costs).
- Interrupted every two minutes. Microsoft’s 2025 Work Trend Index found that, during core work hours, people are interrupted about every two minutes (Microsoft WorkLab, 2025).
For context switching productivity, the number that matters is your own. In the sample report, teams switch apps 10.9 times an hour on average, from 7.9 in engineering to 14.2 in support (illustrative figures until the anonymized data is published).
How to measure it in your team
Surveys ask people how often they get interrupted, and people guess. Activity data counts it. To measure context switching in a team:
- Collect app and website activity for two weeks, with employees informed and consenting.
- Count switches between apps per hour of active time, per person, then average them per team.
- Look at the pairs that switch most often, for example a helpdesk and chat, or a CRM and email.
- Compare teams and weeks, not people: the goal is to find broken workflows, not to rank anyone.
hey.space does this with TimeCamp’s desktop app and reports the result at team level. See how workforce analytics software measures time in apps.
Common causes
- Too many tools. Work for one request lives in a helpdesk, a tracker, a chat and a spreadsheet.
- Manual handoffs. Copying a ticket into Jira, then posting the link in Slack, then updating the ticket again.
- Meetings scattered through the day. A 30-minute call every two hours leaves no long block for focused work.
- Notifications. Chat and email set to interrupt instead of being checked in batches.
5 ways to reduce context switching
- Batch similar work. Answer tickets, review pull requests or update the CRM in set blocks instead of as they come in.
- Protect focus time. Agree on meeting-free hours for the team and set chat to do not disturb during them.
- Cut the number of tools per workflow. If a request touches four tools, check whether two of them could go.
- Agree on response times. When chat replies are expected within hours, not minutes, people stop watching the chat.
- Automate the handoffs. The switches that repeat with the same steps, such as ticket to issue to message, are the easiest to remove completely.
When to automate instead
Habits reduce switching; automation removes it. When the same sequence of apps repeats dozens of times a week, a no-code workflow, an RPA bot or an AI agent can do the steps, and the switches disappear with them. hey.space finds those sequences in your team’s activity data and ranks them by the hours they would give back. Read how we find automation opportunities.