It’s time to examine the good, the bad, and the very ugly elements of context switching. Even better, we’ll take a look at some strategies for managing it.
You say that getting back to the task spent 23 minutes. But I can't find it in the text that you link for. Moreover, they say that people who had been distracted finished tasks faster than people who hadn't. Could you find the part about 23 minutes and copy it here?
I don't know why everybody is considering e-mail replies as a low priority/or shallow work?! Maybe a reply to an e-mail or slack message can save hours to the other part and help him to perform well.
Interruption is bad, yes, we agree with that. But the solution is not as simple as changing status to "Do not disturb" and ignoring the rest of the world around.
I treat interruptions the same way as I enforce boundaries. No matter what the interruption is, I need X minutes to be at a stopping point (aka shelve my work, write notes to come back to) with the current work. Eventually some interruptions come as "I need you in 5 minutes"
You say that getting back to the task spent 23 minutes. But I can't find it in the text that you link for. Moreover, they say that people who had been distracted finished tasks faster than people who hadn't. Could you find the part about 23 minutes and copy it here?
I don't know why everybody is considering e-mail replies as a low priority/or shallow work?! Maybe a reply to an e-mail or slack message can save hours to the other part and help him to perform well.
Interruption is bad, yes, we agree with that. But the solution is not as simple as changing status to "Do not disturb" and ignoring the rest of the world around.
Great article btw. Thank you Addy!
I treat interruptions the same way as I enforce boundaries. No matter what the interruption is, I need X minutes to be at a stopping point (aka shelve my work, write notes to come back to) with the current work. Eventually some interruptions come as "I need you in 5 minutes"