.svg){kind=logo}
On this page
Measure the work, not the signal.
See productive time and utilization by team, not just what looks active.
Key takeaways
- The cost of context switching sits between the effort a team puts in and the output it produces, where standard reports don't look.
- Each interruption carries a recovery cost, and across a working week those costs add up to hours per person.
- Personal focus habits fall short because tools, handoffs, notifications, and meetings build interruptions into the work.
- A team can price its own switching cost with four inputs and set the result beside a hiring request.
- The lasting fix is a redesign of how work reaches people, with AI taking on summaries, routing, and status updates.
Your team puts in full hours and still produces less than the effort suggests. Much of that output gap is switching cost, and no hours report or task count measures it. The cost of context switching at work sits between effort and output. Each time someone is pulled from one piece of work to another, part of the next stretch goes to finding their place again.
Asking people to focus harder won't close the gap. Interruptions arrive with the work itself, through the tools people use, the handoffs they wait on, and the requests that land as notifications. The fix lies in how work flows, and AI can take on much of the switching that people absorb today.
The output gap nobody budgets for
The planning question is familiar: how do we get more from the team we already have? The numbers on hand are hours and task counts. Hours are full. Task counts hold steady.
Effort and output can come apart somewhere between those numbers, and nothing on the dashboard says where. A team can add hours and answer faster while the output line stays flat. Improving team efficiency starts with finding that gap.
Hours measure what went in and task counts measure what came out. The cost of getting from one to the other lands in neither column, so no budget line covers it.
What context switching costs
Context switching at work is moving attention from one task, tool, or conversation to another before the first is finished. Every move carries a recovery cost, because the mind has to reload where it left off.
Three published findings put numbers on that cost.
UC Irvine's Gloria Mark told Fast Company in 2008 that it takes 23 minutes and 15 seconds on average to get back to the task after an interruption.
A 2022 Harvard Business Review study followed 137 users on 20 teams at three Fortune 500 companies and counted about 1,200 switches a day per person. They lost just under four hours a week to reorienting, roughly 9% of their work time.
The American Psychological Association's 2006 summary says brief mental blocks from shifting between tasks can cost as much as 40% of someone's productive time.
Those findings describe context switching productivity from three angles: the single interruption, the daily toggling, and the share of the working week. None of these costs shows up in a timesheet or a task count, which is how a full calendar and a flat output line coexist. No study measures the whole gap between effort and output, but together they show a large cost that the usual measures miss.
Why "focus harder" doesn't work
The familiar advice on interruptions is a personal checklist: silence notifications, block out focus time, process email in batches. Those habits help one person on one afternoon. Across a team they fall short, because the conditions behind interruptions are structural.
A request that arrives as a notification gets answered because the system that sends it expects an answer. Block the calendar and a colleague whose work depends on yours still needs a reply. Batch the email and the same question turns up in chat.
Some of the switching is self-inflicted. In the same interview, Mark said roughly half of interruptions are self-interruptions. That doesn't make it a discipline problem. A person with every tool open and every request arriving as a notification has more to be pulled toward, and no habit closes the tools the job requires.
On its own, personal discipline can't fix a problem that starts with how work reaches people.
Where the switching comes from
Most context switching examples trace back to four sources, and each one started as a decision.
Tool sprawl comes first. Resolving one ticket can send a support agent through a helpdesk, a customer database, a billing system, and a chat window, and every hop is a switch.
Handoffs between people come next. Every person a task passes through is another wait and another restart. A developer pulled out of a build to answer a Slack question is the familiar case, and the question exists because a handoff needed an answer.
Notification norms follow. When every request arrives as a ping, the sender decides when the receiver's attention moves. Microsoft's 2025 Work Trend Index draws on Microsoft 365 data. It found that the most-pinged employees are interrupted by a meeting, email, or chat about every two minutes of the core workday.
The last source is meetings cut into the day. A meeting at eleven interrupts the work before it as well as the hour it fills. A manager stepping out of a budget review and into a hiring call has no gap to reset in.
Each of these is a choice someone made: which tools to buy, who signs off, how requests get sent, when to meet. Each can be changed.
How to put a number on it for your team
A team can put a rough number on this by multiplying four inputs: switches per hour, recovery time in hours, loaded hourly cost, and headcount. Loaded cost means pay plus benefits and overhead for an hour of work. The result is the cost of switching for each hour the team works, and a budget owner can set it beside a hiring request.
Count the interruptions that pull someone off a task, such as a chat message that needs an answer. A quick toggle between apps doesn't count.
Take the recovery time from your own team by asking people how long it takes to get back into the work. Gloria Mark's 23 minutes describes a full interruption. The Harvard Business Review study counted app toggles, which cost seconds each. Neither figure suits every switch.
For example, say a support team of 10 loses three minutes to each of two interruptions an hour, at a loaded cost of $60 an hour. That's six minutes of every hour, a tenth of the working time. The loss is $6 per person and $60 an hour across the team.
Redesign the flow of work
Reducing context switching means changing how work flows, and each change answers one of the four sources.
Put fewer tools in the path of a task, so a ticket or a request moves through one place. Batch handoffs: gather the questions a colleague needs answered and deliver them together at a set time. Set protected blocks at the team level, so focus time becomes a norm the whole team respects.
Then let AI take the switching work. Summarizing a long thread, routing a request to the person who owns it, and drafting a status update all pull people out of what they were doing. When an agent handles them, people get the work without the interruptions that used to travel with it.
Measuring AI adoption by team shows which teams have taken up the AI tools and which haven't. Pick one team and one of the four sources, change it, and run the number again a month later.
Seeing the flow before you redesign it
You can't redesign what you can't see. Insightful People Intelligence shows how people work and suggests opportunities to improve their output.
Work Patterns, one of the opportunities for improvement People Intelligence offers, shows how each team spends the workday and suggests ways to improve focus and execution, so the redesign starts where the team loses the most time.
Each opportunity is tracked from a starting point to a target, so the team can see whether the change worked.
Insightful sees the apps, sites and AI tools your people use, and how they use them. It does not log content or capture keystrokes, messages, or documents. People Intelligence uses no screenshots or screen recordings.
Start with a Work Audit. We show your first opportunities on your own data 14 days after the agent is deployed.
Frequently asked questions
What is context switching at work?
Context switching at work means shifting attention to a different task, tool, or conversation while the first is still unfinished. Each shift carries a recovery cost, because the earlier work has to be picked back up. In a 2022 Harvard Business Review study, users switched between applications about 1,200 times a day.
How much time does context switching take?
Gloria Mark of UC Irvine found that, on average, it takes 23 minutes and 15 seconds to get back to a task after an interruption. In a 2022 Harvard Business Review study of 137 users, app switching ran to about 1,200 a day and cost just under four hours a week in reorienting.
What is an example of context switching?
One example is a developer who stops mid-build to answer a Slack question. A support agent hopping between a helpdesk, a customer database, and a billing system is another. So is a manager who leaves a budget review for a hiring call.
How expensive is context switching?
The American Psychological Association's 2006 summary of the research says switching can cost as much as 40% of productive time. To price it for a team, multiply switches per hour by recovery time in hours, then by loaded hourly cost and headcount.
Is multitasking the same as context switching?
No. Multitasking means trying to do two things at once, which in practice usually means alternating between them. Context switching is that alternation, and every switch costs time.
How do you reduce context switching?
Change how work reaches people. Cut the number of tools a task passes through, batch handoffs, set protected blocks for the team, and let AI handle summaries, routing, and status updates.
Is some switching unavoidable?
Some switching comes with any shared work, because requests and questions arrive from other people. The aim is to remove the switching that comes from how work is set up, so what remains is the kind that can't be avoided.
What is the 3-3-3 rule at work?
It's a personal time-management rule: three hours on the top priority, three shorter tasks, and three maintenance activities. It helps an individual plan a day, but it can't fix a team whose interruptions come from how the work is set up.
