<?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: Flintstoning</title>
	<atom:link href="http://rowansimpson.com/2007/12/11/flintstoning/feed/" rel="self" type="application/rss+xml" />
	<link>http://rowansimpson.com/2007/12/11/flintstoning/</link>
	<description>Made in New Zealand from local and imported ingredients</description>
	<pubDate>Thu, 08 Jan 2009 01:14:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Miki</title>
		<link>http://rowansimpson.com/2007/12/11/flintstoning/#comment-6813</link>
		<dc:creator>Miki</dc:creator>
		<pubDate>Wed, 12 Dec 2007 01:32:31 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/2007/12/11/flintstoning/#comment-6813</guid>
		<description>We always used to use the term Kit Kat - usually web forms filled in that ended up in someone's in tray that they might (or might not) get around to.

Flintstoning is a much better term - better mental picture of what really happens!

My experience of this is not a debate about whether to automate or not but more to have the discipline to review your processes regularly to make sure that you are operating as efficiently as possible. I've seen too many situations where the Day 1 process was never automated but was also never reviewed to see how it coped with scale.</description>
		<content:encoded><![CDATA[<p>We always used to use the term Kit Kat - usually web forms filled in that ended up in someone&#8217;s in tray that they might (or might not) get around to.</p>
<p>Flintstoning is a much better term - better mental picture of what really happens!</p>
<p>My experience of this is not a debate about whether to automate or not but more to have the discipline to review your processes regularly to make sure that you are operating as efficiently as possible. I&#8217;ve seen too many situations where the Day 1 process was never automated but was also never reviewed to see how it coped with scale.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://rowansimpson.com/2007/12/11/flintstoning/#comment-6809</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Tue, 11 Dec 2007 10:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/2007/12/11/flintstoning/#comment-6809</guid>
		<description>"Automation is critical to achieving scale" - a very dangerous and seriously flawed assumption, especially when dealing with physical goods and human interactions.  It leads you into complex automation of complex processes. Try to automate everything, and the complexity is often some combination of unbuildable, unreliable, unresponsive, or inflexible.

"Lean thinking" says only automate if there are very clear benefits of doing so, if the process is very robust, and if you are absolutely certain that flexibility is not lost.  Simple focused automation using a flexible building block approach seems to work better.  Best example - Toyota, which is the least automated yet most efficient car manufacturer, with the highest ex-factory reliability.

The way application families are emerging now suggests the same is true even in information systems.</description>
		<content:encoded><![CDATA[<p>&#8220;Automation is critical to achieving scale&#8221; - a very dangerous and seriously flawed assumption, especially when dealing with physical goods and human interactions.  It leads you into complex automation of complex processes. Try to automate everything, and the complexity is often some combination of unbuildable, unreliable, unresponsive, or inflexible.</p>
<p>&#8220;Lean thinking&#8221; says only automate if there are very clear benefits of doing so, if the process is very robust, and if you are absolutely certain that flexibility is not lost.  Simple focused automation using a flexible building block approach seems to work better.  Best example - Toyota, which is the least automated yet most efficient car manufacturer, with the highest ex-factory reliability.</p>
<p>The way application families are emerging now suggests the same is true even in information systems.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
