How does context switching impact team productivity?

In this panel, we’ll dig into why unmanaged context switching is detrimental, and ways you can help developers handle interruptions, and reach (and maintain) a state of focus and flow.

Moderated by Najla Elmachtoub

Presented by Amador Fernández , Cara (Borenstein) Marin , Ryn Daniels

Register or log in to access this video

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

We have linked your account and just need a few more details to complete your registration:

First name Last name Job title Company Country

Terms and conditions I agree to the LeadDev.com terms and conditions of use

Create a password

October 15, 2024

Developers are seasoned pros when it comes to juggling different projects. But there is a difference between multitasking, and jumping between unexpected interruptions – also known as context switching.

More like this

Context switching comes in many forms. Whether it’s pausing a code review to help fix an outage, or stopping coding to join an unproductive meeting, when changes in mental focus become too frequent and abrupt, it can lead to decreased productivity and burnout.

In this panel, we’ll dig into why unmanaged context switching is detrimental, and ways you can help developers handle interruptions, and reach (and maintain) a state of focus and flow.

Register to learn:

The main causes of context switching
The cost of context switching on developer wellbeing and productivity
Strategies like time batching and incident response processes to reduce the impact of interruptions