<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Of Team Size, Social Loafing and Lack of Direction</title>
	<atom:link href="http://kaizenfieldbook.com/marksblog/archives/1112/feed" rel="self" type="application/rss+xml" />
	<link>http://kaizenfieldbook.com/marksblog/archives/1112?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=of-team-size-social-loafing-and-lack-of-direction</link>
	<description>Lean stories, lessons and reflections</description>
	<lastBuildDate>Fri, 18 May 2012 00:14:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: leansim</title>
		<link>http://kaizenfieldbook.com/marksblog/archives/1112/comment-page-1#comment-754</link>
		<dc:creator>leansim</dc:creator>
		<pubDate>Thu, 01 Jul 2010 23:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://kaizenfieldbook.com/marksblog/?p=1112#comment-754</guid>
		<description>I like small, intimate groups, especially useful for one-on-one training. Depending on the scope of the kaizen, I prefer a facilitator and 4 or 5 others. Each person can be involved in the problem at hand.
Of course, when doing large scale training, you can run great simulations with 10 to 20 people competing  in teams. Due to the &quot;loafing&quot; aspect you mention, this is works best with generic overview style training.</description>
		<content:encoded><![CDATA[<p>I like small, intimate groups, especially useful for one-on-one training. Depending on the scope of the kaizen, I prefer a facilitator and 4 or 5 others. Each person can be involved in the problem at hand.<br />
Of course, when doing large scale training, you can run great simulations with 10 to 20 people competing  in teams. Due to the &#8220;loafing&#8221; aspect you mention, this is works best with generic overview style training.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: markrhamel</title>
		<link>http://kaizenfieldbook.com/marksblog/archives/1112/comment-page-1#comment-750</link>
		<dc:creator>markrhamel</dc:creator>
		<pubDate>Tue, 29 Jun 2010 17:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://kaizenfieldbook.com/marksblog/?p=1112#comment-750</guid>
		<description>Hi Matt,

Thanks for the comment and the sharing of your experience!

Team size is a fairly basic concept, but it gets complicated when we don&#039;t do a good job scoping the target or carefully getting proper team representation without including &quot;everyone.&quot; Team selection is critical within a number of different venues and vehicles - strategy deployment sessions, kaizen events, mini-kaizens, daily kaizen activities, etc.

Best regards,
Mark</description>
		<content:encoded><![CDATA[<p>Hi Matt,</p>
<p>Thanks for the comment and the sharing of your experience!</p>
<p>Team size is a fairly basic concept, but it gets complicated when we don&#8217;t do a good job scoping the target or carefully getting proper team representation without including &#8220;everyone.&#8221; Team selection is critical within a number of different venues and vehicles &#8211; strategy deployment sessions, kaizen events, mini-kaizens, daily kaizen activities, etc.</p>
<p>Best regards,<br />
Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Wrye</title>
		<link>http://kaizenfieldbook.com/marksblog/archives/1112/comment-page-1#comment-749</link>
		<dc:creator>Matt Wrye</dc:creator>
		<pubDate>Tue, 29 Jun 2010 17:13:35 +0000</pubDate>
		<guid isPermaLink="false">http://kaizenfieldbook.com/marksblog/?p=1112#comment-749</guid>
		<description>Mark, you are right on with this.  I have seen teams get too large many times.  I have coached managers in selecting appropriate teams for the kaizen events but sometimes they go against the advice, trying to get everyone involved.  Instead, too many people end up standing around and you are trying to keep them busy or the group is too big and not as many ideas are shared because most employees don&#039;t want to share in front of a big group.

I really like you suggestion that if the scope is too big, have a core team and then smaller subteams.  I have seen that work.</description>
		<content:encoded><![CDATA[<p>Mark, you are right on with this.  I have seen teams get too large many times.  I have coached managers in selecting appropriate teams for the kaizen events but sometimes they go against the advice, trying to get everyone involved.  Instead, too many people end up standing around and you are trying to keep them busy or the group is too big and not as many ideas are shared because most employees don&#8217;t want to share in front of a big group.</p>
<p>I really like you suggestion that if the scope is too big, have a core team and then smaller subteams.  I have seen that work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Of Team Size, Social Loafing and Lack of Direction &#124; Gemba Tales -- Topsy.com</title>
		<link>http://kaizenfieldbook.com/marksblog/archives/1112/comment-page-1#comment-736</link>
		<dc:creator>Tweets that mention Of Team Size, Social Loafing and Lack of Direction &#124; Gemba Tales -- Topsy.com</dc:creator>
		<pubDate>Sat, 26 Jun 2010 12:37:54 +0000</pubDate>
		<guid isPermaLink="false">http://kaizenfieldbook.com/marksblog/?p=1112#comment-736</guid>
		<description>[...] This post was mentioned on Twitter by Mark Hamel, Tim McMahon. Tim McMahon said: RT @MarkRHamel: Of Team Size, Social Loafing and Lack of Direction http://ow.ly/17SZHZ [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Mark Hamel, Tim McMahon. Tim McMahon said: RT @MarkRHamel: Of Team Size, Social Loafing and Lack of Direction <a href="http://ow.ly/17SZHZ" rel="nofollow">http://ow.ly/17SZHZ</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

