<?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"
	>
<channel>
	<title>Comments on: The Seventh Flow</title>
	<atom:link href="http://theleanthinker.com/2007/10/21/the-seventh-flow/feed/" rel="self" type="application/rss+xml" />
	<link>http://theleanthinker.com/2007/10/21/the-seventh-flow/</link>
	<description>Thoughts and insights from the shop floor.</description>
	<pubDate>Fri, 29 Aug 2008 01:58:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Mark</title>
		<link>http://theleanthinker.com/2007/10/21/the-seventh-flow/#comment-105</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Tue, 23 Oct 2007 00:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/2007/10/21/the-seventh-flow/#comment-105</guid>
		<description>Brian - 
From what I was taught, the "Seven Flows" all relate to the production process (whether manufacturing or administrative information processing). 

Design engineering certainly has an impact, and I think it is a major player in this flow. That is because I think design changes are one possible countermeasure that this flow could deliver.

However, I do not believe Nakao-san intends "The flow of engineering" to be the design/development process itself.

That being said, design engineering *is* a production process, and all of the "seven flows" would apply if I were assessing how efficiently it was being done. In this case, the "flow of engineering" (aka "the flow of problem solving") would assess how well the system responds when a design engineer has a problem of some kind that delays his work or his deliverables.

Thanks for commenting! It is nice to know people read this stuff.</description>
		<content:encoded><![CDATA[<p>Brian -<br />
From what I was taught, the &#8220;Seven Flows&#8221; all relate to the production process (whether manufacturing or administrative information processing). </p>
<p>Design engineering certainly has an impact, and I think it is a major player in this flow. That is because I think design changes are one possible countermeasure that this flow could deliver.</p>
<p>However, I do not believe Nakao-san intends &#8220;The flow of engineering&#8221; to be the design/development process itself.</p>
<p>That being said, design engineering *is* a production process, and all of the &#8220;seven flows&#8221; would apply if I were assessing how efficiently it was being done. In this case, the &#8220;flow of engineering&#8221; (aka &#8220;the flow of problem solving&#8221;) would assess how well the system responds when a design engineer has a problem of some kind that delays his work or his deliverables.</p>
<p>Thanks for commenting! It is nice to know people read this stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Sherwod Jones</title>
		<link>http://theleanthinker.com/2007/10/21/the-seventh-flow/#comment-102</link>
		<dc:creator>Brian Sherwod Jones</dc:creator>
		<pubDate>Mon, 22 Oct 2007 18:04:58 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/2007/10/21/the-seventh-flow/#comment-102</guid>
		<description>I haven't seen anything on the application of lean to design and development, but this would be the flow that matters there?</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t seen anything on the application of lean to design and development, but this would be the flow that matters there?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
