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

26 of 224 comments (clear)

  1. crap by l3v1 · · Score: 5, Insightful

    "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.
    1. Re:crap by johannesg · · Score: 2

      Geez, just check when the compiler is running. If it is, I have a few minutes for you. See? This really isn't so hard, is it?

    2. Re:crap by flex941 · · Score: 4, Funny

      Some of use JIT! So that should mean you must never interrupt me!

    3. Re:crap by Ol+Olsoc · · Score: 4, Informative

      Geez, just check when the compiler is running. If it is, I have a few minutes for you. See? This really isn't so hard, is it?

      For coders, or anyone in particular, ya gotta remember that your particular job isn't the only, or the most important job at the place.

      Because that interruption might be from the guy who signs your paychecks.

      For me, it isn't coding, but 3-D work. It's like an alternate universe, and while reducing everything to numbers and juggling it all in my head, I do lose track of reality. And it takes time to come back, then get into the 3-D Universe again.

      While my people would "protect" me from interruptions when I was doing that intense work, there were some people who they had to let through. So it was just part of the day.

      If any of y'all have a position where you can thell the director or CEO to slag off - you better keep it.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
  2. Pro-tip by skam240 · · Score: 5, Interesting

    I find wearing headphones (something kind of large that covers the ear, not earbuds or anything) scares off a lot of interruptions. If i'm doing something light I might even have music playing on them but most of them time they're just for show.

    --
    I ignore Anonymous Coward posts. If you want to discuss something, that's awesome. Log in.
    1. Re:Pro-tip by Mal-2 · · Score: 2

      I used to use that trick at the poker table. I'd wear large, conspicuous headphones, and from time to time pull out and fidget with the media player. What I didn't tell people was that I never turned it on.

      It's amazing what people will say when they don't think you can hear them.

      --
      How is the Riemann zeta function like Trump rallies? Both have an endless number of trivial zeros.
    2. Re:Pro-tip by oobayly · · Score: 2

      Same here. I tend to have music on quite low - unless there's a colleague ranting about politics, foreigners or the EU, then the volume goes up to 11 - and I've overheard one person saying "I bet he's not even listening to anything", which I had the good sense to pretend that I didn't hear.

  3. Increase the cost of the interruptor by ovanklot · · Score: 5, Insightful

    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"
    1. Re:Increase the cost of the interruptor by v1 · · Score: 2

      That, and get the managers out of their isolated office and into the same pen area as the coders (or vice-versa) so they can empathize with the coders. In most cases, managers have less of a "knocked out of the zone" issue with their work than coders, and yet we shelter them in corner offices, often behind closed doors, and have something of an "office understanding" that you don't interrupt the manager for something trivial.

      Even if the manager still isn't getting bugged all the time, they now can see it occurring with their own eyes. After Greg stops by yet again, Manager: "Wasn't that Greg again?" Me: "Yep." Manager: "What'd he want?" Me: "problems with his voice mail again." Manager: "why the hell is he asking YOU?" Me: "no idea." A manager with half a clue can quickly see his people getting interrupted for trivial, inappropriate, and unnecessary things and hopefully see the harm this is causing and have a chat with the problem children.

      I work in a small team managing computers on campus, and lately I've been spending a lot of time getting things automated, which involves a fair amount of coding. I'm also closest to the door and the one that answers a good 50% of the calls that ring all the phones in the room. Getting knocked out of my zone is unfortunately a common occurrence for me, but somewhat by design it's part of my job definition, so owell. Once I get things more finalized, I won't be so susceptible to jamming because I'll be spending more time monitoring things than coding, but until then I just have to suffer through it as there really isn't a solution for us right now.

      Parent: consider a whiteboard on the outside of your cubicle, indicating project status. A few here do that and it's somewhat beneficial. This won't work on managers probably, but may help with coworkers. Or propose a weekly meeting, say Monday afternoon before close, where everyone meets to catch up. This will give the manager(s) an opportunity to ask all their project status questions, and lets everyone else know how things are going also. This may be enough to satiate their thirst for updates, and will lump all your interruption into one solid bit of time, minimizing your time spent out of the zone. You may not like the idea of "another meeting" if you already have some to deal with too often, but a half hour meeting right at the end of the day (which should incur no out-of-zone time since you're leaving after the meeting) surely will beat a dozen 5-10 minute interruptions throughout the week. This also gives you a more powerful response if they still bug you, "didn't we talk about that yesterday at the meeting?" "Why didn't you ask about that on Monday?" etc. "But I needed an update!" is no longer a valid excuse to knock you out of the zone.

      --
      I work for the Department of Redundancy Department.
  4. Insert coin. by Anonymous Coward · · Score: 4, Funny

    I have a cash acceptor wired up outside my office, which dispenses sequential tickets. I won't talk to you unless you have a ticket.

    It was kinda a stupid joke I setup one day because I got sick and tired of being constantly interrupted. People actually took it seriously, much to the amusement of my boss. The first day I made well over $120 in spare cash from all the interruptions. The next day, I only made $40, but got so much more work done. The day after that, it was around $10, and then finally people got the hint and it was $0.

    Occasionally someone still comes and knocks on my door, and for the privilege of interrupting me, they get to pay $10 (in cash or coins). If I'm not too busy I'll drag the machine inside and leave it unhooked, but otherwise it's out there by my (closed) door and plugged in, ready to accept payment. I even landed up building an additional three units for our other developers (it's basically just a laser cut plexiglass chassis with an Atmel AVR development board, an OTS cash acceptor, and an OTS ticket printer). Our productivity has skyrocketed as a result, and management even lets us keep the cash we make. Most of the time, it gets reinvested back into the office as donuts or other treats though, so it's not like we're actually making a massive profit or anything.

  5. How to get interruptions to stop! by redcliffe · · Score: 5, Funny

    Unzip pants, start masturbating.

  6. Blank stares by Carewolf · · Score: 2

    I think I chose not to swap out and when interrupted I stay in the working state and just stare blankly at the interruption until it goes away.

  7. Give up by javawocky · · Score: 2

    I have pretty much given up trying to be 'productive' at work. As a team leader I am normally dealing with questions and interruptions the entire time I am in the office. Fortunately, our team decided on something we call Core Hours. If you are at work you need to be around between 10am and 3pm for collaboration. So you can start early and leave early, start late leave late or do what I do: spend time at work to deal with the team - go home early then do the 'real work' after the kids are in bed. Now if I can just deal with my wife asking me questions while trying to hack away...

  8. Re:Incomplete summary by Mal-2 · · Score: 4, Funny

    Did you hear the whoosh as that joke went over your head then?

    I am disappoint

    --
    How is the Riemann zeta function like Trump rallies? Both have an endless number of trivial zeros.
  9. Re:By shooting the person summarily. by Rockoon · · Score: 2

    I compare the new interruptions IRQ to the current interruptions IRQ and will only begin working on the new interruption if it has a higher priority.

    --
    "His name was James Damore."
  10. Headset.... by __aaclcg7560 · · Score: 3, Insightful

    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.

  11. I gave up by ka9dgx · · Score: 3, Insightful

    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.

  12. Re:By shooting the person summarily. by DontBeAMoran · · Score: 4, Funny

    Prioritizing by Interruption-to-Reply-Questions is a good idea, but what if they have Direct Management Access?

    --
    #DeleteFacebook
  13. Companies need to recognise this as a problem by Arakun · · Score: 2

    I used to work in a test tools team and we'd get a lot of visitors wanting help interpreting test results and preferably fix their bugs for them. It was manageable until we got close to release. By that point our scrum master moved to the desk closest to the door and would intercept everyone coming into the room. He'd have them describe their issue to him and then he'd make the call whether to disturb anyone in the team. Still, there was almost constant talking in the room so headphones were a must.

    I've found that one thing that causes a lot of unnecessary interruptions is a lack of documentation. One company I worked for kept almost no documentation since "this is a fun workplace and writing documentation is boring". I had to track down multiple people just to figure out how to set up a working build environment. Another problem is knowing who to ask. Spending some time to create a knowledge matrix and assigning a go-to person for each area helps limit the amount of people that get disturbed and also spread the load.

    Code reviews are another thing that can cause a lot of interruptions. I don't have much experience with code ownership and automatically assigning reviewers so I can't say how well that works in practice.

  14. Always leave 2 untapped islands by netsavior · · Score: 2

    Since interrupt is/was the fastest cast type, I try to leave 2 untapped islands at all times, so I can cast a counter-spell in response to their interrupt, thus negating it and allowing me to get back to coding before I was ever interrupted.

  15. Re:a bunch of things by swb · · Score: 2

    If somone complains about me not being available or that I haven't completed a task, I inform them that I have more tasks than time and I ask my boss to prioritize my assignments.

    That's a nice theory, but the problem is that many managers will ding you on reviews for poor time management. I've known people who got fired for it, being told that part of what was expected out of them was the ability to judge conflicting workloads and prioritize them yourself.

    I'm not saying that doing that -- even successfully -- doesn't result in complaints, or that people aren't legitimately given more work than they have the bandwidth to get done and that managers won't refuse to acknowledge this -- aka, manage poorly.

    But these days, asking what your number 1 priority is almost always results in "they all are number 1" and nobody cares to fix this.
     

  16. Re:Overthinking a simple problem by PrimaryConsult · · Score: 2

    +1000 on kill voicemail. Our group unofficially does not answer voicemail - it started with just me, and soon spread to everyone - our voicemail lights are always on, and after 30 messages queue up the system sends emails nagging us about it. Every month or so we delete them all and have a day or two where we're not sure if our phones are working (since that is normally the only time the VM light is off). Some are so put off by the change that they leave one in the box to keep it lit.

    If it's important, send an email. If it's super important, create a ticket - it gets all the right visibility and spams management when it's ignored. If it's a dodgy request they don't want a record of (i.e. help I fucked this up, divine miracle required), send a skype message (still logged but buries the needle in a bigger haystack).

  17. I handle interruptions by by fyngyrz · · Score: 2

    I handle interruptions by petting whichever cats show up or giving the lady of the house the hugs she deserves when she ghosts by (one reason why she deserves them is that she carefully doesn't try to engage my attention verbally when I'm working.) Neither of which minor activities derail my train of thought. They just make my environment that much more conducive to doing what I am trying to do. Because, you know, happy.

    Other than that, when I work, the social media is shut down, the phone is in "airplane mode", and the doorbell doesn't get answered. I am, as you might suspect, very productive under these conditions. I keep coding hours 100% separated from other types of work hours, such as jawing with those who have contracted my services, etc.

    There is nothing better than working in your own lab, in your own home, with full control over the chaos that wants to intrude, choosing your own working hours, managing noise levels, doing breaks and feedings as desired instead of as permitted, etc. Nothing. Nothing comes even close.

    --
    I've fallen off your lawn, and I can't get up.
  18. Re:Overthinking a simple problem by DutchSter · · Score: 2

    while they could simply give me a red light controlled by a switch. Red=do not disturb...

    A few years ago we used to have these little do not disturb flags to put on top of our cube when we were really busy. Naturally the top performers tended to be very busy and were often showing DND. Those with less things to do, or less productive almost never used it.

    Management noticed, of course. But they didn't notice the right things. Instead of wondering why their average performers always had time to BS and their top performers didn't, they started letting it be known that having your DND flag up too much was kind of anti-social. Using it "too much" (not defined) was discouraged. Within three months the whole idea went kaput. Most of the top performers eventually moved on to other opportunities.

    I'm not a programmer anymore but the best thing I ever did was start working remotely full time. If you're not physically there people tend to only bother you via IM/email when it's real work-related stuff. I think that's because it takes effort and it is logged (the joys of working in litigation), whereas plopping yourself in someone else's cube when you're out roaming the halls anyway does not. Thankfully no millennial knows how to use a telephone so I happily answer that when it rings.

  19. Re:Investment opportunities by mwvdlee · · Score: 2

    Green LED's indicate my readyness to be interrupted; I have no need for them.

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  20. Re:By shooting the person summarily. by igny · · Score: 2

    try { DoWork(); } catch(InterruptedException) { DoWhine(); }

    --
    In theory there is no difference between theory and practice. In practice there is. - Yogi Berra