Slashdot Mirror


Multitasking Harmful To Productivity

Greyfox writes: "According to a CNN article, a person who is multitasking several things takes a hit on his productivity. Oddly enough, it reads almost exactly like a description of the problem with multitasking on computers; context switches cost, especially if you have to swap a lot of crap out in order to fit the new process into memory. So basically, an employee who can stay focussed on one thing for long periods of time is going to have higher productivity than one who has to handle constant interrupts. Now if I could get my manager to buy into that ..."

30 of 333 comments (clear)

  1. Twice the results? by wiredog · · Score: 4, Funny

    You pee twice as much while brushing your teeth? Better see a doctor about that.

  2. Re:I guess it depends on.. by Phroggy · · Score: 3, Interesting

    Hmm, that's interesting. For me, I can't use a form of languages on two tracks simultaneously. I can't talk and listen, or talk and write, or listen and write, or read and listen, or read and talk (unless I'm reading aloud) at the same time. I can jump back and forth between two tracks with no problem, and a little bit of overlap is fine, but I can't maintain two tracks of language usage for more than a few seconds.

    Doing tech support, this means I can't listen to a customer while taking notes - I have to wait for a pause in the conversation before I can take my notes (or put them on hold, or whatever). If I try to take notes, I can only get a few seconds before I can no longer hear the customer - needless to say, this is rather embarassing, so I try not to do it. Fortunately my boss was somewhat understanding, so I never got in serious trouble for having a low call volume.

    I wonder if I have a milder version of what you describe? I've never talked to a doctor about it; this is all just from my own personal observation of myself.

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  3. Re:Don't tell that to cavalry pilots by markmoss · · Score: 3, Interesting
    And sometimes pilots will fly smack into a mountain, in daylight and in clear air, because they were too busy with all those instruments and radios to look out the windscreen. Nobody's fault but the system designers. 8-(

    However, most modern piloting tasks don't require deep thinking. Try doing all that, or even half of that, plus taking a star sight and working out your position with sliderule and nav tables... That's why large airplanes used to have a four man flight crew -- two to fly, one to watch the multiple engines, and one to navigate -- and small airplanes didn't use to have that many distractions. E.g., Lindbergh could center the controls and take a star sight without worrying about running into anything over the Atlantic ocean.

  4. Don't tell that to cavalry pilots by HerrGlock · · Score: 3, Funny

    Four radios, talking to six people, a co-pilot, maps, weapons systems, mast mounted sight, scanning for other aircraft, while on a screenline looking for bad guys, setting up relief on station and tracking the movements of everybody.

    Multi-tasking? What's that?

    DanH

    --
    Cav Pilot's Reference Page
    UNIX - Not just for Vestal Virgins anymore
  5. Re:I multitask for a reason by Zico · · Score: 3, Funny

    You got that right. I've got 18 freakin' browser windows open right now, forget about all the other stuff that's open, too. I'm impatient, and some of us can actually handle multitasking, thank you. Sure, there are some times when it slows me down, like I won't read a book while listening to something like the Phil Hendrie Show because that my brain doesn't handle very well. Then again, knowing the simps that work at CNN, it wouldn't suprise me in the least if they have one browser window open at a time, spending 50% of their time just watching that little blue ball spin 'round and 'round...

  6. Re:Multitasking is ... by csbruce · · Score: 5, Funny

    Trying to think of something profound, while going for First Post.

    That'd be real-time multitasking.

  7. Re:Multitasking has its place.... by markmoss · · Score: 3, Interesting
    The lost time usually isn't from when you _choose_ to switch tasks, it's from the interrupts, except when you are thrashing the interrupt stack in order to avoid doing real work... 8-)

    There some very good parallels between brain work and computing in the 60's. A good CPU would often overrun the IO devices, and since the CPU cost half a million they didn't like wait cycles. So when it had to wait for IO, it would switch to another task, until that had to wait also, etc. The analogy is to you working on one job until you find that you need information from someone else to proceed, writing e-mail to him, then switch to another job until the reply comes back. This (task switching when on hold) improves productivity. On the other hand, when you get a phone call about some project you aren't even working on today, or have to stop coding to go to a meeting about parking spaces, you lose productivity. Likewise, interrupt-driven task switching tends to reduce the number of jobs finished per hour, and only became common when the CPU's became fast and cheap enough that you could afford to waste cycles.

    Since the human brain isn't getting any faster, any situation where you are frequently interrupted is going to reduce the amount or quality of work completed. Note also that there are major and minor context switches, and the cost difference is much larger than the difference between switching processes and threads. Switching to a different part of the same project requires re-loading "registers" (short term memory), but the major context of the project stays the same. Switching to something I put away last week will probably require skimming through some of the documents to remember where I left off and to refresh my memory of the overall structure.

  8. Re:Task Loading by Phroggy · · Score: 3, Insightful

    That basic concept also applies to driving a car. With new drivers, many of the basic decisions are handled consciously - and there are a lot of them. As you gain experience, your subconscious can take over a lot of the work, so you no longer have to concentrate on so many different things.

    New driver:
    OK, the light in front of us is turning red, so we have to stop. We need to shift into first, so first we step on the clutch, shift, release the clutch. Now we also need to step on the brake, slowly, paying close attention to where the car in front of us is so we get reasonably close without hitting it. OK, there, we're stopped, I can relax now.

    Experienced driver:
    Damn, I knew we should have taken the freeway.

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  9. This result is over 100 years old! by possible · · Score: 5, Interesting
    Henry James, in his Principles of Psychology (1890 or thereabouts) described the mind's multitasking and task-switching in terms that modern-day computer folks will find quite familiar.

    There's a running joe that James' century old work represents basically everything cognitive scientists know today. In other words, not much new progress in the last 100 years. :) Anyways, to quote from James' book, chapter 11 (emphasis mine):

    [p. 409] If, then, by the original question, how many ideas or things can we attend to at once, be meant how many entirely disconnected systems or processes of conception can go on simultaneously, the answer is, not easily more than one, unless the processes are very habitual; but then two, or even three, without very much oscillation of the attention. Where, however, the processes are less automatic, as in the story of Julius Caesar dictating four letters whilst he writes a fifth,[9] there must be a rapid oscillation of the mind from one to the next, and no consequent gain of time. Within any one of the systems the parts may be numberless, but we attend to them collectively when we conceive the whole which they form.

    When the things to be attended to are small sensations, and when the effort is to be exact in noting them, it is found that attention to one interferes a good deal with the perception of the other. A good deal of fine work has been done in this field, of which I must give some account.

    It has long been noticed, when expectant attention is concentrated upon one of two sensations, that the other one is apt to be displaced from consciousness for a moment and to appear subsequent; although in reality the two may have been contemporaneous events...

    Chad Loder
    Rapid 7, Inc.
    The next generation of network security products

  10. Costs by Lemmy+Caution · · Score: 3, Insightful
    The question is, however, whether the difference in productivity between a mono-tasker and a multi-tasker is greater than the cost of hiring additional mono-taskers to fill in the void created by the dedication of staff to one-and-just-one function. And whether the perspective gained by having people work on a variety of tasks - giving them more of a birds-eye view of the organization's needs and goals - has any value that might be lost by creating an organization of super-focused people.

    I suspect that, except for the staff geniuses and the people focused on make-or-break tasks, the answer is often that the productivity costs of multitasking is offset by its benefits.

  11. The reality is by q-soe · · Score: 3, Interesting

    Some thoughts from my workplace

    I find myself more and more multitasking (and now its not just because i have to use win2k at work - but that adds to it) the fact is that we are caught by a couple of things

    1. Expectations of Users - The average user has come to expect support and help in a much quciker time frame which couples with their increasing knowledge and skills (note this in general) to produce a class of user who thinks every problem is major and they then try to fix it them selves therefore ensuring it IS a major problem.

    2. complexity of systems - this goes hand in handwith the above - eveyr day systems grow more and more complex - we are in the process of SAP implementation and this is a killer on the back on WIN2k, Intranet Payroll and HR and Intranet helpdesk loggin - the number of passwords grow and there is no easy way to resolve the issue and maintain security - that means the system become more complex on a daily basis and the struggle for support staff and users to keep up with the required skills and knowledge (paid training is an impossible joke in most companies - it does not happen)

    3. Time and Resources - time is a valuable concept - the amount of time in a day is finite at 24 hours and you can only work so much of it - yet i spend a lot of my time waiting for things to load and dealing with FIX THIS NOW requests for low priority issues whilst trying to fix the major issues i have - it takes longer to tell them to go away than the fix would but you have to maintain a focus. Staffing resources have also decreased - in my role its down to 1 staff member for every 100 staff and sometimes less - i have a state to run with approx 200 users and there is me and one part time partly skilled staff member who gets sick 2 days a week, so you can imagine that i dont have time to relax - 18 hour days are standard and i have done more than one 20 hour.

    4. Money - the pressure of technology means that companies have to stay on top of things to survive - that means upgrades, new systems, software etc. This comes at a huge cost - SAP cost us AU$20 Million and thats only year 1 - dont forget as IT we now have to look after Phones, Video Conferencing, TV's, Boardrooms, Photocopiers, Fax Machine, Building Management Systems, Security Systems, etc etc - all this with less staff than before (2 years ago to do less i had 3 staff full time working flat out) - no money = no staff (SAP again)

    SO whats the multitasking point ?

    Yes staff who multitask are probably less efficient but then again hiring adequate staff to fill the roles in an organisation would mean less multi tasking and more efficiency - simple maths really.

    I multitask because i have to - the headaches, backachec, half done jobs and 10000 email messages i cold do without - im efficient as hell tho - i have to be to survive and stay sane.

    No if you will excuse me the 5 minutes i took to write this whilst waiting for a server to reboot is up and i have to go fix SQL - god i wish i had another pair of hands as well...

    --
    I refuse to argue with Anonymous Cowards - if you want a discussion get an account....
  12. it all depends on duration of tasks also by sidster · · Score: 3, Insightful
    What i mean is if a person is trying to multi-task 5 different tasks during the 8 hour work-day then this might be true.

    Personally I do a lot of multi-tasking as in i'm involved in at least 2 (ideally 3) different coding tasks. I actually find myself to be very productive that way.

    This was actually something i recently realized. One of the projects i am involved with was put on hold due to configuration problems with new hardware that was installed, leaving me to work on a single project until the hardware issue is solved.

    I find myself getting extremely bored and tired of this single project after about 5 hours or so. I end up not being able to concentrate as well and my motivation level drops considerably compared with its level at the start of the day.

    Anyone else notice anything similar?

    --
    --sidster
    Play lotto? Try http://www.alottofun.com/
  13. It depends totally on the type of work. by Bowie+J.+Poag · · Score: 3, Interesting



    Tell a stock trader that he's going to be more "productive" by simply walking over to the gentleman he wishes to conduct a transaction with, and speaking quietly versus standing elbow deep in a pit with thousands of other guys screaming at the top of his lungs and flinging gestures at other traders.

    It all comes down to the work environment. For some things, like engineering, QA, R&D, a quiet distraction-free environment is ideal. For other things, where transaction speed matters more than quality of execution, multitasking is the only way to go.

    --
    Bowie J. Poag

  14. Sad but true by Robotech_Master · · Score: 3, Funny
    I find myself trying to multitask a lot of the time during my free time...and usually what I'm trying to do suffers for it. Roleplay online, read net news, read Slashdot, read email, read net comics, watch a DVD movie...I guess I'm easily distracted by things.

    Oooh! Bright shiny object, sorry gotta go!

    --
    Editor Emeritus and Senior Writer, TeleRead.org
  15. No surprise there.... by neoshmeng · · Score: 3, Insightful

    Well, duh.

    As if computers have made people any more efficient in the first place. How often do I work on a paper for school only to check my email, run my TV Card in a window or listen to MP3's at the same time. Computers are more for entertainment these days than actual productivity. Although they can do that too....

  16. XP and pair programming by phr1 · · Score: 5, Insightful
    Reduction of multitasking may be one of the big wins of pair programming in XP. Unless you're very absorbed in the task, just about everyone gets distracted while programming, even when there aren't random interrupts (phone calls etc.) coming in. The win of pair programming may have little to do with splitting the task into abstract and concrete components or anything like that. A big part may simply be that having another person next to you absorbed in the exact same task and working closely with you will keep you focused better.

    I haven't done any formal XP projects but I've certainly had the experience of developing code alongside another person, and found it works very well.

    1. Re:XP and pair programming by Kalak451 · · Score: 5, Interesting

      Where I work we don't have any specific rules about this kind of thing so things happen both ways, but on the one project where one other guy and I are working side by side on a piece of code, our productivity jumps thru the roof, and not only do we get MUCH more done, the code we produce comes back from QA with almost none(or in several cases Zero) defects. I think alot of it has to do with us catching each others dumb mistakes, and i don't just mean missing ';' or other things that compilers will check (In fact we had to teach our selves to igonor such problems when the other was typing becuase by the end of the day we woudl want to kill each other) We will catch simple logic errors and flawed assumptions as the come up because each of us already has an idea of what the code will look like, and if the other does something completly strange we can discuss it and figure out if its the right thing to do, all before its ever finished. There is nothing worse than digging thru 5k lines of code looking for weird logic erros.

  17. Multitasking for programmers by DevTopics · · Score: 5, Interesting

    A discussion of "multitasking for programmers" and why it hurts is at Distraction: the one big obstacle. This is written for programmers, but it is true for everbyody who works with knowledge.

    --
    You found a sword: +4 damage, +5 moderator points
  18. that reminds me of the days in IBM by jsse · · Score: 3, Interesting

    We didn't have computerized timesheet system at that time(I got to write one later) because CPU time was costy. We had given a stack of palm-size timesheet cards, each slot is a 15-minute interval.(I think newer IBMers could find this timecards in storage room, they've printed quite a lot of them)

    It wasn't so bad when one day our new manager introducing 'time-slicing' time-management technique, that we had to fill in different tasks in each time slot, to prove that you've 'used your time efficiently'.

    Time-slicing was a new buzzwords that days. Obviously he didn't quite catch the meaning of it.

    Clueless managers can be found everywhere.

  19. New government studies show: by Kierthos · · Score: 5, Funny
    • Sky indeed blue, research study concludes.
    --
    Mr. Hu is not a ninja.
  20. Re:I guess it depends on.. by dadragon · · Score: 5, Interesting
    Who can't spit out the name of your ISPs mail server while some dolt fills on the Email wizard in Outlook Express while they do something else?

    I can't. I have CAPD(Central Audiotory Processing Disorder). I could spit it out, if I knew what he was asking, but that's what I can't do, make sense of what I hear. If I'm doing ANYTHING else, I don't understand what somebody is saying to me, be it hitting something with a hammer, reading a book, coding, looking at a wall, if my attention is even remotely used for something else, I can't hear people.

    That includes thinking of what to say when they're done talking, or if they get me thinking of something else. It's really annoying, actually. That's why I can't do the phone-monkey thing.

    It does have its advantages, though. I'm not easily interrupted when doing work, I don't hear people talking to me when I don't want to, it's not ignoring, it's involentary, but convenient at times. I have not trouble visiting my own little world.

    --
    God save our Queen, and Heaven bless The Maple Leaf Forever!
  21. Home working by TarpaKungs · · Score: 3, Insightful
    Guess I'm lucky - but...
    When I'm going insane with soem development I simply announce that I'll be at home till it's fixed. This works because:
    1. Because my boss understands the *real* issue - our systems working is higher priority that company policies/management fads etc.
    2. I'm reasonable - I wouldn't do it if there's no other staff around or there is some pressing reason I *should* be in.
    3. I already have unmetered net and enough equipment at home to do my job.

    This works for me. I can do helpdesk duties because I'm not trying to do anything long term most of the time. Just trying help users. But when I'm programming any interrupt withing a 3-4 hour time span destroys all my concentration.

    Curiously - a great many comapnies in the UK don't encourage home working. They don't have a "policy" in place(!).

    Come on UK management: why are so many people taking up expensive office space, polluting the planet, wasting their lives on the train, in the car or bus and stressing themselves to death when they *could* be at home 60+% of the time and actually do *more* work?

    --
    Why can't women be like Hedy Lamarr - beautiful, talented and inventors of frequency-hopping spread-spectrum techn
  22. So There I Was... by asackett · · Score: 5, Insightful
    Interviewing for a gig with a division of H-P. The interviewing team all knew me, they all knew my work, that's why they were interviewing me.

    One new age, diversity celebrating, politically correct company chick asked me, from her list of prepared questions, "Do you believe you multitask well?" So, I asked her, "Can you define multitask, so I can be sure I'm answering the question you want answered?"

    "Doing more than one job at a time", she replied, "like debugging one minute, explaining an important process change to a coworker the next, and then going back to debugging." I thought on this for a moment, wondering if it was a trick question, an honest question, or perhaps an honest question that through the acts of self deception and corporate mind-fucking had become a trick question. So I figured I'd just be honest, and let the chips fall where they may. "No, I do not believe that I multitask well in environments such as this, and in fact I do not believe that anyone multitasks well in an environment such as this. When I worked at Burger King, as a teenager, I could make fries and fill drinks at the same time, but those were not mentally challenging tasks."

    "I happen to think that I multitask very well, and don't find that it's all that difficult", she said to me. And it was at that very moment that I realized that I was not meant to work in the corporate environment. Which is fortunate, because I did not get that job, and I'm still self-employed. The PC company chick? She proved that she multitasked well by volunteering for every function that would keep her in meetings, all day every day, and for avoiding work so skillfully, but being seen rushing past on her way from one conference room to the next, she was promoted and now runs the department.

    My point? There is a fallacy floating around in corporate America, that in order to produce more output with less time and fewer resources, we must all fill many roles. Instead of focusing on doing one job very, very well, we are supposed to compensate for the fact that jobs have been eliminated, but their roles have not. So we are expected to "multitask" -- and the harder we're expected to swap, the lower the work output, the lower the quality of it. We are never allowed to operate at our full potential because we cannot achieve the mental state necessary to do Great Work. We find ourselves staring at the same problem for half the day, only to spot it within 20 minutes first thing the next morning, before our minds are cluttered up with corporate crap.

    Productivity and quality will not improve no matter how many policy changes and process controls we are subjected to. What has to change is the production budget has to rise in direct proportion to shareholder dividend reductions. We are not going to cure anorexia by starving it to death!

    Being self employed, I no longer have to deal with the down-sized company (or being down-sized out of a job) and can focus on my work as long as the telephone doesn't ring. It always seems to be that client with the hairiest project who calls right at that moment when the feeling of an inspiration forming is building... and I let my wife answer the call and take a message. Gotta love it.

    --

    Warning: This signature may offend some viewers.

  23. I multitask for a reason by Muggins+the+Mad · · Score: 4, Insightful


    I often have half a dozen (or more) things going on at once, switching between screens, applications,
    and even computers regularly.

    Why?

    Because I'm *waiting* for things to happen. Waiting for that 3 minute web page to load,
    waiting for that 10 minute compile, waiting for a reply to an ICQ, or whatever.

    If I couldn't multitask, I'd be sitting dumbly staring at the screen waiting for whatever task I'm doing to
    become ready for my input again.

    Sure, a lot of time/energy goes in the context switch. But it's time that's wasted *anyway*.

    - Muggins

    1. Re:I multitask for a reason by leereyno · · Score: 4, Informative

      What you're doing is an example of cooperative multitasking. You choose when you do the context switch and which task you pay attention to next.

      The problems start when you're forced to do pre-emptive multitasking. This is what happens when you're busy trying to do one thing while the phone is constantly ringing, people are coming and asking you questions, or any number of other distractions are vieing for your attention. It is at this point that productivity plummits because you're spending 75% of your time dealing with bullshit. I once worked as a tech at Fry's Electronics and that is the exact kind of thing I had to deal with. Here I was supposed to be fixing customer's computers but I wasn't able to do that because Fry's wouldn't hire enough people to handle things like customers at the counter, processing returns, etc. etc. I quit that job and I hope I never have another one like it.

      Lee

      --
      Muslim community leaders warn of backlash from tomorrow morning's terrorist attack.
    2. Re:I multitask for a reason by s390 · · Score: 5, Interesting
      Because I'm *waiting* for things to happen. Waiting for that 3 minute web page to load, waiting for that 10 minute compile, waiting for a reply to an ICQ, or whatever.

      Right on. However, the researchers here seem to have a rather simplistic, one-dimensional view of multitasking.

      (OK, sound research starts by validating a few simple concepts, then building more complex structures later. But seriously, eight years of research, for merely this? I guess they've got to keep some ideas in their back pockets, ready for a next round of grants.)

      There are two ways multitasking can happen: chosen swapout of tasks (you mention waiting for something to finish, but it might be waiting for anything - email reply, phone callback, etc.), and imposed interruptions (phone, instant-message, chatty boss/coworker, and so on). Swapouts are like enqueue-wait swaps on a mainframe - you know it's going to be awhile before you can resume that task, so you turn to something else. Interruptions are like, well... I/O interrupts - they demand immediate attention, whether or not its convenient at the moment. Swapouts tend to _improve_ efficiency generally, and so does minimal servicing of trivial I/O interrupts. Continuing the mainframe analogy, a first-level I/O interrupt handler merely fills a buffer and posts an ACK, then exits; these don't seriously degrade scheduling. What hurts productivity are interrupts that are forced as untimely swapouts of important, hard tasks.

      A long time ago, I did some applications programming in COBOL for a S&L. (Yeah, I know COBOL sucks, but it paid the mortgage and I also taught myself IBM S/360 ASM during the same period.) Anyway, I was easily the most productive programmer in the shop, because I always had at least three and sometimes half a dozen projects ongoing at once. This was back when you were lucky to get two compilations of any one program per day. So, I'd code in one program, submit it for compile, and go on to coding in another program. It was quite effective, swapping tasks that way. Of course, it also helped that the programs were usually related.

      As with many things, the real issue here is empowerment. Workers who can choose when to swap out tasks and turn to other ones will always be more productive (and happier) than those who are constantly interrupt-driven and never get to take anything to a "stopping point." This seems obvious: it's why you don't have the Help Desk do any network engineering or complex programming.

  24. Re:I guess it depends on.. by jcarley · · Score: 5, Funny

    I think I have the same problem although it sounds less acute. When my wife talks to me I can't hear her. The disorder seems to be hereditary because my kids can't seem to watch tv and hear their parents either...

  25. Re:Common knowledge? by hillct · · Score: 4, Insightful

    It should be common knowlege, except management doesn't often seem to make the connection between reality and most management books. There's a great book The One Minute Manager Meets the Monkey all about deligating tasks to reduce the mmanager's stress level and allow him to focus. Unfortunately, This book alocates vary little time to task assignment across staff, such that your staff can focus on a limited number of tasks in an organized sequence. This is unfortunate since the productivity of a manager doesn't often ralate as directly as we'd all like to believe; to the productivity of his employees.

    --CTH

    --

    --Got Lists? | Top 95 Star Wars Line
  26. Multitasking is ... by Anonymous Coward · · Score: 5, Funny

    Trying to think of something profound, while going for First Post.

  27. Re:Multitasking Efficiency Dependent on Sex? by keithdowsett · · Score: 3, Insightful

    Women are great at multi-tasking. They can iron, watch tv, mind the kids and still find time to tell you all the things you have done wrong in the last two weeks.