Comments on: Multitasking is Conflict Avoidance

By: Ericlodi

Ericlodi — Sun, 10 Jun 2007 19:28:55 +0000

Multitasking is cetainly killing efficiency… But in our world it is more and more difficult to avoid it. Personal organization methods like GTD allow to limit multitasking impact at individual level by improving focus and reducing switching costs: the tasks are split in elementary actions that are focused on, one at a time, when context allows.
I develop this idea in “GTD vs multitasking”
http://web.mac.com/ericlodi/iWeb/Orgameth/
Happy GTD and stay away from multitasking!

By: Mary

Mary — Mon, 26 Mar 2007 23:38:45 +0000

I get a kick out of this multi-tasking thing…People use the word to connote highly talented…in the meantime most women say they are good at it and men aren’t…I have yet to see a mult-tasker accomplish great things…Usually people who excel at the highest level of greatness are very focused individuals

By: F. Schophuizen

F. Schophuizen — Sun, 25 Mar 2007 13:54:03 +0000

If you do 2 tasks of 40 hours work simultaneously, you need 2 weeks to finish.
If you do them sequencially, one task finishes after 1 week and the other after 2 weeks.
So, by ignoring priorities, all work will be as late as the lowest priority. Indeed, multitasking is not an economic choice.

By: James Ward

James Ward — Thu, 22 Mar 2007 22:51:49 +0000

For those of you who have commented above, I suggest you study the teachings of Eli Goldratt, notably “The Goal” and the Theory of Constraints. Is it the mission of the organization to get projects completed as rapidly and efficiently as possible or to fully utilize every hour of every staff member? The big problem with assigning a person who is only needed 50% of the time on one project to a second (or third or fourth) project is that you can’t know exactly when you will need this 50% involvement and what other tasks or personnel may be dependent on the efforts of that person. For those of us who have seen this dynamic in action, there is no question about the deleterious effects of multi-tasking. Having fill-in work for idle time is not the same thing.
I would love to receive a detailed description of the Confetti Factory exercise from Chris Frame.

By: Adam Jacobson

Adam Jacobson — Thu, 22 Mar 2007 02:39:33 +0000

I think there are two questiona to ask :
1) what is a reasonable number of project for a given group to be working on at the same time”.
2) How much time can you safely allocate a resource to any project (slack)?
To me, if a resource is only needed 50% of the time on a given project, they shouldn’t be necessarily idle the other 2.5 days of the week.
I think what happens is that after priorities are nominally set (and I am absolutely in the middle of this right now), other “priorities” intrude. so, for example, “Rich” is assigned to my project 2 days a week and 3 days a week to John’s project. This is fine. Then, it turns out that Rich is .5 days on me, .5 days on John and 4 days on three other things that “came up”.
As for question 2, we need to acknowledge that we can’t fill every whole. Is it reasonable to budget people at more than 80% time for anything? How much slack do we need in the system?

By: Chet Frame

Chet Frame — Mon, 19 Mar 2007 21:58:13 +0000

I have been working with several clients where multitasking had taken on a new level. I did a brief exercise with several teams to show them the harm. The exercise is the Confetti Factory and it takes about a half hour. It helps people understand the time wasting and it lead one client to change an established policy. People need work to do, but they need an orderly process to get more of it done in a set time.

By: Chip Patton

Chip Patton — Wed, 14 Mar 2007 18:01:41 +0000

Just because a tool is being used badly, even by the majority of people, is not sufficient reason to condemn the tool. This sounds like a classic case of misuse.
Sticking with the computer analogy, multitasking is a way to use CPU cycles that would otherwise be wasted due to a block on an external resource. Similarly there are plenty of legitimate impediments to project progress at the individual level and having something else to do is just plain efficient; twiddling of thumbs waiting for resource availability is not.
Granted that we need to pace ourselves and not bounce from one task to the next, making little progress on any of them — there’s another computer term for that: “thrashing”. A well-functioning system tunes these into proper proportion, it doesn’t dismiss multi-tasking as a bad idea.