The research you're referring to as "it takes 23 minutes" is actually titled "The Cost of Interrupted Work: More Speed and Stress". It doesn't mention ANYTHING about 23 minutes and its main conclusion is that "people
completed interrupted tasks in less time with no difference
in quality. Our data suggests that people compensate for
interruptions by working faster, but this comes at a price:
experiencing more stress, higher frustration, time pressure
and effort." It seems like the author has never seen it.
Useful, I've already used 2 and 3 items but first quite surprised me , definitely will read the PDF
great post!
I'd say that from the developer's end, he/she could do the following to increase the focus hours:
- use the Pomodoro technique
- block personal calendar slots for productive time
- keep dedicated time slots to reply to any queries via Slack or email
Ya, I'm also kind of blown away by the 23 minute data as well.
The research you're referring to as "it takes 23 minutes" is actually titled "The Cost of Interrupted Work: More Speed and Stress". It doesn't mention ANYTHING about 23 minutes and its main conclusion is that "people
completed interrupted tasks in less time with no difference
in quality. Our data suggests that people compensate for
interruptions by working faster, but this comes at a price:
experiencing more stress, higher frustration, time pressure
and effort." It seems like the author has never seen it.