Slashdot Mirror
Slashdot Asks: How Do You Handle Interruptions At Work?
This question was inspired by this anonymous submission:
Analysis of programming sessions and surveys note that programmers take 10-15 minutes to resume editing code after being interrupted. Computer scientists and researchers from University of Zurich and ABB Inc. have designed the 'FlowLight' system which automatically determines a worker's interruptibility using a combination of keyboard/mouse usage, calendar information, and login state, and makes interruptibility visible to other employees using a red/yellow/green LED indicator placed near the desk... Knowledge workers in various locations found that interruptions were significantly reduced by 46%. [PDF]
NBC reports these researchers "also tested a more advanced version that uses biometric sensors to detect heart rate variability, pupil dilation, eye blinks or even brainwave activity," and of course one of the researchers tells the New Yorker that a commercial version "is 'in the works.'" But it'd be interesting to hear from Slashdot's readers about their own solutions -- and how interruptions affect their own productivity at work. So share your best answers in the comments. How do you feel about interrupt
NBC reports these researchers "also tested a more advanced version that uses biometric sensors to detect heart rate variability, pupil dilation, eye blinks or even brainwave activity," and of course one of the researchers tells the New Yorker that a commercial version "is 'in the works.'" But it'd be interesting to hear from Slashdot's readers about their own solutions -- and how interruptions affect their own productivity at work. So share your best answers in the comments. How do you feel about interrupt
"automatically determines a worker's interruptibility using a combination of keyboard/mouse usage, calendar information, and login state, and makes interruptibility visible"
I understand this is for coders, and how someone might think that when they don't tap away angrily they are available for interruption, but it would be safer to assume that when tapping slows or stops, there's a reason for that. And that reason might not always be that they have nothing more to do. Researching stuff, reading stuff, and just thinking about stuff might not be done in parallel with mighty mouse movements and constant tapping, but they are equally important. So my opinion about this is that it's a result based on research that just wasted money. The simplest way is generally better: just ask, or even better just agree on a time to discuss issues, it's really not rocket science.
I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
Looking at it from a manager's perspective:
Work in rooms, not an open-plan office. This way, if someone wants to interrupt you, they have to "pay" a higher price, like messaging you (you may not be available or the nature of the asynchronous conversation may not be convenient) or actually getting up and going to your room.
Cultivate a culture of empathy, wherein people learn to pick up signs that someone is busy working. Apply peer pressure when someone doesn't pick up the cues. Make it an "insult" to destroy someone's flow. Don't be a dick about it, though - there are ways of cultivating this slowly and discreetly.
"Programming is life, the rest is mere details"
I usually tap my headset to indicate I'm listening to the 30+ voices in an all-day conference call — and return to posting on Slashdot.
After a few years of constant interruptions, I just gave up, and never attempted anything except under deadline pressure, which gave me the excuse required to push out interruptions.
I've never been productive since.