<?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: Gemba</title>
	<atom:link href="http://www.velaction.com/gemba/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.velaction.com/gemba/</link>
	<description>Everything Lean for Leaders and their Teams</description>
	<lastBuildDate>Thu, 02 Feb 2012 13:02:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Jeff Hajek</title>
		<link>http://www.velaction.com/gemba/comment-page-1/#comment-60226</link>
		<dc:creator>Jeff Hajek</dc:creator>
		<pubDate>Fri, 16 Dec 2011 15:46:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.velaction.com/?p=1371#comment-60226</guid>
		<description>Antonio,

Good point. There are lots of different ways to label the same thing. The important thing, though, is that the terminology is used consistently throughout the organization to prevent confusion.

To that point, I use the term &quot;process walk&quot; differently than &quot;going to gemba&quot;. For me, it is a thorough review of an operation during an improvement project. It involves detailed documentation and observation. Going to gemba, in my mind, is more of a quick check to avoid discussing something that can be observed firsthand, or simply a leadership style of being present in an operation.

Thanks for the comment.
Jeff</description>
		<content:encoded><![CDATA[<p>Antonio,</p>
<p>Good point. There are lots of different ways to label the same thing. The important thing, though, is that the terminology is used consistently throughout the organization to prevent confusion.</p>
<p>To that point, I use the term &#8220;process walk&#8221; differently than &#8220;going to gemba&#8221;. For me, it is a thorough review of an operation during an improvement project. It involves detailed documentation and observation. Going to gemba, in my mind, is more of a quick check to avoid discussing something that can be observed firsthand, or simply a leadership style of being present in an operation.</p>
<p>Thanks for the comment.<br />
Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antonio Souza Jr</title>
		<link>http://www.velaction.com/gemba/comment-page-1/#comment-60172</link>
		<dc:creator>Antonio Souza Jr</dc:creator>
		<pubDate>Fri, 16 Dec 2011 14:06:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.velaction.com/?p=1371#comment-60172</guid>
		<description>Hello Folks,

In Xerox we have a strong Lean Six Sigma culture. Go to GEMBA for us is normally referred as &quot;Walk the Process&quot;.

Regards,

Antonio Souza Jr</description>
		<content:encoded><![CDATA[<p>Hello Folks,</p>
<p>In Xerox we have a strong Lean Six Sigma culture. Go to GEMBA for us is normally referred as &#8220;Walk the Process&#8221;.</p>
<p>Regards,</p>
<p>Antonio Souza Jr</p>
]]></content:encoded>
	</item>
</channel>
</rss>

