<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: When Good Enough is Perfect</title>
	<atom:link href="http://richworklife.com/2009/09/15/when-good-enough-is-perfect/feed/" rel="self" type="application/rss+xml" />
	<link>http://richworklife.com/2009/09/15/when-good-enough-is-perfect/</link>
	<description>designs for work and life</description>
	<lastBuildDate>Fri, 16 Dec 2011 02:21:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: richprest</title>
		<link>http://richworklife.com/2009/09/15/when-good-enough-is-perfect/#comment-3</link>
		<dc:creator><![CDATA[richprest]]></dc:creator>
		<pubDate>Wed, 16 Sep 2009 18:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://richworklife.wordpress.com/?p=26#comment-3</guid>
		<description><![CDATA[Olivier,

Thanks for kicking off the discussion!  You&#039;ve got me thinking about those &quot;artistic parts&quot; and wondering if the rule applies to them as well - I recall many long meetings debating to the nth degree copy for an ad, when it was clear that for most of the audience that effort was clearly in the realm of diminishing returns.  Same goes in architecture, hours and hours fussing over details that only another architect would notice.  To counter this, there are clearly examples, like the iPhone, where compromise over design would not have yielded such a great result.  Where I&#039;m heading is: do we want a good enough rule for the feature set, but perfection for the execution of the design?  That is, work out what people really need (no unnecessary features) and then execute that minimum feature set brilliantly?  

Cheers,
Rich]]></description>
		<content:encoded><![CDATA[<p>Olivier,</p>
<p>Thanks for kicking off the discussion!  You&#8217;ve got me thinking about those &#8220;artistic parts&#8221; and wondering if the rule applies to them as well &#8211; I recall many long meetings debating to the nth degree copy for an ad, when it was clear that for most of the audience that effort was clearly in the realm of diminishing returns.  Same goes in architecture, hours and hours fussing over details that only another architect would notice.  To counter this, there are clearly examples, like the iPhone, where compromise over design would not have yielded such a great result.  Where I&#8217;m heading is: do we want a good enough rule for the feature set, but perfection for the execution of the design?  That is, work out what people really need (no unnecessary features) and then execute that minimum feature set brilliantly?  </p>
<p>Cheers,<br />
Rich</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivier Fontana</title>
		<link>http://richworklife.com/2009/09/15/when-good-enough-is-perfect/#comment-2</link>
		<dc:creator><![CDATA[Olivier Fontana]]></dc:creator>
		<pubDate>Wed, 16 Sep 2009 18:12:44 +0000</pubDate>
		<guid isPermaLink="false">http://richworklife.wordpress.com/?p=26#comment-2</guid>
		<description><![CDATA[I would even argue that, with the exception of the artistic parts of Marketing (copy of an ad, design of a site...), most of marketing is ruled by the good-enough rule  or as I often refer to the 80/20 Pareto Law.]]></description>
		<content:encoded><![CDATA[<p>I would even argue that, with the exception of the artistic parts of Marketing (copy of an ad, design of a site&#8230;), most of marketing is ruled by the good-enough rule  or as I often refer to the 80/20 Pareto Law.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

