<?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: Second best is often good enough</title>
	<atom:link href="http://www.nigel-leech.com/subram/2009/09/09/second-best-is-often-good-enough/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nigel-leech.com/subram/2009/09/09/second-best-is-often-good-enough/</link>
	<description>living with human minds</description>
	<lastBuildDate>Tue, 22 Nov 2011 10:29:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Chris</title>
		<link>http://www.nigel-leech.com/subram/2009/09/09/second-best-is-often-good-enough/comment-page-1/#comment-12</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 09 Sep 2009 07:02:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.nigel-leech.com/subram/?p=798#comment-12</guid>
		<description>Ah, well said that man - I wish I had had that clarity of explanation a few years back because your tale has parallels in businesses. You see, there was a small group of (extremely skilled) guys in my business who - whenever we got a project in - would always want to do the tip-toppermost job on it. The problem was that I knew how long it would take me to do, quoted on that basis, and then discovered they would take twice as long. Even when quizzed about this, the response was usually &quot;Well, you quote what you like that will get the customer to pay, but it will take X days whatever you quote for - we refuse to do the work unless we can do it properly.&quot;

They simply couldn&#039;t get into their heads that there is a sliding scale in the quality of project delivery and that it&#039;s important to hit the sweet spot on it. 

At one end there is &#039;Useless, this has made things worse, I&#039;m not paying you at all, and in fact I&#039;ll probably sue you.&#039;, and at the other end there is &#039;This is the &lt;i&gt;best&lt;/i&gt; possible job that could have been done - no stone has been left unturned and the engineer is clearly capable of leaping tall buildings in a single bound.&#039;. The difficulty is that neither is commercially workable - the first is clearly disastrous, and the second will probably make you a loss, or at best break even - which is no good for paying the bills.

What is needed is a happy half-way house where the customer is just slightly more than contented (i.e. he can see some quality in the work that is more than &#039;average&#039; for the money he&#039;s being asked to pay), but which doesn&#039;t necessarily have all the finesse that a wine connoisseur will detect in a vintage bottle of Krug. It&#039;s about the balance between customer happiness (for which read &#039;propensity to come back next time he wants something and/or recommend you to someone else&#039;) and cold, hard, cash. On a first job for a customer, you might err slightly - and I do only mean &lt;i&gt;slightly&lt;/i&gt; towards the &#039;tip top&#039; end of the spectrum.

(Incidentally, the &#039;tip top&#039; job can be counter-productive too - if it takes longer than the customer wants then it may be perceived as wasting &lt;i&gt;his&lt;/i&gt; time, which is Very Bad.)</description>
		<content:encoded><![CDATA[<p>Ah, well said that man &#8211; I wish I had had that clarity of explanation a few years back because your tale has parallels in businesses. You see, there was a small group of (extremely skilled) guys in my business who &#8211; whenever we got a project in &#8211; would always want to do the tip-toppermost job on it. The problem was that I knew how long it would take me to do, quoted on that basis, and then discovered they would take twice as long. Even when quizzed about this, the response was usually &#8220;Well, you quote what you like that will get the customer to pay, but it will take X days whatever you quote for &#8211; we refuse to do the work unless we can do it properly.&#8221;</p>
<p>They simply couldn&#8217;t get into their heads that there is a sliding scale in the quality of project delivery and that it&#8217;s important to hit the sweet spot on it. </p>
<p>At one end there is &#8216;Useless, this has made things worse, I&#8217;m not paying you at all, and in fact I&#8217;ll probably sue you.&#8217;, and at the other end there is &#8216;This is the <i>best</i> possible job that could have been done &#8211; no stone has been left unturned and the engineer is clearly capable of leaping tall buildings in a single bound.&#8217;. The difficulty is that neither is commercially workable &#8211; the first is clearly disastrous, and the second will probably make you a loss, or at best break even &#8211; which is no good for paying the bills.</p>
<p>What is needed is a happy half-way house where the customer is just slightly more than contented (i.e. he can see some quality in the work that is more than &#8216;average&#8217; for the money he&#8217;s being asked to pay), but which doesn&#8217;t necessarily have all the finesse that a wine connoisseur will detect in a vintage bottle of Krug. It&#8217;s about the balance between customer happiness (for which read &#8216;propensity to come back next time he wants something and/or recommend you to someone else&#8217;) and cold, hard, cash. On a first job for a customer, you might err slightly &#8211; and I do only mean <i>slightly</i> towards the &#8216;tip top&#8217; end of the spectrum.</p>
<p>(Incidentally, the &#8216;tip top&#8217; job can be counter-productive too &#8211; if it takes longer than the customer wants then it may be perceived as wasting <i>his</i> time, which is Very Bad.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

