<?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: A &#8220;Problems First&#8221; Culture</title>
	<atom:link href="http://theleanthinker.com/2009/11/13/a-problems-first-culture/feed/" rel="self" type="application/rss+xml" />
	<link>http://theleanthinker.com/2009/11/13/a-problems-first-culture/</link>
	<description>Thoughts and insights from the shop floor.</description>
	<lastBuildDate>Fri, 18 May 2012 16:29:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Riegholt</title>
		<link>http://theleanthinker.com/2009/11/13/a-problems-first-culture/comment-page-1/#comment-34808</link>
		<dc:creator>Riegholt</dc:creator>
		<pubDate>Sat, 08 May 2010 19:22:09 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=1006#comment-34808</guid>
		<description>Browsing your blog using the tag leadership, I came across this article. 

Though I must have read it in November as well, it really hits me this time.

Gonna think of ways to put the lessons in practice.

Thanks.</description>
		<content:encoded><![CDATA[<p>Browsing your blog using the tag leadership, I came across this article. </p>
<p>Though I must have read it in November as well, it really hits me this time.</p>
<p>Gonna think of ways to put the lessons in practice.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curious Cat Management Improvement Blog &#187; Management Improvement Carnival #82</title>
		<link>http://theleanthinker.com/2009/11/13/a-problems-first-culture/comment-page-1/#comment-34310</link>
		<dc:creator>Curious Cat Management Improvement Blog &#187; Management Improvement Carnival #82</dc:creator>
		<pubDate>Sun, 22 Nov 2009 19:23:36 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=1006#comment-34310</guid>
		<description>[...] A Problems First Culture by Mark Rosenthal &#8220;&#8216;Problems first&#8217; is one of the mantras used by Phil Jenkinson, the CEO character in The Lean Manager by Michael and Freddy Ballé. Now that I have had a few weeks to let it sink in and synthesize with my mental models, I am seeing a concept that is so fundamental I would think it would be hammered into students in every management and leadership course taught in the world.’&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] A Problems First Culture by Mark Rosenthal &#8220;&#8216;Problems first&#8217; is one of the mantras used by Phil Jenkinson, the CEO character in The Lean Manager by Michael and Freddy Ballé. Now that I have had a few weeks to let it sink in and synthesize with my mental models, I am seeing a concept that is so fundamental I would think it would be hammered into students in every management and leadership course taught in the world.’&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Il meglio della blogosfera lean #13 — Encob Blog</title>
		<link>http://theleanthinker.com/2009/11/13/a-problems-first-culture/comment-page-1/#comment-34219</link>
		<dc:creator>Il meglio della blogosfera lean #13 — Encob Blog</dc:creator>
		<pubDate>Sat, 21 Nov 2009 07:35:52 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=1006#comment-34219</guid>
		<description>[...] A &#8220;Problems First&#8221; Culture dal blog The Lean Thinker di Mark Rosenthal, dove l&#8217;autore spiega la cultura di evidenziare e risolvere i problemi e non nasconderli&#8230; (traduzione automatica) [...]</description>
		<content:encoded><![CDATA[<p>[...] A &#8220;Problems First&#8221; Culture dal blog The Lean Thinker di Mark Rosenthal, dove l&#8217;autore spiega la cultura di evidenziare e risolvere i problemi e non nasconderli&#8230; (traduzione automatica) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Buck</title>
		<link>http://theleanthinker.com/2009/11/13/a-problems-first-culture/comment-page-1/#comment-34106</link>
		<dc:creator>Brian Buck</dc:creator>
		<pubDate>Wed, 18 Nov 2009 16:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=1006#comment-34106</guid>
		<description>Mark, this is awesome.</description>
		<content:encoded><![CDATA[<p>Mark, this is awesome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Ballé</title>
		<link>http://theleanthinker.com/2009/11/13/a-problems-first-culture/comment-page-1/#comment-34101</link>
		<dc:creator>Michael Ballé</dc:creator>
		<pubDate>Wed, 18 Nov 2009 13:36:21 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=1006#comment-34101</guid>
		<description>Mark,

as usual, you&#039;re hitting it right on the nail. I believe &quot;Problems First&quot; is one of the largest contributions of Toyota&#039;s version of lean to the business world. It&#039;s link to their rather curious assertion that TPS is nothing other than applying the scientific mindset to business problems.

Indeed, what I&#039;ve always found the most counter-intuitive in scientific reasoning is the focus on anamolaies: on events which disconfirm our beliefs rather than reinforce them. This requires real mental effort and discipline because our brains work the other way around, by selecting information which reinforces (reassures, etc.) our beliefs.

We naturally look for the lost key where the light is, but looking for anomalies is about seeking out areas where reality does something different than we would have thought: areas where we have something to learn.

Problems first is the practical everyday reflection of this attitude: looking for areas where things don&#039;t go the way they ought to, or the way we think they should. These events are key opportunities to learn and to enrich our mental models.

However, as with scientific thinking, problems first is very demanding beyond the psychological unease of stepping where angels fear to tread: where we are wrong.

Problems first means we 1) are clear on what should normally happen, which means that we have an explicit theory (a &quot;standard&quot; in lean parlance) of the way things work and 2) the ability to spot the deviation (hence the focus on visual management). Both skills are, well, skills, and hard to acquire:
1) expliciting theories as work standards and standaridzed work
2) visualizing process in a way that reveals problems
is the bedrock of what is unique in lean practice (as opposed to other problem solving methods such as brainstorming, thinking hats, six sigma, etc.)

Finally, I believe that lean is truly empowering in the sense of teaching people to solve their own problems and, in the process, making better business decisions. So yes, I have to agree that &quot;problems first&quot; is one of the key messages of the book, and I trust, one of the key contributions of lean to management,

Do you agree?</description>
		<content:encoded><![CDATA[<p>Mark,</p>
<p>as usual, you&#8217;re hitting it right on the nail. I believe &#8220;Problems First&#8221; is one of the largest contributions of Toyota&#8217;s version of lean to the business world. It&#8217;s link to their rather curious assertion that TPS is nothing other than applying the scientific mindset to business problems.</p>
<p>Indeed, what I&#8217;ve always found the most counter-intuitive in scientific reasoning is the focus on anamolaies: on events which disconfirm our beliefs rather than reinforce them. This requires real mental effort and discipline because our brains work the other way around, by selecting information which reinforces (reassures, etc.) our beliefs.</p>
<p>We naturally look for the lost key where the light is, but looking for anomalies is about seeking out areas where reality does something different than we would have thought: areas where we have something to learn.</p>
<p>Problems first is the practical everyday reflection of this attitude: looking for areas where things don&#8217;t go the way they ought to, or the way we think they should. These events are key opportunities to learn and to enrich our mental models.</p>
<p>However, as with scientific thinking, problems first is very demanding beyond the psychological unease of stepping where angels fear to tread: where we are wrong.</p>
<p>Problems first means we 1) are clear on what should normally happen, which means that we have an explicit theory (a &#8220;standard&#8221; in lean parlance) of the way things work and 2) the ability to spot the deviation (hence the focus on visual management). Both skills are, well, skills, and hard to acquire:<br />
1) expliciting theories as work standards and standaridzed work<br />
2) visualizing process in a way that reveals problems<br />
is the bedrock of what is unique in lean practice (as opposed to other problem solving methods such as brainstorming, thinking hats, six sigma, etc.)</p>
<p>Finally, I believe that lean is truly empowering in the sense of teaching people to solve their own problems and, in the process, making better business decisions. So yes, I have to agree that &#8220;problems first&#8221; is one of the key messages of the book, and I trust, one of the key contributions of lean to management,</p>
<p>Do you agree?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Rosenthal</title>
		<link>http://theleanthinker.com/2009/11/13/a-problems-first-culture/comment-page-1/#comment-34047</link>
		<dc:creator>Mark Rosenthal</dc:creator>
		<pubDate>Mon, 16 Nov 2009 22:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=1006#comment-34047</guid>
		<description>On the other hand, what would happen if your lean project board were run like a (world class) assembly line?
What would an andon call look like?
When would it be triggered?
What would be the process for escalation, clearing, and solving the problem?</description>
		<content:encoded><![CDATA[<p>On the other hand, what would happen if your lean project board were run like a (world class) assembly line?<br />
What would an andon call look like?<br />
When would it be triggered?<br />
What would be the process for escalation, clearing, and solving the problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Fernandez</title>
		<link>http://theleanthinker.com/2009/11/13/a-problems-first-culture/comment-page-1/#comment-34035</link>
		<dc:creator>Jim Fernandez</dc:creator>
		<pubDate>Mon, 16 Nov 2009 15:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=1006#comment-34035</guid>
		<description>This is very a interesting concept.  I never really thought about it until you pointed it out.  

We have a Lean project status board.  When my boss notices something in red he says, what are you going to do about this?  And I respond with, I will push harder.  I will do more of what I have been doing.  I will meet more often with the person responsible for this task and I will push on him.  

So now I wonder what if the assembly line were managed like my Lean project board,  and a problem arose.  I guess you&#039;d have a bunch of supervisors and managers standing there with their arms folded expecting the assembly line worker to &quot;try harder&quot;.

Thank you for your insight.</description>
		<content:encoded><![CDATA[<p>This is very a interesting concept.  I never really thought about it until you pointed it out.  </p>
<p>We have a Lean project status board.  When my boss notices something in red he says, what are you going to do about this?  And I respond with, I will push harder.  I will do more of what I have been doing.  I will meet more often with the person responsible for this task and I will push on him.  </p>
<p>So now I wonder what if the assembly line were managed like my Lean project board,  and a problem arose.  I guess you&#8217;d have a bunch of supervisors and managers standing there with their arms folded expecting the assembly line worker to &#8220;try harder&#8221;.</p>
<p>Thank you for your insight.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

