Multitasking Yourself Away From Efficiency
by Thomas M. Cagley Jr

(Originally posted on the Software Process and Measurement Cast 57 – www.spamcast.net)


Increasing efficiency has been the clarion call for organizations in earnest for at least the past six months. Efficiency has a simple technical definition, the ratio work done to the energy required to do that work. The definition is similar to that of productivity however in normal usage efficiency is held to relate to how productive a machine or process is. Taking the more general usage it easy to see why efficiency is important. In the software development world efficiency and its relative productivity are rarely managed rather the discussion tends to be on cost. Cost and efficiency are different attributes, related but they are not the same.

Increasing the level of efficiency in a person, process or organization will require some kind of change. You do not get a different result by doing the same thing over and over. Using the manufacturing industry as a reference we know that in order to change efficiency, we need to change the process that transforms an input into a product or the environment the transformation occurs inside or the input such as people or raw materials or some combination of these areas.

While it might be too obvious for most people listening to the Software Process and Measurement Cast, the first place to look when you want to improve efficiency is the process being used. Removing process deadwood, simplifying the flow, adding tools and automation whether through frameworks like CMMI or agile or through techniques like Six Sigma, lean or others is a philosophy choice that needs to fit organizational culture. Unfortunately process changes are not instantaneous which is causing many organizations to jump over the process improvement step and go right to the cutting people as an option.

The thought process around the cutting people option goes something like this:

We will cut some percentage of people because we have gotten ‘fat’. When we cut people those that are left will pick of the slack through working a little harder and by multitasking. They should just be happy to have jobs. Tasks that we just can’t cover anymore probably didn’t need to be done anyway. I have thoughts on this last sentence that I will share in a few weeks.

Multitasking is in general thought of doing more than one thing at a time. The silver bullet of the 21st Century. Relying on multitasking steals efficiency. Unfortunately multitasking is a common tool we are being asked to use in order to manage the world around us. According to René Marois, a neuroscientist and director of the Human Information Processing Laboratory at Vanderbilt University, “trying to do two things at once can be disadvantageous.” Now I will readily admit that I have not been able to put aside multitasking all of the time. Humans do most of their multitasking in an unconscious mode (breathing, pumping blood and other mostly autonomic tasks). I have tested conscious multitasking personally trying to text or talk on the cell phone while driving; no one has died, yet although my wife has threatened divorce. Unfortunately humans aren’t good at multitasking! Humans do not really multitask, what we do typically is fast switch shuffling between tasks quickly focusing on each slice for a brief period of time. It is during the switch and reorientation that we loose efficiency. In an article published in the “The Journal of Experimental Psychology: Human Perception and Performance” reported in a 2001 a study by Joshua Rubinstein, David Meyer, and Jeffrey Evans on the brain’s executive control process found that “at best, a person needs to be aware that multitasking causes inefficiency in brain function.”

Focus is required for efficiency. Doing one thing at a time correctly has an appeal both in terms of logic and science. We are faced with the issue that most workplace cultures do not seem to support focus with action. As evidence I suggest you count the number of interrupters in your environment (cell phones, email, twitter, instant messengers and pagers to name a few). Our work culture is sending a strong message that you are not expected to be cut off from the information flow at any time. The ability to deal with continual partial attention is a career success factor in many instances. Quite time for concentration tends to happen outside of core hours or at home when we are tired. The question we must ask is when the does the cost of interruptions and multitasking ever outweigh the benefit of focus? How can we construct processes or environments that allow connection and collaboration to happen while providing an atmosphere where focus is not the odd man out of the equation?

The Fine Line
Thomas M. Cagley Jr.

All organizations try to walk the fine line between what is perceived as productive activities (deliver product) and activities that are perceived as overhead. The line is razor thin and horribly difficult to recognize. Part of the reason that it is difficult to recognize is that no one actively pursues adding overhead to a project or process just for the sake of adding overhead. Overhead is added to meet specific perceived needs. Needs like time accounting, billing, status or the knowledge of when work will be delivered and how much it will cost. All of these needs are rational. The problem starts when you pile these types of information needs up. Each requirement draws time from somewhere such as from the time needed to create the output of a project or process or that other part of the day when you are not supposed to be working.

Once implemented the steps needed to collect the data, evaluate or monitor the process rarely go away at least until the process implodes and it is re-engineered. True re-engineering is rare because it is politically difficult and takes time away from the task at hand. The answer? Bite the bullet and re-engineer more often? Just say no and ignore the information need? Buy a tool? The envelope please . . . I would suggest a simple process.

1. Establish a philosophy that that has two primary tenants:
a. All process changes that can’t be directly tied to delivering the expressed
output of the project or process must be viewed as suspect (not bad or evil
just suspect).
b. All processes must be changed as organizational needs and environments
change (no process is ever perfect).
2. Review every suspect step or activity to ensure it that it is really needed not
just nice to have and whether the data might be available elsewhere.
3. Repeat the mantra “simple, simpler, simplest”. Anything that needs to be added
or changed in a process must be implemented in the simplest form possible that
fits the requirement.
4. When adding tools consider human usability not just the sales brochure.
Test to see whether the tool works well in the technical and cultural environment.
Investigate whether any suggested tool can be linked to other tools used in the
environment. Finally determine whether automating the work doesn’t add different
kinds of work somewhere else that might cancel the benefit.
5. Periodically re-engineer the process and any supporting business processes.
Remember your mantra. Consider starting with a blank page (zero based
process engineering) every other time you re-engineer the process.

A simple but powerful process.

Playing ostrich and ignoring information needs is rarely a good idea in the long run but neither is making indiscriminate additions to any process. Challenge all needs that add steps to your process to ensure they actually solve the specific problem. Once convinced (be rational and not obstinate) use the process described above to ensure an effective path is chosen. The line between required overhead and productive work is a fine line, step back occasionally and review which side of the line you’re walking on.