<?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 for Synaptus</title>
	<atom:link href="http://blog.synaptus.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.synaptus.com</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Thu, 28 Aug 2008 11:07:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>Comment on Lessons from the Blogosphere by Stuart Baker</title>
		<link>http://blog.synaptus.com/2007/03/08/lessons-from-the-blogosphere/#comment-7</link>
		<dc:creator>Stuart Baker</dc:creator>
		<pubDate>Mon, 16 Apr 2007 14:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.synaptus.com/?p=15#comment-7</guid>
		<description>Dennis, this thank-you is a bit delayed, but I appreciate your nod.

I really respect what you and the people with you are doing, too.

Stuart Baker
www.consciouscooperation.com
</description>
		<content:encoded><![CDATA[<p>Dennis, this thank-you is a bit delayed, but I appreciate your nod.</p>
<p>I really respect what you and the people with you are doing, too.</p>
<p>Stuart Baker<br />
<a href="http://www.consciouscooperation.com" rel="nofollow">http://www.consciouscooperation.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Multi-tasking is bad - Again 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>Comment on Multi-tasking is bad - Again 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>
	<item>
		<title>Comment on Workforce 2015 by Steve</title>
		<link>http://blog.synaptus.com/2007/03/20/workforce-2015/#comment-12</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 20 Mar 2007 19:48:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.synaptus.com/?p=26#comment-12</guid>
		<description>Although bleak from a personal/personnel standpoint, based on the current trends the direction that will ultimately be taken is quite clear - those rolls will be outsourced as the skill sets of the resources currently being used to perform more “menial tasks” are developed to encompass innovation, design, and the like.

I have been reading, "The World is Flat" by Thomas Friedman, and have been a fan of Tom Peters for a while now.  Both firmly believe that the natural progression will be from the outsourcing of services to that of knowledge-based work - it's only a matter of time.

Companies will remain competitive through whatever means they choose to utilize as the environment dictates.  If faced with an unreliable, incompetent workforce in the US with a highly reliable and motivated workforce in India and China – the decision becomes obvious (from a corporate survival perspective).

The question that both raise; how do we (and our children) remain competitive in a globalized environment?

Outsourcing, to me, makes "global warming" look like just another sunny day in the context of those global issues that are going to most impact our future generations.

Clunk – clunk (that’s me stepping off my soapbox).

</description>
		<content:encoded><![CDATA[<p>Although bleak from a personal/personnel standpoint, based on the current trends the direction that will ultimately be taken is quite clear - those rolls will be outsourced as the skill sets of the resources currently being used to perform more “menial tasks” are developed to encompass innovation, design, and the like.</p>
<p>I have been reading, &#8220;The World is Flat&#8221; by Thomas Friedman, and have been a fan of Tom Peters for a while now.  Both firmly believe that the natural progression will be from the outsourcing of services to that of knowledge-based work - it&#8217;s only a matter of time.</p>
<p>Companies will remain competitive through whatever means they choose to utilize as the environment dictates.  If faced with an unreliable, incompetent workforce in the US with a highly reliable and motivated workforce in India and China – the decision becomes obvious (from a corporate survival perspective).</p>
<p>The question that both raise; how do we (and our children) remain competitive in a globalized environment?</p>
<p>Outsourcing, to me, makes &#8220;global warming&#8221; look like just another sunny day in the context of those global issues that are going to most impact our future generations.</p>
<p>Clunk – clunk (that’s me stepping off my soapbox).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Business Cards Tell a Story by Stuart Baker</title>
		<link>http://blog.synaptus.com/2007/03/14/business-cards-tell-a-story/#comment-11</link>
		<dc:creator>Stuart Baker</dc:creator>
		<pubDate>Thu, 15 Mar 2007 14:03:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.synaptus.com/?p=21#comment-11</guid>
		<description>Dennis, this is a really interesting subject.

To me it is key to work on the human relations, which would include sharing knowledge.   Underneath that I think we have a wish to feel that we matter, that we are valued, that we are more than just workers for a company.

I have seen people stay with a company for years because they are happy there, even though they could make more money somewhere else.

Stuart Baker
www.consciouscooperation.com
</description>
		<content:encoded><![CDATA[<p>Dennis, this is a really interesting subject.</p>
<p>To me it is key to work on the human relations, which would include sharing knowledge.   Underneath that I think we have a wish to feel that we matter, that we are valued, that we are more than just workers for a company.</p>
<p>I have seen people stay with a company for years because they are happy there, even though they could make more money somewhere else.</p>
<p>Stuart Baker<br />
<a href="http://www.consciouscooperation.com" rel="nofollow">http://www.consciouscooperation.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile Management by Steve</title>
		<link>http://blog.synaptus.com/2007/03/14/agile-management/#comment-10</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 14 Mar 2007 18:24:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.synaptus.com/?p=20#comment-10</guid>
		<description>With respect to Merit-based pay, marketing guru Seth Godin relates his recent experience at, of all places, his local Toyota dealership (http://sethgodin.typepad.com/seths_blog/2007/03/good_is_not_alm.html).

The output of his visit; some rather brutal advice that may be more generally applicable (if I weren't such a nice guy) across all areas of business:

Seth's advice: Fire half your salesforce. Then, give the remainder, the top people, a big raise, and use the money left over to steal the best salespeole you can find from other industries or even from your competition. You'll end up with fewer salespeople. But all of them will be great.

And the good guys? Have them go work for the competition.

Seth is clearly all about "great", but we all should be.

In the past, I've lost "great" people because I believed or didn't challenge the "good" pay guidlines provided by my HR group.  If I had fought harder, I probably would have had different outcomes.
</description>
		<content:encoded><![CDATA[<p>With respect to Merit-based pay, marketing guru Seth Godin relates his recent experience at, of all places, his local Toyota dealership (http://sethgodin.typepad.com/seths_blog/2007/03/good_is_not_alm.html).</p>
<p>The output of his visit; some rather brutal advice that may be more generally applicable (if I weren&#8217;t such a nice guy) across all areas of business:</p>
<p>Seth&#8217;s advice: Fire half your salesforce. Then, give the remainder, the top people, a big raise, and use the money left over to steal the best salespeole you can find from other industries or even from your competition. You&#8217;ll end up with fewer salespeople. But all of them will be great.</p>
<p>And the good guys? Have them go work for the competition.</p>
<p>Seth is clearly all about &#8220;great&#8221;, but we all should be.</p>
<p>In the past, I&#8217;ve lost &#8220;great&#8221; people because I believed or didn&#8217;t challenge the &#8220;good&#8221; pay guidlines provided by my HR group.  If I had fought harder, I probably would have had different outcomes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Talking about what we&#8217;re talking about by Dennis Stevens</title>
		<link>http://blog.synaptus.com/2007/03/13/talking-about-what-were-talking-about/#comment-9</link>
		<dc:creator>Dennis Stevens</dc:creator>
		<pubDate>Wed, 14 Mar 2007 18:17:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.synaptus.com/?p=19#comment-9</guid>
		<description>Based on this definition of conversation "The use of language to exchange thoughts, ideas or information", then they must be taking place, they just aren't taking place purposefully. However, I recently found a great definition of conversation. A conversation is a "two way exchange entered into with an intent on the part of both parties to be changed in the process." I need to research the source since I will using it. But based on this definition of conversation it appears you are right, the conversations aren't talking place. I would say that people are participating in the conversations differently. In one case they are partcipating to defend their norms and perception of value without regard for productivity. In the other case they are participating with the intention of improving productivity. Sometimes, you are able to induce the second type of conversation when it is necessary. The goal of Productive Collaboration is not to induce these conversations everywhere all the time, but to purposefully identify the ones that must happen effectively and consistently induce the second kind of participation.
</description>
		<content:encoded><![CDATA[<p>Based on this definition of conversation &#8220;The use of language to exchange thoughts, ideas or information&#8221;, then they must be taking place, they just aren&#8217;t taking place purposefully. However, I recently found a great definition of conversation. A conversation is a &#8220;two way exchange entered into with an intent on the part of both parties to be changed in the process.&#8221; I need to research the source since I will using it. But based on this definition of conversation it appears you are right, the conversations aren&#8217;t talking place. I would say that people are participating in the conversations differently. In one case they are partcipating to defend their norms and perception of value without regard for productivity. In the other case they are participating with the intention of improving productivity. Sometimes, you are able to induce the second type of conversation when it is necessary. The goal of Productive Collaboration is not to induce these conversations everywhere all the time, but to purposefully identify the ones that must happen effectively and consistently induce the second kind of participation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Talking about what we&#8217;re talking about by Steve</title>
		<link>http://blog.synaptus.com/2007/03/13/talking-about-what-were-talking-about/#comment-8</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 14 Mar 2007 16:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.synaptus.com/?p=19#comment-8</guid>
		<description>I believe that one of the key issues is that “conversations” are not taking place at all.  As the project lead across several independent, as well as inter-related projects I often deal with what I consider concurrent monologues – each team member looking out for themselves or their turf.

The root of these challenges seem to be engineered into the overall process with local goals, measurements, and management styles all being different, and ultimately driving what each individual/functional area is saying and how they are acting.  In siloed hierarchies it has been my experience that these differences rise all the way to the top, and thus are very entrenched at the bottom.

Coming to this understanding over the past few years has allowed me to modify myself to allow dialogues, and in rare instances what I would consider meaningful conversation when the right people are in the room.  When it works, it’s beautiful, and makes it a little bit easier to get out of bed in the morning.

</description>
		<content:encoded><![CDATA[<p>I believe that one of the key issues is that “conversations” are not taking place at all.  As the project lead across several independent, as well as inter-related projects I often deal with what I consider concurrent monologues – each team member looking out for themselves or their turf.</p>
<p>The root of these challenges seem to be engineered into the overall process with local goals, measurements, and management styles all being different, and ultimately driving what each individual/functional area is saying and how they are acting.  In siloed hierarchies it has been my experience that these differences rise all the way to the top, and thus are very entrenched at the bottom.</p>
<p>Coming to this understanding over the past few years has allowed me to modify myself to allow dialogues, and in rare instances what I would consider meaningful conversation when the right people are in the room.  When it works, it’s beautiful, and makes it a little bit easier to get out of bed in the morning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lessons from the Blogosphere by Chuck Hester, IntelliContact</title>
		<link>http://blog.synaptus.com/2007/03/08/lessons-from-the-blogosphere/#comment-6</link>
		<dc:creator>Chuck Hester, IntelliContact</dc:creator>
		<pubDate>Thu, 08 Mar 2007 23:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.synaptus.com/?p=15#comment-6</guid>
		<description>Glad you are using us, Dennis.  We are all about making your publishing experience easier!
</description>
		<content:encoded><![CDATA[<p>Glad you are using us, Dennis.  We are all about making your publishing experience easier!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lessons from the Blogosphere by Dave Schoof</title>
		<link>http://blog.synaptus.com/2007/03/08/lessons-from-the-blogosphere/#comment-5</link>
		<dc:creator>Dave Schoof</dc:creator>
		<pubDate>Thu, 08 Mar 2007 22:46:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.synaptus.com/?p=15#comment-5</guid>
		<description>Thanks for the mention Dennis.  I will be back to visit and explore!
</description>
		<content:encoded><![CDATA[<p>Thanks for the mention Dennis.  I will be back to visit and explore!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
