

<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Toyota&#8217;s Lesson for Project Managers</title>
	<atom:link href="http://www.reformingprojectmanagement.com/2010/02/10/1060/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/</link>
	<description>The magazine for the project age</description>
	<lastBuildDate>Fri, 15 Apr 2011 17:20:14 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Itaz</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21935</link>
		<dc:creator>Itaz</dc:creator>
		<pubDate>Wed, 16 Mar 2011 12:52:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21935</guid>
		<description>For an organization such as Toyota there are enough lessons to learn from this setback than from all their successful ventures.</description>
		<content:encoded><![CDATA[<p>For an organization such as Toyota there are enough lessons to learn from this setback than from all their successful ventures.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21933</link>
		<dc:creator>David</dc:creator>
		<pubDate>Fri, 11 Mar 2011 10:07:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21933</guid>
		<description>Just wondering how Hal is: no blog action for months. If he&#039;s not well, best wishes, and my thoughts are with him,

David</description>
		<content:encoded><![CDATA[<p>Just wondering how Hal is: no blog action for months. If he&#8217;s not well, best wishes, and my thoughts are with him,</p>
<p>David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LSS</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21809</link>
		<dc:creator>LSS</dc:creator>
		<pubDate>Wed, 12 Jan 2011 17:47:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21809</guid>
		<description>It&#039;s been interesting to see how Toyota&#039;s been handling the recalls - there have been several. 

I think they screwed up at first, but have made somewhat of a comeback, not completely, but to an extent. 

Though I wonder how much that has to do with Toyota and how much has to do with the public beginning to forget since it&#039;s not in front of them 24/7 any longer.</description>
		<content:encoded><![CDATA[<p>It&#8217;s been interesting to see how Toyota&#8217;s been handling the recalls &#8211; there have been several. </p>
<p>I think they screwed up at first, but have made somewhat of a comeback, not completely, but to an extent. </p>
<p>Though I wonder how much that has to do with Toyota and how much has to do with the public beginning to forget since it&#8217;s not in front of them 24/7 any longer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Project Manager</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21701</link>
		<dc:creator>Project Manager</dc:creator>
		<pubDate>Wed, 27 Oct 2010 20:11:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21701</guid>
		<description>With the magnitude of his job I think it is safe to assume that he cannot be accused of having bad intentions. I&#039;m sure his over-sight lapsed and certain things happened that shouldn&#039;t have. We all make mistakes, but seeing how the company bounces back will be good learning material for all of us. Sincerely, &lt;a href=&quot;http://projectmanagerinfo.com&quot; rel=&quot;nofollow&quot;&gt;Project Manager&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>With the magnitude of his job I think it is safe to assume that he cannot be accused of having bad intentions. I&#8217;m sure his over-sight lapsed and certain things happened that shouldn&#8217;t have. We all make mistakes, but seeing how the company bounces back will be good learning material for all of us. Sincerely, <a href="http://projectmanagerinfo.com" rel="nofollow">Project Manager</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jessie Warner</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21673</link>
		<dc:creator>Jessie Warner</dc:creator>
		<pubDate>Tue, 12 Oct 2010 20:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21673</guid>
		<description>I think Toyota has been and continues to be a good company and does many things right.  Their mistake will pass in time and soon people won&#039;t even remember that it happened.  Lucky for us and them.</description>
		<content:encoded><![CDATA[<p>I think Toyota has been and continues to be a good company and does many things right.  Their mistake will pass in time and soon people won&#8217;t even remember that it happened.  Lucky for us and them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21669</link>
		<dc:creator>Art</dc:creator>
		<pubDate>Fri, 08 Oct 2010 19:01:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21669</guid>
		<description>Hi Hal , we would be interested in interviewing you for our website. Please take a look at our site http://www.operationsmanager.com and send me an email if you would like to be interviewed .

Art
Manager
www.OperationsManager.com</description>
		<content:encoded><![CDATA[<p>Hi Hal , we would be interested in interviewing you for our website. Please take a look at our site <a href="http://www.operationsmanager.com" rel="nofollow">http://www.operationsmanager.com</a> and send me an email if you would like to be interviewed .</p>
<p>Art<br />
Manager<br />
<a href="http://www.OperationsManager.com" rel="nofollow">http://www.OperationsManager.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Baybour</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21463</link>
		<dc:creator>Paul Baybour</dc:creator>
		<pubDate>Sat, 13 Mar 2010 22:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21463</guid>
		<description>Every successful organisation makes the mistake of believing its own publicity. Toyota has come a long way from its birth a truly lean organisation. It was lean not out of choice but because it was the only affordable option. Ideas like these have a natural life cycle. Why so we expect more from Toyota than any other car manufacture.</description>
		<content:encoded><![CDATA[<p>Every successful organisation makes the mistake of believing its own publicity. Toyota has come a long way from its birth a truly lean organisation. It was lean not out of choice but because it was the only affordable option. Ideas like these have a natural life cycle. Why so we expect more from Toyota than any other car manufacture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Freelance Project Manager</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21462</link>
		<dc:creator>Freelance Project Manager</dc:creator>
		<pubDate>Sat, 13 Mar 2010 20:07:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21462</guid>
		<description>I think mistakes do happen in any organisation and we are all falleable and make mistakes. The same with any project, admit a mistake has been made, do your best to rectify it and document the lesson learned and make someone accountable for owning or actioning that lesson.</description>
		<content:encoded><![CDATA[<p>I think mistakes do happen in any organisation and we are all falleable and make mistakes. The same with any project, admit a mistake has been made, do your best to rectify it and document the lesson learned and make someone accountable for owning or actioning that lesson.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: doc_usui</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21461</link>
		<dc:creator>doc_usui</dc:creator>
		<pubDate>Sat, 13 Mar 2010 05:18:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21461</guid>
		<description>I think lesson on this time is too much human error

According to the NHTSA, It looks like 95% or more root cause of the unintended acceleration is human error. It means people are depressing acceleration pedal instead of brake pedal when they try to stop. 

If so, we can not fix these unintended acceleration problem even if we have non troubled car or we introduce brake prioritized control program.  For example Prius have this control but still creating unintended acceleration problem.

To prevent this kind of human error, I think we must change our vehicle operation manner to suppress this kind of miss operation. I think miss operation caused by to use same foot and depressing action for both acceleration and braking. So one of possible counter measure is using hand for braking. Like installing a multiple braking grip around the steering column?  

It looks funny but If we think seriously to prevent unintended acceleration accident, I believe we need this kind of counter measure. Also If we can eliminate human error and still have unintended acceleration problem then we must fund another root cause and counter measure.  I think taking action from bigger matter is the basic of problem solving.</description>
		<content:encoded><![CDATA[<p>I think lesson on this time is too much human error</p>
<p>According to the NHTSA, It looks like 95% or more root cause of the unintended acceleration is human error. It means people are depressing acceleration pedal instead of brake pedal when they try to stop. </p>
<p>If so, we can not fix these unintended acceleration problem even if we have non troubled car or we introduce brake prioritized control program.  For example Prius have this control but still creating unintended acceleration problem.</p>
<p>To prevent this kind of human error, I think we must change our vehicle operation manner to suppress this kind of miss operation. I think miss operation caused by to use same foot and depressing action for both acceleration and braking. So one of possible counter measure is using hand for braking. Like installing a multiple braking grip around the steering column?  </p>
<p>It looks funny but If we think seriously to prevent unintended acceleration accident, I believe we need this kind of counter measure. Also If we can eliminate human error and still have unintended acceleration problem then we must fund another root cause and counter measure.  I think taking action from bigger matter is the basic of problem solving.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Burden</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21445</link>
		<dc:creator>Will Burden</dc:creator>
		<pubDate>Sat, 13 Feb 2010 20:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21445</guid>
		<description>The core of TPS is the awareness that the system is not perfect, but that it can always be made better. That is the role of the people in the process. Those who actually worked with Taichi Ohno, probably the key architect/implementer of TPS as we know it, all talk about his relentless role in keeping people focused on the system, and on the intense discipline of applying TPS precepts to any process. It is, for most of us, inherently counterintuitive. The fact that it works pretty well on the production floor does not mean that it will automatically transfer to the sales and marketing side of the business without the same discipline. 
Those who have some experience with Toyota management will probably recognize, if they look closely, that kaizen can also be used to ignore or redefine problems, or to focus on solutions that meet other requirements than &quot;customer first.&quot; It&#039;s not the tool, it&#039;s the system.
The philosophy IS scalable. If the staff seems fearful of pulling the andan cord, that goes to the heart of TPS, not just its application in this case.</description>
		<content:encoded><![CDATA[<p>The core of TPS is the awareness that the system is not perfect, but that it can always be made better. That is the role of the people in the process. Those who actually worked with Taichi Ohno, probably the key architect/implementer of TPS as we know it, all talk about his relentless role in keeping people focused on the system, and on the intense discipline of applying TPS precepts to any process. It is, for most of us, inherently counterintuitive. The fact that it works pretty well on the production floor does not mean that it will automatically transfer to the sales and marketing side of the business without the same discipline.<br />
Those who have some experience with Toyota management will probably recognize, if they look closely, that <acronym title="Japanese term for continuous improvement">kaizen</acronym> can also be used to ignore or redefine problems, or to focus on solutions that meet other requirements than &#8220;customer first.&#8221; It&#8217;s not the tool, it&#8217;s the system.<br />
The philosophy IS scalable. If the staff seems fearful of pulling the andan cord, that goes to the heart of TPS, not just its application in this case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Romero, IT Governance Evangelist, PMP</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21444</link>
		<dc:creator>Steve Romero, IT Governance Evangelist, PMP</dc:creator>
		<pubDate>Sat, 13 Feb 2010 16:50:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21444</guid>
		<description>Nice advice for Project Managers. I just want to temper the expectation on Project Managers by including Project Sponsors in your quest for diligence and fostering open communication.  Given the inevitable unknown you rightfully anticipate, Project Sponsors need to be open to change, tolerant of mistakes, and responsive to customer needs. If Project Managers are to have any chance of managing a team that speaks up and freely shares information, Project Sponsors must work with Enterprise Leaders to create a culture that values and rewards accurate information - whether the news is bad or good. I have seen few organizations with the audacity and courage to accept the unknown you describe, and even fewer with the tolerance, resilience and perseverance to overcome the types of challenges Toyota now faces.

Steve Romero, IT Governance Evangelist
http://community.ca.com/blogs/theitgovernanceevangelist/</description>
		<content:encoded><![CDATA[<p>Nice advice for Project Managers. I just want to temper the expectation on Project Managers by including Project Sponsors in your quest for diligence and fostering open communication.  Given the inevitable unknown you rightfully anticipate, Project Sponsors need to be open to change, tolerant of mistakes, and responsive to customer needs. If Project Managers are to have any chance of managing a team that speaks up and freely shares information, Project Sponsors must work with Enterprise Leaders to create a culture that values and rewards accurate information &#8211; whether the news is bad or good. I have seen few organizations with the audacity and courage to accept the unknown you describe, and even fewer with the tolerance, resilience and perseverance to overcome the types of challenges Toyota now faces.</p>
<p>Steve Romero, IT Governance Evangelist<br />
<a href="http://community.ca.com/blogs/theitgovernanceevangelist/" rel="nofollow">http://community.ca.com/blogs/theitgovernanceevangelist/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hal</title>
		<link>http://www.reformingprojectmanagement.com/2010/02/10/1060/comment-page-1/#comment-21443</link>
		<dc:creator>Hal</dc:creator>
		<pubDate>Sat, 13 Feb 2010 15:59:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.reformingprojectmanagement.com/?p=1060#comment-21443</guid>
		<description>Dear Dr. K,

Shameless transparency is one of Toyota&#039;s aims. They say it differently, but they celebrate when people announce their own failings. In fact, not doing so is a reason for firing. But it is not in our nature, certainly not in Western society, to announce our mistakes in the moment we make them. It seems contrary to our human condition. 

Thirteen years ago I joined &lt;a href=&quot;http://www.neenan.com&quot; rel=&quot;nofollow&quot;&gt;The Neenan Company&lt;/a&gt;, a design-build firm in Fort Collins, CO, to be their COO. David Neenan understood that their only hope of competing and thriving rested on everyone in his company and on his projects to celebrate the learning that came from the mistakes we made and encountered. He had a large Chinese gong in the lobby to be used for announcing and sharing the learning from mistakes. As you might imagine new people would hesitate to bang the gong. I was hesitant. Small mistakes that were quickly addressed didn&#039;t look like learning opportunities. Big mistakes were too embarrassing. It took courage to bang the gong...courage that was rewarded each time with praise.

Toyota, like Neenan, work on shameless transparency. Neither has achieved it. Neither is in denial about it. Neither just hopes that one day it will work. Both have complementary practices to stay close with their staff, partners and customers so they can avoid upsets. Still, it is not perfect.</description>
		<content:encoded><![CDATA[<p>Dear Dr. K,</p>
<p>Shameless transparency is one of Toyota&#8217;s aims. They say it differently, but they celebrate when people announce their own failings. In fact, not doing so is a reason for firing. But it is not in our nature, certainly not in Western society, to announce our mistakes in the moment we make them. It seems contrary to our human condition. </p>
<p>Thirteen years ago I joined <a href="http://www.neenan.com" rel="nofollow">The Neenan Company</a>, a design-build firm in Fort Collins, CO, to be their COO. David Neenan understood that their only hope of competing and thriving rested on everyone in his company and on his projects to celebrate the learning that came from the mistakes we made and encountered. He had a large Chinese gong in the lobby to be used for announcing and sharing the learning from mistakes. As you might imagine new people would hesitate to bang the gong. I was hesitant. Small mistakes that were quickly addressed didn&#8217;t look like learning opportunities. Big mistakes were too embarrassing. It took courage to bang the gong&#8230;courage that was rewarded each time with praise.</p>
<p>Toyota, like Neenan, work on shameless transparency. Neither has achieved it. Neither is in denial about it. Neither just hopes that one day it will work. Both have complementary practices to stay close with their staff, partners and customers so they can avoid upsets. Still, it is not perfect.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 1.202 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-01-29 22:21:01 -->

