Context switching is moving your attention from one task to another before the first is finished. Each switch has a cost, because the brain has to drop one set of rules and load another. Psychologists say these costs can take up as much as 40% of a person's productive time. The fix is fewer interruptions and longer blocks of work, and it starts with seeing how fragmented the day already is.
Key takeaways
- Switching costs grow as tasks get more complex.
- Microsoft's data shows workers interrupted about every two minutes in core hours.
- Most switching is caused by how work is organized, not by weak willpower.
- Managers control the biggest levers: meetings, priorities and how many projects each person carries.
What does the research say?
The American Psychological Association summarizes decades of experiments on task switching.
- In the mid-1990s, Robert Rogers and Stephen Monsell found that people were slower after a switch even when the switch was fully predictable. Time to prepare reduced the cost and did not remove it.
- In 2001, Joshua Rubinstein, David Meyer and Jeffrey Evans had people switch between tasks such as solving math problems and classifying shapes. Participants lost time on every switch, and lost more as the tasks got more complex.
- They described two stages: goal shifting, which is deciding to do the other thing, and rule activation, which is switching off the rules for one task and switching on the rules for the next.
Meyer has said that even brief mental blocks from shifting between tasks can cost as much as 40 percent of someone's productive time. Treat that as an upper bound from laboratory work, not as a figure measured in your office.
How interrupted is a normal working day?
Microsoft analyzed activity data from its own workplace tools up to February 2025.
- 275
interruptions a day from meetings, email and chat, about one every two minutes in core hours
Microsoft, 2025 - 117
emails received by the average worker each day
Microsoft, 2025 - 153
Teams messages received by the average worker each weekday
Microsoft, 2025
The same report found that half of all meetings fall between 9 and 11 in the morning and 1 and 3 in the afternoon, which are the hours many people would otherwise use for concentrated work.
What causes context switching?
Notifications
Chat, email and alerts that arrive one at a time, all day.
Scattered meetings
Thirty minutes of work between two calls is rarely usable.
Too many projects
A person on four projects owes four sets of people an answer.
Unclear priorities
When everything is urgent, the last request wins.
Three of the four are set by managers.
How do you spot it in your team's day?
You do not need a special metric. Look at how the day is cut up.
Both mornings contain about the same minutes of design work. In the second it never lasts longer than 20 minutes.
Signs of heavy switching
- Many short stretches in different applications, with few long ones
- Chat and email open in every hour of the day
- Meetings spread evenly across the day
- People logging time to four or more projects in a day
- Long days with little finished work
How do you reduce context switching?
Protect two blocks a day
Agree on hours with no meetings, such as 9 to 11 and 2 to 4.
Cluster meetings
Put them next to each other so the gaps are usable.
Batch messages
Check chat and email at set times. Agree what counts as urgent and how to flag it.
Limit work in progress
Two projects per person is plenty. A third should replace one, not join it.
Rank the work
One ordered list per team, so nobody has to guess what comes first.
Write things down
A decision in writing does not need a meeting or six messages.
Review the pattern monthly
Look at the team's day as data and change one thing.
What should managers avoid?
Do
- Ask before you interrupt, and batch your own questions
- Give people permission to close chat while they concentrate
- Count finished work, not replies per hour
- Look at fragmentation by team
Do not
- Expect instant answers to every message
- Add a status meeting to fix a communication problem
- Praise whoever responds fastest
- Use switching data to single out one person
How does BirdsEye show fragmentation?
BirdsEye records which application is in the foreground, in one-minute blocks, inside working hours. Three views make switching visible without anyone filling in a form.
- Timeline. The working day as a chronological band of segments. Long blocks and chopped-up hours are obvious at a glance.
- Hour-of-day heat map. When each person's working time falls, hour by hour.
- Application usage and project time. How much of the week went to communication tools, and how many projects each person touched.
BirdsEye does not calculate a focus score. It shows the shape of the day and leaves the reading to you. Employees can see their own timeline too, which is often where the useful conversation starts. See reports and analytics.
Frequently asked questions
What is context switching?
It is shifting attention from one task to another before finishing the first. Each shift carries a small time cost while the brain changes goals and rules.
How much time does context switching waste?
There is no single measured figure for every workplace. Psychologist David Meyer has said switching costs can take up as much as 40% of productive time, based on laboratory research.
Is multitasking the same as context switching?
In practice, yes. People rarely do two demanding tasks at once. They switch between them quickly, and each switch has a cost.
How long should a focus block be?
Long enough to finish something meaningful. Many teams protect blocks of 90 minutes to two hours, twice a day.