<?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 for Video Blog</title>
	<atom:link href="http://leanlearningcenter.com/videoblog/index.php/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://leanlearningcenter.com/videoblog</link>
	<description>Videos from the Lean Learning Center</description>
	<lastBuildDate>Tue, 27 Dec 2011 18:33:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Promoting Employee Engagaement&#8211;A Cautionary Tale by LInda Budan</title>
		<link>http://leanlearningcenter.com/videoblog/index.php/2011/12/promoting-employee-engagaement-a-cautiounary-tale/comment-page-1/#comment-232</link>
		<dc:creator>LInda Budan</dc:creator>
		<pubDate>Tue, 27 Dec 2011 18:33:32 +0000</pubDate>
		<guid isPermaLink="false">http://leanlearningcenter.com/videoblog/?p=62#comment-232</guid>
		<description>Dear Andy,
Thanks for this emphasis on understanding the current culture.  This seems to be a particular challenging need when working with the &quot;older&quot; boomers.  They&#039;ve &quot;been there done that&quot; and &quot;tasted every flavor of the month&quot;  The key seems to me to be authentic engagement and visible, persistent demonstrated commitment of top leadership.</description>
		<content:encoded><![CDATA[<p>Dear Andy,<br />
Thanks for this emphasis on understanding the current culture.  This seems to be a particular challenging need when working with the &#8220;older&#8221; boomers.  They&#8217;ve &#8220;been there done that&#8221; and &#8220;tasted every flavor of the month&#8221;  The key seems to me to be authentic engagement and visible, persistent demonstrated commitment of top leadership.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Building Effective Escalation with Triggers by Tim Peoples</title>
		<link>http://leanlearningcenter.com/videoblog/index.php/2011/06/building-effective-escalation-with-triggers/comment-page-1/#comment-231</link>
		<dc:creator>Tim Peoples</dc:creator>
		<pubDate>Tue, 28 Jun 2011 12:43:46 +0000</pubDate>
		<guid isPermaLink="false">http://leanlearningcenter.com/videoblog/?p=43#comment-231</guid>
		<description>Andy/Jamie,
Excellent explanation of how the escalation process should work.  I know in my plant we struggle with this quite often.  In certain areas of our operation we have put triggers in place, but what we have missed is the method of raising the trigger and in some instances we&#039;ve missed the &quot;who&quot; that the trigger should be raised.  We have many opportunities to better define and implement triggers within our operation, however, I want to be cautious in doing so not to overwhelm folks which could lead to confusion.</description>
		<content:encoded><![CDATA[<p>Andy/Jamie,<br />
Excellent explanation of how the escalation process should work.  I know in my plant we struggle with this quite often.  In certain areas of our operation we have put triggers in place, but what we have missed is the method of raising the trigger and in some instances we&#8217;ve missed the &#8220;who&#8221; that the trigger should be raised.  We have many opportunities to better define and implement triggers within our operation, however, I want to be cautious in doing so not to overwhelm folks which could lead to confusion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using a Lean Roadmap by Philippe Wattiez</title>
		<link>http://leanlearningcenter.com/videoblog/index.php/2010/11/using-a-lean-roadmap/comment-page-1/#comment-230</link>
		<dc:creator>Philippe Wattiez</dc:creator>
		<pubDate>Wed, 17 Nov 2010 12:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://leanlearningcenter.com/videoblog/?p=37#comment-230</guid>
		<description>Good morning

I like your roadmap system , it gives us the way where we want to go  , 

But could you please let me know more about what you put in the phase 4 : Momentum ?

Kind Regards

Philippe</description>
		<content:encoded><![CDATA[<p>Good morning</p>
<p>I like your roadmap system , it gives us the way where we want to go  , </p>
<p>But could you please let me know more about what you put in the phase 4 : Momentum ?</p>
<p>Kind Regards</p>
<p>Philippe</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using a Lean Roadmap by Limor Riven</title>
		<link>http://leanlearningcenter.com/videoblog/index.php/2010/11/using-a-lean-roadmap/comment-page-1/#comment-227</link>
		<dc:creator>Limor Riven</dc:creator>
		<pubDate>Wed, 17 Nov 2010 09:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://leanlearningcenter.com/videoblog/?p=37#comment-227</guid>
		<description>Hi, 
great video! 
Especially now when we are planning 2011 vision.
As you know we are using your lean roadmap, need to see how can we go from where we are now (probably phase 2) to phase 3, and how we can do it all over the organization.

Thanks!

Limor Riven
Micron FAB 12 Israel 
Lean  Expert
(EX Numonyx)</description>
		<content:encoded><![CDATA[<p>Hi,<br />
great video!<br />
Especially now when we are planning 2011 vision.<br />
As you know we are using your lean roadmap, need to see how can we go from where we are now (probably phase 2) to phase 3, and how we can do it all over the organization.</p>
<p>Thanks!</p>
<p>Limor Riven<br />
Micron FAB 12 Israel<br />
Lean  Expert<br />
(EX Numonyx)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reflection through After Action Reviews by Roxanne</title>
		<link>http://leanlearningcenter.com/videoblog/index.php/2010/10/reflection-through-after-action-reviews/comment-page-1/#comment-182</link>
		<dc:creator>Roxanne</dc:creator>
		<pubDate>Tue, 12 Oct 2010 14:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://leanlearningcenter.com/videoblog/?p=32#comment-182</guid>
		<description>Excellent video. I liked the repetition and reiterations. And I absolutely loved the pop-up summaries in the video track bar. I think more sample answers would be helpful.
Thanks,
Roxanne</description>
		<content:encoded><![CDATA[<p>Excellent video. I liked the repetition and reiterations. And I absolutely loved the pop-up summaries in the video track bar. I think more sample answers would be helpful.<br />
Thanks,<br />
Roxanne</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Engaging Through Daily Huddles by Jamie Flinchbaugh</title>
		<link>http://leanlearningcenter.com/videoblog/index.php/2010/09/engaging-through-daily-huddles/comment-page-1/#comment-175</link>
		<dc:creator>Jamie Flinchbaugh</dc:creator>
		<pubDate>Mon, 13 Sep 2010 14:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://leanlearningcenter.com/videoblog/?p=28#comment-175</guid>
		<description>Ed, obviously we had limited time, as we could probably talk about this for an hour, but those are great adds. 

Accountability I think is particularly crucial. By having a cadence, coupled with the visibility of a visual board, things that are not happening should be surfaced, but most importantly surfaced quickly. It&#039;s much easier to manage accountability when the feedback is &quot;that new tool you promised yesterday didn&#039;t arrive&quot; versus &quot;you never do stuff on time.&quot; The latter is less effective. To use your words, Ed, the huddle can add cadence to accountability. 

Jamie</description>
		<content:encoded><![CDATA[<p>Ed, obviously we had limited time, as we could probably talk about this for an hour, but those are great adds. </p>
<p>Accountability I think is particularly crucial. By having a cadence, coupled with the visibility of a visual board, things that are not happening should be surfaced, but most importantly surfaced quickly. It&#8217;s much easier to manage accountability when the feedback is &#8220;that new tool you promised yesterday didn&#8217;t arrive&#8221; versus &#8220;you never do stuff on time.&#8221; The latter is less effective. To use your words, Ed, the huddle can add cadence to accountability. </p>
<p>Jamie</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Engaging Through Daily Huddles by Ed Sosnowski</title>
		<link>http://leanlearningcenter.com/videoblog/index.php/2010/09/engaging-through-daily-huddles/comment-page-1/#comment-149</link>
		<dc:creator>Ed Sosnowski</dc:creator>
		<pubDate>Wed, 08 Sep 2010 20:05:58 +0000</pubDate>
		<guid isPermaLink="false">http://leanlearningcenter.com/videoblog/?p=28#comment-149</guid>
		<description>Jamie &amp; Andy,

Thanks for the post, I liked this one and wanted to say that I find the daily huddle really useful in a project environment as well.  For a recent launch of a new product we used daily huddles (supported with some technology) and found it very successful.  A few things that I didn&#039;t hear in your video is cadence and accountability.  The daily meetings set a cadence in a project environment such that tasks were getting an improved focus and closed much quicker.  The team also started to form a bond and became very candid with each other.  If someone promised that something would get done and it didn&#039;t they would put pressure on each other to get it done.  This was a far greater impact than I thought it would be in that I saw team members who were by all accounts weak in the beginning of the project holding their own and functioning very well within the team when the accountability was to their teammates.  As you noted, surfacing issues, resolving them outside the meeting and then the entire group reflecting on those lessons learned is very important as well.  Thanks again for the video!</description>
		<content:encoded><![CDATA[<p>Jamie &amp; Andy,</p>
<p>Thanks for the post, I liked this one and wanted to say that I find the daily huddle really useful in a project environment as well.  For a recent launch of a new product we used daily huddles (supported with some technology) and found it very successful.  A few things that I didn&#8217;t hear in your video is cadence and accountability.  The daily meetings set a cadence in a project environment such that tasks were getting an improved focus and closed much quicker.  The team also started to form a bond and became very candid with each other.  If someone promised that something would get done and it didn&#8217;t they would put pressure on each other to get it done.  This was a far greater impact than I thought it would be in that I saw team members who were by all accounts weak in the beginning of the project holding their own and functioning very well within the team when the accountability was to their teammates.  As you noted, surfacing issues, resolving them outside the meeting and then the entire group reflecting on those lessons learned is very important as well.  Thanks again for the video!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Engaging Through Daily Huddles by Jamie Flinchbaugh</title>
		<link>http://leanlearningcenter.com/videoblog/index.php/2010/09/engaging-through-daily-huddles/comment-page-1/#comment-147</link>
		<dc:creator>Jamie Flinchbaugh</dc:creator>
		<pubDate>Wed, 08 Sep 2010 10:47:46 +0000</pubDate>
		<guid isPermaLink="false">http://leanlearningcenter.com/videoblog/?p=28#comment-147</guid>
		<description>Thanks for the responses folks. 

Dan, thanks for your question. Through the scoreboard, there should be a process and a place for capturing the problems that require attention. This should be an ongoing process. Unless a problem is just a lack of information that you can resolve by sharing the information, you are not likely going to do the problem solving in the huddle. 

The team leader, to establish the right behaviors, should always thank people for surfacing problems. This is a behavior that is often not natural, because people associate problems with bad news and no one wants to be the bearer of bad news. We need every opportunity we can find to encourage people to surface problems. You can&#039;t solve the problems that haven&#039;t been surfaced.</description>
		<content:encoded><![CDATA[<p>Thanks for the responses folks. </p>
<p>Dan, thanks for your question. Through the scoreboard, there should be a process and a place for capturing the problems that require attention. This should be an ongoing process. Unless a problem is just a lack of information that you can resolve by sharing the information, you are not likely going to do the problem solving in the huddle. </p>
<p>The team leader, to establish the right behaviors, should always thank people for surfacing problems. This is a behavior that is often not natural, because people associate problems with bad news and no one wants to be the bearer of bad news. We need every opportunity we can find to encourage people to surface problems. You can&#8217;t solve the problems that haven&#8217;t been surfaced.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Engaging Through Daily Huddles by Ram</title>
		<link>http://leanlearningcenter.com/videoblog/index.php/2010/09/engaging-through-daily-huddles/comment-page-1/#comment-142</link>
		<dc:creator>Ram</dc:creator>
		<pubDate>Tue, 07 Sep 2010 15:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://leanlearningcenter.com/videoblog/?p=28#comment-142</guid>
		<description>I liked this video and glad that you covered the importance of connecting to &quot;purpose&quot; and the ability to explore on what I call the &quot;intangibles&quot; based on team member observations and perceptions as opposed to data</description>
		<content:encoded><![CDATA[<p>I liked this video and glad that you covered the importance of connecting to &#8220;purpose&#8221; and the ability to explore on what I call the &#8220;intangibles&#8221; based on team member observations and perceptions as opposed to data</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Engaging Through Daily Huddles by Dan Markovitz</title>
		<link>http://leanlearningcenter.com/videoblog/index.php/2010/09/engaging-through-daily-huddles/comment-page-1/#comment-141</link>
		<dc:creator>Dan Markovitz</dc:creator>
		<pubDate>Tue, 07 Sep 2010 14:50:09 +0000</pubDate>
		<guid isPermaLink="false">http://leanlearningcenter.com/videoblog/?p=28#comment-141</guid>
		<description>Thanks for the excellent video, guys. I enjoyed it, but I do have a question: let&#039;s say that in the huddle someone surfaces a problem that can&#039;t be solved in the 15 minutes. What happens then? (Presumably postpone it.) And what should the team leader say?</description>
		<content:encoded><![CDATA[<p>Thanks for the excellent video, guys. I enjoyed it, but I do have a question: let&#8217;s say that in the huddle someone surfaces a problem that can&#8217;t be solved in the 15 minutes. What happens then? (Presumably postpone it.) And what should the team leader say?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

