<?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: Looking for the next evolution of lean? Look back.</title>
	<atom:link href="http://www.shipulski.com/2010/02/17/looking-for-the-next-evolution-of-lean-look-back/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shipulski.com/2010/02/17/looking-for-the-next-evolution-of-lean-look-back/</link>
	<description>Innovation, Product Development, Design</description>
	<lastBuildDate>Fri, 10 Sep 2010 15:33:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: George Rathbun</title>
		<link>http://www.shipulski.com/2010/02/17/looking-for-the-next-evolution-of-lean-look-back/comment-page-1/#comment-230</link>
		<dc:creator>George Rathbun</dc:creator>
		<pubDate>Thu, 04 Mar 2010 04:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.shipulski.com/?p=525#comment-230</guid>
		<description>A lot of the complexity we see in factories stems directly from designs which are not manufacturing friendly.  One of the best things that an organization can do is ensure process engineers are on the team that defines the DFMEA. The process engineer&#039;s feedback is critical in designing parts that are easy to manufacture with high quality and no complexity.</description>
		<content:encoded><![CDATA[<p>A lot of the complexity we see in factories stems directly from designs which are not manufacturing friendly.  One of the best things that an organization can do is ensure process engineers are on the team that defines the DFMEA. The process engineer&#8217;s feedback is critical in designing parts that are easy to manufacture with high quality and no complexity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://www.shipulski.com/2010/02/17/looking-for-the-next-evolution-of-lean-look-back/comment-page-1/#comment-225</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Sat, 27 Feb 2010 23:00:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.shipulski.com/?p=525#comment-225</guid>
		<description>This post was mentioned on Twitter by mwalsh: Overlapping philosophy w #leanstartup - nice. RT @MikeShipulski: The next evolution of lean http://ow.ly/18tL4...</description>
		<content:encoded><![CDATA[<p>This post was mentioned on Twitter by mwalsh: Overlapping philosophy w #leanstartup &#8211; nice. RT @MikeShipulski: The next evolution of lean <a href="http://ow.ly/18tL4.." rel="nofollow">http://ow.ly/18tL4..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich MacInnes</title>
		<link>http://www.shipulski.com/2010/02/17/looking-for-the-next-evolution-of-lean-look-back/comment-page-1/#comment-168</link>
		<dc:creator>Rich MacInnes</dc:creator>
		<pubDate>Fri, 19 Feb 2010 14:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.shipulski.com/?p=525#comment-168</guid>
		<description>The next area of lean breakthrough is where it should have been all the time...

1st - Demand Management - Without fail the supply chain suffers from lack of clear, meaningful, and timely consumer and industrial demand information... shipping to releases is not demand... it simply pushes inventory forward.  EOQ and similar thinking has caused the glut of inventory as it sits waiting for demand.  Now that inventory has been depleted by the massive shutdown of plants across industry, now we are retooling with the same mindless thinking and I fear that lean tools haven&#039;t been adequate to the task in demand management.  When tiered-suppliers are ask about the nature of demand their customers experience that drives orders to them they are nearly all clueless. Optimizing supply without improved knowledge and transparency of demand information is folly.  Yet we do it without question.

2nd - Product Performance Feedback - I recently attended a working session with a leading design technology provider and suggested that warranty information, failure information, maintenance information, customer satisfaction feedback, et al.  needed to make its way back to the design engineer.  The company informed me that I was 7 years ahead of industry thinking.  What???? Ask Toyota engineering if they think this would have been useful in their accelerators and braking systems!  Designing products that create value of the life of the product requires integrated market feedback... yet like demand information, constipation of essential product performance data remains the bane of industry.  So now we have plants shut down as demand falls off the map for Toyota because products were designed that severely impacted forecasted demand. But that’s okay... demand wasn&#039;t forecasted and communicated usefully (refer to first point).  

We can&#039;t 5S, Six Sigma, or Kaizen event our way out of these fundamental flaws in our supply chain practices... one-piece flow to supply (inventory) waiting for demand  just doesn&#039;t appear like progress to me.</description>
		<content:encoded><![CDATA[<p>The next area of lean breakthrough is where it should have been all the time&#8230;</p>
<p>1st &#8211; Demand Management &#8211; Without fail the supply chain suffers from lack of clear, meaningful, and timely consumer and industrial demand information&#8230; shipping to releases is not demand&#8230; it simply pushes inventory forward.  EOQ and similar thinking has caused the glut of inventory as it sits waiting for demand.  Now that inventory has been depleted by the massive shutdown of plants across industry, now we are retooling with the same mindless thinking and I fear that lean tools haven&#8217;t been adequate to the task in demand management.  When tiered-suppliers are ask about the nature of demand their customers experience that drives orders to them they are nearly all clueless. Optimizing supply without improved knowledge and transparency of demand information is folly.  Yet we do it without question.</p>
<p>2nd &#8211; Product Performance Feedback &#8211; I recently attended a working session with a leading design technology provider and suggested that warranty information, failure information, maintenance information, customer satisfaction feedback, et al.  needed to make its way back to the design engineer.  The company informed me that I was 7 years ahead of industry thinking.  What???? Ask Toyota engineering if they think this would have been useful in their accelerators and braking systems!  Designing products that create value of the life of the product requires integrated market feedback&#8230; yet like demand information, constipation of essential product performance data remains the bane of industry.  So now we have plants shut down as demand falls off the map for Toyota because products were designed that severely impacted forecasted demand. But that’s okay&#8230; demand wasn&#8217;t forecasted and communicated usefully (refer to first point).  </p>
<p>We can&#8217;t 5S, Six Sigma, or Kaizen event our way out of these fundamental flaws in our supply chain practices&#8230; one-piece flow to supply (inventory) waiting for demand  just doesn&#8217;t appear like progress to me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
