<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Multi-tasking is bad - Again</title>
	<atom:link href="http://blog.synaptus.com/2007/03/28/multi-tasking-is-bad-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.synaptus.com/2007/03/28/multi-tasking-is-bad-again/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Wed, 10 Mar 2010 11:41:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Dennis Stevens</title>
		<link>http://blog.synaptus.com/2007/03/28/multi-tasking-is-bad-again/#comment-14</link>
		<dc:creator>Dennis Stevens</dc:creator>
		<pubDate>Wed, 04 Apr 2007 14:40:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.synaptus.com/?p=33#comment-14</guid>
		<description>Steve,

You are right. The appropriate systems must be in place to support the prioritization of efforts. What I see a vicious cycle of expediting new high priority work fueled by long durations and unpredictable results caused by multi-tasking in the first place.

Without the appropriate systems in place to prioritize, we work on many tasks at the same time. We stay busy by switching but do not deliver results rapidly. This extends how long any one deliverable will take and makes it difficult to predict completion times.

Extensive duration length and uncertainty leads to management prioritizing “important” work into the existing work in progress, exacerbating the problems. Moving deliverables through the work stream intact reduces the time from start to finish and increases predictability.

The power of short time to delivery and predictable results is that management will queue the next most important thing, rather that expedite over work in process.

Dennis
</description>
		<content:encoded><![CDATA[<p>Steve,</p>
<p>You are right. The appropriate systems must be in place to support the prioritization of efforts. What I see a vicious cycle of expediting new high priority work fueled by long durations and unpredictable results caused by multi-tasking in the first place.</p>
<p>Without the appropriate systems in place to prioritize, we work on many tasks at the same time. We stay busy by switching but do not deliver results rapidly. This extends how long any one deliverable will take and makes it difficult to predict completion times.</p>
<p>Extensive duration length and uncertainty leads to management prioritizing “important” work into the existing work in progress, exacerbating the problems. Moving deliverables through the work stream intact reduces the time from start to finish and increases predictability.</p>
<p>The power of short time to delivery and predictable results is that management will queue the next most important thing, rather that expedite over work in process.</p>
<p>Dennis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blog.synaptus.com/2007/03/28/multi-tasking-is-bad-again/#comment-13</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 29 Mar 2007 18:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.synaptus.com/?p=33#comment-13</guid>
		<description>I’ve had this conversation with several people hierarchically above and below me and get the same vapid stare until I clarify the difference between multi-tasking and time management.  The conversation is generally an attempt to discuss the importance of appropriate prioritization.  In my mind multi-tasking is not working on something else when you cannot work on the task at hand (e.g., you are waiting), or stopping to address e-mails, answer the phone, or other aspects of corporate life.  That is time management.

Multi-tasking is the intentional stoppage of ongoing work to transition focus to another task area.

It has been my experience that many companies, and thus mid-level managers (where the work gets done), live in an inverted priority world:  more “high” priority projects than “mid” priority projects, and more “mid” priority than those with “low” priority.  This inability to prioritize then creates a need to show some (however minimal) progress across the multiple high-level projects.

The key to eliminating the perceived need to multi-task in my mind is to flip the priority world upright.  Project sponsors must internally coordinate and establish a meaningful prioritization of needed work.  Secondly, in a multi-team environment, systems need to be in place to ensure that each team member has only one highest priority project, and a clearly defined series of “nexts”. There should be minimal question regarding what should be worked on when I can’t work on my A project.  The rest is just good time management.

</description>
		<content:encoded><![CDATA[<p>I’ve had this conversation with several people hierarchically above and below me and get the same vapid stare until I clarify the difference between multi-tasking and time management.  The conversation is generally an attempt to discuss the importance of appropriate prioritization.  In my mind multi-tasking is not working on something else when you cannot work on the task at hand (e.g., you are waiting), or stopping to address e-mails, answer the phone, or other aspects of corporate life.  That is time management.</p>
<p>Multi-tasking is the intentional stoppage of ongoing work to transition focus to another task area.</p>
<p>It has been my experience that many companies, and thus mid-level managers (where the work gets done), live in an inverted priority world:  more “high” priority projects than “mid” priority projects, and more “mid” priority than those with “low” priority.  This inability to prioritize then creates a need to show some (however minimal) progress across the multiple high-level projects.</p>
<p>The key to eliminating the perceived need to multi-task in my mind is to flip the priority world upright.  Project sponsors must internally coordinate and establish a meaningful prioritization of needed work.  Secondly, in a multi-team environment, systems need to be in place to ensure that each team member has only one highest priority project, and a clearly defined series of “nexts”. There should be minimal question regarding what should be worked on when I can’t work on my A project.  The rest is just good time management.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
