Context switching time analytics and refinements

What is context switching time analytics?
Context switching time analytics is the process of analyzing how much time your team has, on average, during which we get interrupted by meetings, IMs (e.g. on Slack, or in MS Teams) and emails sent. If it’s less than 2 hours from interruption - to interruption, it’s context switching time. One of the most popular ways of collecting such data is by running surveys or engaging in other active listening activities with your team. Many companies conduct focus time analytics through existing corporate systems, such as Slack, G-Suite, or Office 365. 

The key to effective context switching time analytics is to do it ethically. This means conducting an analysis on a team level, where individual data is anonymized, and you’re not assessing each employee individually. You should look at your team from a bird’s eye view and collect data on work patterns, and not human characteristics.

What is context switching time?
Context switching time analytics is the process of analyzing how much time your team has, on average, during which we get interrupted by meetings, IMs (e.g. on Slack, or in MS Teams) and emails sent. If it’s less than 2 hours from interruption - to interruption, it’s context switching time. One of the most popular ways of collecting such data is by running surveys or engaging in other active listening activities with your team. Many companies conduct focus time analytics through existing corporate systems, such as Slack, G-Suite, or Office 365. 

Context switching time is the time spent by team members on their work with interruptions created by meetings, IMs (e.g. on Slack, or in MS Teams) and emails sent, if they happen more frequently, than 2 hours at a larger scale. That’s because deep work relates to two hours of uninterrupted work needed to complete complex tasks. If we’re not in a deep work mode, we are in a context switching mode.

How can you, as a team leader, support less context switching in your team?

Here are a few tips:

  • Reserve two hours daily in your calendar for deep work, ideally as one slot,
  • Group intra-team ad hoc sync time before/after recurring meetings (daily / weekly)
  • Group all the other intra-team recurring meetings for one day per week (1-on-1s, knowledge sharing, planning)
  • Reply to IMs & emails 2-3 times per day in 0.5h long slots if possible
  • Organize async brainstorms to improve innovation.

Context switching | refinements:

Configure your Slack notifications →

Read more on our blog:

Mastering Productivity – Proven Tactics to Eliminate Multitasking and Context Switching →Did you know that context switching can slash productivity by as much as 80% →Cut interruptions to avoid context switching and secure deep work for your engineers →

Start working in a data-informed smart way

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.