<?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: Obstacles vs. Lists of Tools</title>
	<atom:link href="http://theleanthinker.com/2012/10/22/obstacles-vs-lists-of-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://theleanthinker.com/2012/10/22/obstacles-vs-lists-of-tools/</link>
	<description>Thoughts and insights from the shop floor.</description>
	<lastBuildDate>Tue, 21 May 2013 16:41:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: mark greenhouse</title>
		<link>http://theleanthinker.com/2012/10/22/obstacles-vs-lists-of-tools/comment-page-1/#comment-36914</link>
		<dc:creator>mark greenhouse</dc:creator>
		<pubDate>Wed, 24 Oct 2012 08:33:21 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=2070#comment-36914</guid>
		<description><![CDATA[Mark,

I can’t speak for to many others but the practice of teaching variation is key to understanding Lean and probably a great many other frameworks for improvement.

In our “process” we start by getting staff to define what it is they are trying to achieve, this allows them to own this. In the manufacturing teams this is often straight forward, in the knowledge sector, individuals or small teams are often working on a series of different customer requirements for different clients at the same time. 

Focussing on these requirements, they often find they are the same across the many clients they have, just dispersed over a period of time.

Having common outputs then allows us to build the Value Streams and the variation in processes used by different teams or for different clients is exposed. 

At this point, in our experience, individuals and teams are much more comfortable asking the question “Why do we use different process, if the requirement/output is the same?” 

Where the requirements are different the question is then around suitability of the process for the output.

Finding the reason for the variation helps in identifying solutions and ultimately then, which tools and techniques are suitable.

regards,
Mark Greenhouse]]></description>
		<content:encoded><![CDATA[<p>Mark,</p>
<p>I can’t speak for to many others but the practice of teaching variation is key to understanding Lean and probably a great many other frameworks for improvement.</p>
<p>In our “process” we start by getting staff to define what it is they are trying to achieve, this allows them to own this. In the manufacturing teams this is often straight forward, in the knowledge sector, individuals or small teams are often working on a series of different customer requirements for different clients at the same time. </p>
<p>Focussing on these requirements, they often find they are the same across the many clients they have, just dispersed over a period of time.</p>
<p>Having common outputs then allows us to build the Value Streams and the variation in processes used by different teams or for different clients is exposed. </p>
<p>At this point, in our experience, individuals and teams are much more comfortable asking the question “Why do we use different process, if the requirement/output is the same?” </p>
<p>Where the requirements are different the question is then around suitability of the process for the output.</p>
<p>Finding the reason for the variation helps in identifying solutions and ultimately then, which tools and techniques are suitable.</p>
<p>regards,<br />
Mark Greenhouse</p>
]]></content:encoded>
	</item>
</channel>
</rss>
