<?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: &#8220;We do what the customers ask for.&#8221;</title>
	<atom:link href="http://www.redmonk.com/cote/2006/09/20/we-do-what-the-customers-ask-for/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/cote/2006/09/20/we-do-what-the-customers-ask-for/</link>
	<description>One foot in the muck, the other in utopia</description>
	<pubDate>Tue, 02 Dec 2008 02:26:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Morten</title>
		<link>http://www.redmonk.com/cote/2006/09/20/we-do-what-the-customers-ask-for/#comment-9926</link>
		<dc:creator>Morten</dc:creator>
		<pubDate>Mon, 26 Feb 2007 14:02:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/wp/?p=381#comment-9926</guid>
		<description>Hi, just stumbled upon your blog. Enjoying it so far and just thought I'd throw a comment at this.

My experience is that you cannot simply make decisions for the customer. You have to a very good job of explaining the situation for them and have them realise themselves the better solution. Also I have on numerous accounts hit a wall of company policy issues which makes me, as a consultant, incapable of persuading a customer to go down a different path.

But then again, I've just recently seen an IT consultant sell a customer a system architecture which they basically didn't need. The result was a price tag much over the budget and a very ill functioning system. So your making the decisions on behalf of the customer also means that you have to be completely into the customers demands. This might be a bit basic, but I have encountered some situations where the customer does not only know exactly was he or she wants (usually the case) but also is withholding some information (not on purpose) that might be very relevant.</description>
		<content:encoded><![CDATA[<p>Hi, just stumbled upon your blog. Enjoying it so far and just thought I&#8217;d throw a comment at this.</p>
<p>My experience is that you cannot simply make decisions for the customer. You have to a very good job of explaining the situation for them and have them realise themselves the better solution. Also I have on numerous accounts hit a wall of company policy issues which makes me, as a consultant, incapable of persuading a customer to go down a different path.</p>
<p>But then again, I&#8217;ve just recently seen an IT consultant sell a customer a system architecture which they basically didn&#8217;t need. The result was a price tag much over the budget and a very ill functioning system. So your making the decisions on behalf of the customer also means that you have to be completely into the customers demands. This might be a bit basic, but I have encountered some situations where the customer does not only know exactly was he or she wants (usually the case) but also is withholding some information (not on purpose) that might be very relevant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriel</title>
		<link>http://www.redmonk.com/cote/2006/09/20/we-do-what-the-customers-ask-for/#comment-495</link>
		<dc:creator>Gabriel</dc:creator>
		<pubDate>Fri, 22 Sep 2006 21:15:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/wp/?p=381#comment-495</guid>
		<description>I believe there's a big difference in what the customer wants and what the customer needs, and there lies the problem.
</description>
		<content:encoded><![CDATA[<p>I believe there&#8217;s a big difference in what the customer wants and what the customer needs, and there lies the problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cote'</title>
		<link>http://www.redmonk.com/cote/2006/09/20/we-do-what-the-customers-ask-for/#comment-494</link>
		<dc:creator>Cote'</dc:creator>
		<pubDate>Thu, 21 Sep 2006 17:20:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/wp/?p=381#comment-494</guid>
		<description>Ric: yes, that's an excellent correction on the point. Yuh!
Robert: Is there anything Ford &lt;i&gt;didn't&lt;/i&gt; say?</description>
		<content:encoded><![CDATA[<p>Ric: yes, that&#8217;s an excellent correction on the point. Yuh!<br />
Robert: Is there anything Ford <i>didn&#8217;t</i> say?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://www.redmonk.com/cote/2006/09/20/we-do-what-the-customers-ask-for/#comment-493</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 21 Sep 2006 13:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/wp/?p=381#comment-493</guid>
		<description>It reminds me of the Henry Ford quote I use all the time. "If I'd asked my customers what they wanted, they'd have said a faster horse."</description>
		<content:encoded><![CDATA[<p>It reminds me of the Henry Ford quote I use all the time. &#8220;If I&#8217;d asked my customers what they wanted, they&#8217;d have said a faster horse.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ric</title>
		<link>http://www.redmonk.com/cote/2006/09/20/we-do-what-the-customers-ask-for/#comment-492</link>
		<dc:creator>Ric</dc:creator>
		<pubDate>Thu, 21 Sep 2006 02:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/wp/?p=381#comment-492</guid>
		<description>In my experience, the customer will only know what they DON'T want after they've seen something to help them crystallise their thinking - which is where Agile methodologies are valuable in getting something in front of the client and eliciting rapid feedback.</description>
		<content:encoded><![CDATA[<p>In my experience, the customer will only know what they DON&#8217;T want after they&#8217;ve seen something to help them crystallise their thinking - which is where Agile methodologies are valuable in getting something in front of the client and eliciting rapid feedback.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
