Multitasking Considered Harmful
Here’s your challenge for the day. Read this Seattle Times Magazine article from start to finish without trying to multitask. Even though the article puts forth cogent arguments for why multitasking (especially with intellectual tasks like reading) by humans is usually inefficient, I couldn’t stop myself. First, I had to check on the progress of some code that I was compiling. Then I had to see if I had received any urgent email since I had last checked five minutes ago. Finally, I caught myself tabbing back to another half-read article from that morning.
How many books are you in the middle of reading? For me, the answer is eight, and I’m not counting the programming or other technical books that I am constantly grazing through. If I counted those books, the number would be about fifteen. Why do I think this is a good idea? Why am I surprised that I rarely finish a book (though I actually did finish two in the last month)?
The friend at work who forwarded the Seattle Times article to me was interrupted five times by people while he was trying to read it. I was responsible for at least one of those interruptions. Sorry, Eric.
Mihaly Csikszentmihalyi (challenge #2 – say his full name fast five times in a row) wrote an influential book in 1991 entitled Flow: The Psychology of Optimal Experience about how achieving a “flow” state is not just highly productive, but also very emotionally and intellectually pleasing. One of the many books on my bookshelf that I haven’t started to multitask on yet is The Evolving Self, a sequel to Flow. In The Evolving Self, Csikszentmihalyi proposes that we should carefully examine our genetically driven feelings and behaviors, as what was key to our successful evolution hundred years ago may by counter-productive to our pursuit of happiness today.
Fortunately for the recidivist multitaskers among us, some boffins at Oregon State are working on a software system called TaskTracer. TaskTracer attempts to track what software applications and documents you are working with as part of each of the tasks in your virtual multitasking ToComplete list. When you get interrupted, TaskTracer alledgedly informs you of the previous state of the task that you are switching to and what you need to do next on that task. A key factor, of course, is understanding the nature of the task.
Naively, this seems to me to be a case of a software engineer who understands how CPUs and operating systems work with their program counters, registers, threads, stack frames, etc., and wants to extend that to how a person works. Of course, a person doesn’t organize her tasks, processes, and flows as cleanly as a CPU running several applications, because she doesn’t have to. Then again, TaskTracer doesn’t have to be perfect in order to provide a lot of value. I think there is a big risk, though, that it might encourage the easily susceptible among us (Google Translate translates that last phrase to mean “me”) to crank our multitasking up to eleven, though.
