﻿<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Agile Manufacturing Update: Recent Comments</title><link>http://agileviews.chagrinriverconsulting.com</link><description /><generator>Quick Blogcast</generator><lastBuildDate>Mon, 06 Feb 2012 01:20:06 GMT</lastBuildDate><item><title>Comment on Book Review:  Andy and Me - Crisis and Transformation</title><link>http://agileviews.chagrinriverconsulting.com/2010/09/19/book-review--andy-and-me--crisis-and-transformation.aspx#comment-15580859</link><dc:creator>Kirsten Moen</dc:creator><description>&lt;span&gt; &lt;/span&gt;I like the article.  Thank you</description><guid isPermaLink="true">http://agileviews.chagrinriverconsulting.com/2010/09/19/book-review--andy-and-me--crisis-and-transformation.aspx#comment-15580859</guid><pubDate>Fri, 20 Jan 2012 05:49:06 GMT</pubDate></item><item><title>Comment on Progressive Lean:  The Overall Idea of It</title><link>http://agileviews.chagrinriverconsulting.com/2011/09/24/progressive-lean--sort-and-shine.aspx#comment-11886137</link><dc:creator>Karen Wilhelm</dc:creator><description>&lt;span&gt; &lt;/span&gt;I agree - you can't have op ex without organization. When you ask "what's really going on here?" about a process or problem, you can't begin to find out until the clutter is out of the way, things are where they need to be ("why does this process take so long?") and all the dirt is gone ("Who knew this leak was here?")&lt;br /&gt;
&lt;br /&gt;
As for all the approaches - whole place or "most pain," it comes down to the will to improve, all the time, forever. You've already shown that it's rare and frustrating that people can't see it through. But we've all lost energy about something we've tried to change in ourselves or our organizations, so we can't really place blame.&lt;br /&gt;
&lt;br /&gt;
All in all, I agree with much of what you are saying in your approach. Looking forward to hearing the rest of the story.</description><guid isPermaLink="true">http://agileviews.chagrinriverconsulting.com/2011/09/24/progressive-lean--sort-and-shine.aspx#comment-11886137</guid><pubDate>Mon, 26 Sep 2011 13:34:38 GMT</pubDate></item><item><title>Comment on Progressive Lean:  The Overall Idea of It</title><link>http://agileviews.chagrinriverconsulting.com/2011/09/24/progressive-lean--sort-and-shine.aspx#comment-11885131</link><dc:creator>George Bohan</dc:creator><description>&lt;span&gt;Thanks for the comment, Karen.&amp;nbsp; (You were probably thinking I was done with this blogging gig!)&lt;br /&gt;
&lt;br /&gt;
The premise of Progressive Lean is that you can't have operational excellence without organization.&amp;nbsp; Period.&amp;nbsp; So, while we don't altogether eschew problem solving or even conducting action workshops that focus on specific problems, we say, "We're going to get the &lt;em&gt;entire&lt;/em&gt; &lt;em&gt;place&lt;/em&gt; Sorted and Shined, and show we can sustain it.&amp;nbsp; &lt;em&gt;Then&lt;/em&gt; we're going to move on to Straighten and See (Visual Controls) across the entire plant and show we can sustain &lt;em&gt;that.&amp;nbsp; &lt;/em&gt;Then on to the other stuff."&lt;br /&gt;
&lt;br /&gt;
My issue with the "most pain" approach is that, once that pain is gone, they tend to lose energy for more comprehensive efforts.&amp;nbsp; Same way that smokers and obese people get their stents put in, then start right back to two packs and a dozen donuts a day as soon as they're back home.&lt;br /&gt;
&lt;/span&gt;</description><guid isPermaLink="true">http://agileviews.chagrinriverconsulting.com/2011/09/24/progressive-lean--sort-and-shine.aspx#comment-11885131</guid><pubDate>Mon, 26 Sep 2011 12:28:47 GMT</pubDate></item><item><title>Comment on Progressive Lean:  The Overall Idea of It</title><link>http://agileviews.chagrinriverconsulting.com/2011/09/24/progressive-lean--sort-and-shine.aspx#comment-11864266</link><dc:creator>Karen Wilhelm</dc:creator><description>&lt;span&gt; &lt;/span&gt;The deterioration after 5S and improvement events is the most common problem with lean that I hear in smaller shops -- big ones too, for that matter. Even starting with leadership, who we know have to buy in, seems to fall flat when push comes to shove. Event-based lean can get the ball rolling, but often it falls apart, or the focus is too much on the number of events or the tools. I wonder if you have tried the "most pain" approach (undoubtedly you have) with the continuous problem-solving mindset described in Spear's "The High-Velocity Edge" (formerly titled "Chasing the Rabbit") and "Toyota Kata" by Mike Rother. Mike, in particular, gives the "What do I do on Monday" answer along with the big one on culture. -- He also has a bunch of free stuff on his website that is perhaps more practical, just search Toyota Kata. Art Smalley describes on his website how the genesis of continuous improvement at the Toyota Engine Plant was the problem of uptime. Each and every little problem was solved with a focus on keeping the right machines running the right amount of time to insure the necessary throughput. A progressive 5S approach at this point can be the way to uncover the root causes of downtime. Whatever the owner's pain, that's where to start. &lt;br /&gt;
&lt;br /&gt;
How do you usually choose the starting point for applying Progressive 5S? Is it similar?</description><guid isPermaLink="true">http://agileviews.chagrinriverconsulting.com/2011/09/24/progressive-lean--sort-and-shine.aspx#comment-11864266</guid><pubDate>Sun, 25 Sep 2011 14:01:25 GMT</pubDate></item><item><title>Comment on How to Keep Lean Going: Pull Systems</title><link>http://agileviews.chagrinriverconsulting.com/2009/12/02/how-to-implement-lean-manufacturing-part-six-implementation-v-pull-systems.aspx#comment-11593835</link><dc:creator>Ben Benjabutr</dc:creator><description>&lt;span&gt; &lt;/span&gt;I think VSM is a very important tool to visualize current system and let people see where pull system should be in place.</description><guid isPermaLink="true">http://agileviews.chagrinriverconsulting.com/2009/12/02/how-to-implement-lean-manufacturing-part-six-implementation-v-pull-systems.aspx#comment-11593835</guid><pubDate>Mon, 05 Sep 2011 03:12:17 GMT</pubDate></item><item><title>Comment on Why do they call it "lean manufacturing"?</title><link>http://agileviews.chagrinriverconsulting.com/2007/08/04/why-call-it-lean.aspx#comment-11457619</link><dc:creator>Jonah Frye</dc:creator><description>&lt;span&gt; &lt;/span&gt;I found your blog while looking for reputation management sites which is odd, but I'm glad I did, this was a fun read and a good break in my day! Going to look through a few other posts of yours now.</description><guid isPermaLink="true">http://agileviews.chagrinriverconsulting.com/2007/08/04/why-call-it-lean.aspx#comment-11457619</guid><pubDate>Wed, 24 Aug 2011 17:31:38 GMT</pubDate></item><item><title>Comment on New Approach to Implementing Lean</title><link>http://agileviews.chagrinriverconsulting.com/2011/07/04/new-approach-to-implementing-lean.aspx#comment-11232836</link><dc:creator>Clay Williams</dc:creator><description>&lt;span&gt; &lt;/span&gt;Love this approach, can't wait to introduce it to our shop. We have always tried to make the "Solve and Simplify" approach a central part of our designs. Do you have any thoughts on a way to systematically solve and simplify problems?</description><guid isPermaLink="true">http://agileviews.chagrinriverconsulting.com/2011/07/04/new-approach-to-implementing-lean.aspx#comment-11232836</guid><pubDate>Thu, 28 Jul 2011 22:03:39 GMT</pubDate></item><item><title>Comment on I'm gonna be a star!</title><link>http://agileviews.chagrinriverconsulting.com/2010/04/01/im-gonna-be-a-star.aspx#comment-11076436</link><dc:creator>Wrelaymmemibe</dc:creator><description>&lt;span&gt; &lt;/span&gt;I just book marked your blog on Digg and StumbleUpon.I enjoy reading your commentaries.</description><guid isPermaLink="true">http://agileviews.chagrinriverconsulting.com/2010/04/01/im-gonna-be-a-star.aspx#comment-11076436</guid><pubDate>Mon, 04 Jul 2011 12:21:18 GMT</pubDate></item><item><title>Comment on New Idea for the Blog: Book Reviews</title><link>http://agileviews.chagrinriverconsulting.com/2010/08/22/new-idea-for-the-blog-book-reviews.aspx#comment-10913484</link><dc:creator>David</dc:creator><description>Good blog, wish I would of found this earlier, could have saved my money on many books. My bible is "Out of Crisis" by Deming. We just need the right people to read the right books! So keep it up :)</description><guid isPermaLink="true">http://agileviews.chagrinriverconsulting.com/2010/08/22/new-idea-for-the-blog-book-reviews.aspx#comment-10913484</guid><pubDate>Wed, 29 Jun 2011 03:27:02 GMT</pubDate></item><item><title>Comment on How to Get Started: Part Six - Implementation IV: Value Stream Mapping 5 - Current State Map (continued yet again)</title><link>http://agileviews.chagrinriverconsulting.com/2009/11/10/how-to-get-started-part-six--implementation-iv-value-stream-mapping-5--current-state-map-continued-yet-again.aspx#comment-2559132</link><dc:creator>hazel wagner</dc:creator><description>There are so many productive ways to get brainstorming going in addition to one person writing on a flip chart.  Take a look at the many suggestions on &lt;a href="http://www.brainstorming-that-works.com"&gt;www.brainstorming-that-works.com&lt;/a&gt; or read the free chapter at &lt;a href="http://www.askhazelwagner.com"&gt;www.askhazelwagner.com&lt;/a&gt;. &lt;br&gt; &lt;br&gt; I wish you great ideas at lightning speed,&lt;br&gt;Hazel</description><guid isPermaLink="true">http://agileviews.chagrinriverconsulting.com/2009/11/10/how-to-get-started-part-six--implementation-iv-value-stream-mapping-5--current-state-map-continued-yet-again.aspx#comment-2559132</guid><pubDate>Wed, 11 Nov 2009 15:28:11 GMT</pubDate></item></channel></rss>
