<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments for The Lean Edge</title>
	<atom:link href="http://theleanedge.org/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://theleanedge.org</link>
	<description>A dialogue between business leaders and lean authors</description>
	<lastBuildDate>Fri, 18 Mar 2011 01:02:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>Comment on About by From The Lean Edge: Alternatives to Hospitals Spending, Building, and Hiring More &#171; Health Care.</title>
		<link>http://theleanedge.org/?page_id=2#comment-15</link>
		<dc:creator>From The Lean Edge: Alternatives to Hospitals Spending, Building, and Hiring More &#171; Health Care.</dc:creator>
		<pubDate>Fri, 18 Mar 2011 01:02:27 +0000</pubDate>
		<guid isPermaLink="false">http:/?page_id=2#comment-15</guid>
		<description>[...] I&#8217;m linking to a response I gave on TheLeanEdge.org&#8216;s blog that features some really well known Lean authors (people I really have learned a lot from, so it&#8217;s an honor to be [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;m linking to a response I gave on TheLeanEdge.org&#8216;s blog that features some really well known Lean authors (people I really have learned a lot from, so it&#8217;s an honor to be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mike Micklewright: Why Is Quality So Rarely Central In Lean? by Pascal Dennis</title>
		<link>http://theleanedge.org/?p=773#comment-12</link>
		<dc:creator>Pascal Dennis</dc:creator>
		<pubDate>Thu, 15 Apr 2010 17:51:40 +0000</pubDate>
		<guid isPermaLink="false">http://theleanedge.org/?p=773#comment-12</guid>
		<description>Good question, Mike.

Quality implied in the so-called &quot;House of Lean&quot; image, most obviously in the Jidoka &quot;pillar&quot;.  But you&#039;re raising a valid point.  Too often Lean implementations underemphasize Jidoka &amp; Quality, and overemphasize the other pillar (JIT).

It&#039;s understandable on some level - JIT seems &quot;cooler&quot; and promises quick payback in finished goods and WIP reduction.  But the house, and our improvement activities, become imbalanced.  We learn, eventually, that without Jidoka &amp; Quality, you can&#039;t provide the &quot;right part at the right time in the right quantity&quot;.

So what&#039;s the countermeasure?  In my view, we need to respect the house metaphor -- build a solid foundation of standards and stability (in the Four M&#039;s).  Then begin to build the walls (JIT and Jidoka) concurrently.  

Recognize that Jidoka and Quality are likely an even bigger challenge that JIT, not least because root causes inevitably lead straight upstream to our product and machine design process.

Here&#039;s a final thought.  Jidoka and Quality are even more important in our business processes: marketing, design, engineering, planning &amp; scheduling, and so on.

If you &quot;ship junk&quot; in the factory -- everybody can see it.  &quot;Hey, look at that big pile of junk!&quot;

But if you ship junk in, say scheduling, very few people can see it.  A good drawing/schedule/forecast/test-lab-report looks the same as a bad one.</description>
		<content:encoded><![CDATA[<p>Good question, Mike.</p>
<p>Quality implied in the so-called &#8220;House of Lean&#8221; image, most obviously in the Jidoka &#8220;pillar&#8221;.  But you&#8217;re raising a valid point.  Too often Lean implementations underemphasize Jidoka &amp; Quality, and overemphasize the other pillar (JIT).</p>
<p>It&#8217;s understandable on some level &#8211; JIT seems &#8220;cooler&#8221; and promises quick payback in finished goods and WIP reduction.  But the house, and our improvement activities, become imbalanced.  We learn, eventually, that without Jidoka &amp; Quality, you can&#8217;t provide the &#8220;right part at the right time in the right quantity&#8221;.</p>
<p>So what&#8217;s the countermeasure?  In my view, we need to respect the house metaphor &#8212; build a solid foundation of standards and stability (in the Four M&#8217;s).  Then begin to build the walls (JIT and Jidoka) concurrently.  </p>
<p>Recognize that Jidoka and Quality are likely an even bigger challenge that JIT, not least because root causes inevitably lead straight upstream to our product and machine design process.</p>
<p>Here&#8217;s a final thought.  Jidoka and Quality are even more important in our business processes: marketing, design, engineering, planning &amp; scheduling, and so on.</p>
<p>If you &#8220;ship junk&#8221; in the factory &#8212; everybody can see it.  &#8220;Hey, look at that big pile of junk!&#8221;</p>
<p>But if you ship junk in, say scheduling, very few people can see it.  A good drawing/schedule/forecast/test-lab-report looks the same as a bad one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ed Schein: Toyota&#8217;s Safety Culture by Pascal Dennis</title>
		<link>http://theleanedge.org/?p=652#comment-11</link>
		<dc:creator>Pascal Dennis</dc:creator>
		<pubDate>Thu, 15 Apr 2010 17:32:33 +0000</pubDate>
		<guid isPermaLink="false">http://theleanedge.org/?p=652#comment-11</guid>
		<description>Dear Dr. Shein,  It&#039;s a pleasure indeed to get a question from you.  In my personal experience at Toyota, I found that Safety, pardon the cliche, was always first.

First thing discussed at morning production meetings, weekly status reviews, mid-year and year-end reviews.

Significant safety incidents including near misses were investigated within 48 hours.  Report outs, or &quot;Safety Auctions&quot;, were lead lineside, usually by the group leader and responsible manager.   These investigations went far deeper than in any other company I know, with the possible exception of Dupont.

In new model launches, safety and ergonomics, were, again, the first order of business.  Once I asked a senior Toyota executive why safety was so important.

He responded, &quot;To buid a good car, the Four M&#039;s [manpower, machines, methods, materials] must be good. Most important is the team member.  If you don&#039;t take care of them, you cannot build a good car.&quot;

Simple, I know, but a simplicity born of years of experience.

Has Toyota&#039;s culture shifted so dramatically in the past decade, as to lose sight of safety?  I doubt it, and for what it&#039;s worth, expect Toyota to regain its footing not just in safety, but across the board.</description>
		<content:encoded><![CDATA[<p>Dear Dr. Shein,  It&#8217;s a pleasure indeed to get a question from you.  In my personal experience at Toyota, I found that Safety, pardon the cliche, was always first.</p>
<p>First thing discussed at morning production meetings, weekly status reviews, mid-year and year-end reviews.</p>
<p>Significant safety incidents including near misses were investigated within 48 hours.  Report outs, or &#8220;Safety Auctions&#8221;, were lead lineside, usually by the group leader and responsible manager.   These investigations went far deeper than in any other company I know, with the possible exception of Dupont.</p>
<p>In new model launches, safety and ergonomics, were, again, the first order of business.  Once I asked a senior Toyota executive why safety was so important.</p>
<p>He responded, &#8220;To buid a good car, the Four M&#8217;s [manpower, machines, methods, materials] must be good. Most important is the team member.  If you don&#8217;t take care of them, you cannot build a good car.&#8221;</p>
<p>Simple, I know, but a simplicity born of years of experience.</p>
<p>Has Toyota&#8217;s culture shifted so dramatically in the past decade, as to lose sight of safety?  I doubt it, and for what it&#8217;s worth, expect Toyota to regain its footing not just in safety, but across the board.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Rob Austin: Can lean help operational managers realize specific targets on schedule? by Mark Rosenthal</title>
		<link>http://theleanedge.org/?p=172#comment-9</link>
		<dc:creator>Mark Rosenthal</dc:creator>
		<pubDate>Thu, 07 Jan 2010 09:49:06 +0000</pubDate>
		<guid isPermaLink="false">http://theleanedge.org/?p=172#comment-9</guid>
		<description>Hitting specific targets on schedule is what it is about. 

Where this gets diluted is that so many companies try it out by dabbling. They don&#039;t set targets, at least not high level ones, because they don&#039;t engage continuous improvement as *the* way they are going to hit those targets.

What follows is that the lean activity happens in the background, while the &quot;traditional&quot; management-by-objectives happens in a separate, parallel universe. 

In short, the answer to your question is &quot;Yes, but only if it is done right.&quot;</description>
		<content:encoded><![CDATA[<p>Hitting specific targets on schedule is what it is about. </p>
<p>Where this gets diluted is that so many companies try it out by dabbling. They don&#8217;t set targets, at least not high level ones, because they don&#8217;t engage continuous improvement as *the* way they are going to hit those targets.</p>
<p>What follows is that the lean activity happens in the background, while the &#8220;traditional&#8221; management-by-objectives happens in a separate, parallel universe. </p>
<p>In short, the answer to your question is &#8220;Yes, but only if it is done right.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Michael Ballé: Lean is about facing one&#8217;s problems and learning to solve them by Sameh</title>
		<link>http://theleanedge.org/?p=123#comment-8</link>
		<dc:creator>Sameh</dc:creator>
		<pubDate>Thu, 24 Dec 2009 21:27:49 +0000</pubDate>
		<guid isPermaLink="false">http://theleanedge.org/?p=123#comment-8</guid>
		<description>I think Lean is about leadership that can inspire employee.The integrity of this leadership bestows climate of trust, authenticity and responsibility.

I found managers who are notably polite are manipulative. People who work for them learn a little while they learn more about survival according to the company&#039;s political values. I know of a manager who kept saying to his sub-ordinate you&#039;re doing a &quot;great&quot; job while in fact these people were under performer and never trusted on important assignment.

Managers who are over polite are normally strive to be politically correct. They consider talented or independent people as source of risk rather than opportunity.

The success of lean from my view is bound by the integrity of leadership in removing blocks in the way of the flow of work. These blocks are there because of bureaucracy and political reasons.

Respect of people is at the heart of Toyota Product Development System. People who feel appreciation and respect are competent and therefore they are secure. They are ready to adapt daily to what to be done to overcome issues and  improve performance. They trust their leadership and therefore they know that their good intent actions are acknowledged. They know they might make mistakes and their leadership can understand and even help and counsel.

I worked in process improvement project. In order to meet the TAKT time we had to improve the hand-off between two departments. It was impossible because of many political reasons. Getting the heads of the two departments to sit together to arrive at a half-way was my biggest challenge. What was required is to send mail to the other department so that waiting could be avoided. The employee felt why should he do that, it&#039;s not in his performance measures and may not count at all for his evaluation.</description>
		<content:encoded><![CDATA[<p>I think Lean is about leadership that can inspire employee.The integrity of this leadership bestows climate of trust, authenticity and responsibility.</p>
<p>I found managers who are notably polite are manipulative. People who work for them learn a little while they learn more about survival according to the company&#8217;s political values. I know of a manager who kept saying to his sub-ordinate you&#8217;re doing a &#8220;great&#8221; job while in fact these people were under performer and never trusted on important assignment.</p>
<p>Managers who are over polite are normally strive to be politically correct. They consider talented or independent people as source of risk rather than opportunity.</p>
<p>The success of lean from my view is bound by the integrity of leadership in removing blocks in the way of the flow of work. These blocks are there because of bureaucracy and political reasons.</p>
<p>Respect of people is at the heart of Toyota Product Development System. People who feel appreciation and respect are competent and therefore they are secure. They are ready to adapt daily to what to be done to overcome issues and  improve performance. They trust their leadership and therefore they know that their good intent actions are acknowledged. They know they might make mistakes and their leadership can understand and even help and counsel.</p>
<p>I worked in process improvement project. In order to meet the TAKT time we had to improve the hand-off between two departments. It was impossible because of many political reasons. Getting the heads of the two departments to sit together to arrive at a half-way was my biggest challenge. What was required is to send mail to the other department so that waiting could be avoided. The employee felt why should he do that, it&#8217;s not in his performance measures and may not count at all for his evaluation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
