<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Avoiding Breakdowns</title>
	<link>http://www.reformingprojectmanagement.com/2003/09/15/240/</link>
	<description>The magazine for the project age</description>
	<pubDate>Wed, 07 Jan 2009 06:53:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Erudite
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/09/15/240/#comment-53</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/09/15/240/#comment-53</guid>
					<description>
        I read Hal’s blog in the morning.  Later in the day, while reading the New Yorker [pp. 94, 9/15/03] Hal’s blog and comments of “et al” converged with Joseph Stiglitz, who, in 1977, wrote of asymmetric information: one party to a transaction knows more than the other party, such as when a buyer taking out a life insurance knows more about his health that the insurance company does.  The concept really applies to market theory, but, hey, we borrow freely to create metaphors for understanding and getting to stretch.  I thought the concept neatly addresses this issue of breakdowns and variation. 

Variations: in the world of [project management, engineering, coaching, art, fill in the industry, field, etc. here] a variation can be the mother of invention.  Variation can be the very accident that fosters breakthrough thinking, true creativity when people “play” with work – good variation.  The key then is to know a bad idea when you process it out-loud.  If you misjudge the variation because you did not have all the information needed [asymmetrical] to inform your thinking – bad variation.

Breakdowns: when one party responsible to critical path knows more than the other party responsible to critical path, for example about resources [or external dependencies, or timing, or schedule, or the nexus of other work requiring the same participants, etc].  The challenge is to get everyone up to “the same speed” versus getting the project up.  

We are hired because of our expertise in helping customers accomplish goals, but somehow the seduction of a new exciting project pushes us off course – going asymmetrical.  The goal is to get to symmetrical information – a universal awareness where we are fully informed of the customers’ desired outcomes and the customer is informed of the process to achieve the outcome.  In symmetrical harmony everyone understands the goals, objectives, partnerships, and relationships needed to achieve a successful project. In symmetrical harmoney, everyone understands that disconnects, breakdowns, variations, are part of the human project process and, as Hal points out, we can embrace them.  

By being breakdown and variation tolerant, we just might discover something new in recovery – hence, the Yellow Stickie!
      </description>
		<content:encoded><![CDATA[<p>I read Hal’s blog in the morning.  Later in the day, while reading the New Yorker [pp. 94, 9/15/03] Hal’s blog and comments of “et al” converged with Joseph Stiglitz, who, in 1977, wrote of asymmetric information: one party to a transaction knows more than the other party, such as when a buyer taking out a life insurance knows more about his health that the insurance company does.  The concept really applies to market theory, but, hey, we borrow freely to create metaphors for understanding and getting to stretch.  I thought the concept neatly addresses this issue of breakdowns and variation. </p>
<p>Variations: in the world of [project management, engineering, coaching, art, fill in the industry, field, etc. here] a variation can be the mother of invention.  Variation can be the very accident that fosters breakthrough thinking, true creativity when people “play” with work – good variation.  The key then is to know a bad idea when you process it out-loud.  If you misjudge the variation because you did not have all the information needed [asymmetrical] to inform your thinking – bad variation.</p>
<p>Breakdowns: when one party responsible to critical path knows more than the other party responsible to critical path, for example about resources [or external dependencies, or timing, or schedule, or the nexus of other work requiring the same participants, etc].  The challenge is to get everyone up to “the same speed” versus getting the project up.  </p>
<p>We are hired because of our expertise in helping customers accomplish goals, but somehow the seduction of a new exciting project pushes us off course – going asymmetrical.  The goal is to get to symmetrical information – a universal awareness where we are fully informed of the customers’ desired outcomes and the customer is informed of the process to achieve the outcome.  In symmetrical harmony everyone understands the goals, objectives, partnerships, and relationships needed to achieve a successful project. In symmetrical harmoney, everyone understands that disconnects, breakdowns, variations, are part of the human project process and, as Hal points out, we can embrace them.  </p>
<p>By being breakdown and variation tolerant, we just might discover something new in recovery – hence, the Yellow Stickie!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Joe Ely
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/09/15/240/#comment-54</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/09/15/240/#comment-54</guid>
					<description>
        Good systems do have a robustness to them, that handles disruptions.  The twin pillars of lean, JIT and autonomation, point to that, especially the second one.  

The rub, as you point out well, Hal, is that it is much harder to do in human systems (e.g. project management) than in mechanical systems (e.g. a punch press). 

It seems that one need is for maintaining some excess capacity in the system.  A TOC Buffer, or just some extra time.  

Fascinating topic that has, indeed, grabbed interest.
      </description>
		<content:encoded><![CDATA[<p>Good systems do have a robustness to them, that handles disruptions.  The twin pillars of lean, JIT and autonomation, point to that, especially the second one.  </p>
<p>The rub, as you point out well, Hal, is that it is much harder to do in human systems (e.g. project management) than in mechanical systems (e.g. a punch press). </p>
<p>It seems that one need is for maintaining some excess capacity in the system.  A <acronym title="Theory of Constraints; Eli Goldratt's insight on throughput">TOC</acronym> Buffer, or just some extra time.  </p>
<p>Fascinating topic that has, indeed, grabbed interest.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Garrie Hankins
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/09/15/240/#comment-55</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/09/15/240/#comment-55</guid>
					<description>
        I think we can and should. Breakdowns as you describe them can also be an opportunity. 

When working our way though the critical path we will run into unexpected obstacles. Sometimes these obstacles are detrimental and sometimes they are beneficial to the quality of the project. They may even present unexpected opportunities for innovation.

I think, that as project managers, we should nurture innovation in our project teams. We must be aware of the potential to crush opportunities for innovation by being overly task and process oriented. 

But at the same time we must keep the focus of the project team in the direction of completing the project goals. The trick is how do we keep that balance between staying open to unexpected opportunities and moving the project along to meet time and cost objectives?
      </description>
		<content:encoded><![CDATA[<p>I think we can and should. Breakdowns as you describe them can also be an opportunity. </p>
<p>When working our way though the critical path we will run into unexpected obstacles. Sometimes these obstacles are detrimental and sometimes they are beneficial to the quality of the project. They may even present unexpected opportunities for innovation.</p>
<p>I think, that as project managers, we should nurture innovation in our project teams. We must be aware of the potential to crush opportunities for innovation by being overly task and process oriented. </p>
<p>But at the same time we must keep the focus of the project team in the direction of completing the project goals. The trick is how do we keep that balance between staying open to unexpected opportunities and moving the project along to meet time and cost objectives?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Frank Winters
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/09/15/240/#comment-56</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/09/15/240/#comment-56</guid>
					<description>
        In my experience most opportunistic breakdowns should not change a particular project's purpose unless something has been learned that tells us that such a change is sensible.

If an opportunity for innovation presents itself we need to be certain that the innovation is an aid to the project we are actually working on. If not one might consider spawning a new, additional project to take advantage of the opportunity.

I believe this to be a critical distinction.
      </description>
		<content:encoded><![CDATA[<p>In my experience most opportunistic breakdowns should not change a particular project&#8217;s purpose unless something has been learned that tells us that such a change is sensible.</p>
<p>If an opportunity for innovation presents itself we need to be certain that the innovation is an aid to the project we are actually working on. If not one might consider spawning a new, additional project to take advantage of the opportunity.</p>
<p>I believe this to be a critical distinction.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
