<?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: Rearranging Furniture for an Unfocused Client</title>
	<atom:link href="http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/</link>
	<description>Ideas for building efficient developers and software</description>
	<lastBuildDate>Mon, 30 Jan 2012 11:03:44 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Max Pool</title>
		<link>http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/#comment-266</link>
		<dc:creator>Max Pool</dc:creator>
		<pubDate>Wed, 12 Sep 2007 18:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/#comment-266</guid>
		<description>@James - 

Wow! FANTASTIC ideas, I even learned some new poker calls with your comment...</description>
		<content:encoded><![CDATA[<p>@James &#8211; </p>
<p>Wow! FANTASTIC ideas, I even learned some new poker calls with your comment&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: devtrench</title>
		<link>http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/#comment-265</link>
		<dc:creator>devtrench</dc:creator>
		<pubDate>Wed, 12 Sep 2007 14:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/#comment-265</guid>
		<description>You speak the truth.  I&#039;ve found that the temperament of the client has a huge impact on scope creep and staying within budget.  Great clients are ones that are decisive, go getters, know what they want done, and most importantly, don&#039;t get distracted -- they&#039;re focused.  Some red flags that I&#039;ve come across over the years:

* Client doesn&#039;t look at you when they talk
* Client only speaks in &quot;what ifs&quot;
* When you get down to details, the client doesn&#039;t know, or has to leave
* When you show a client your software for the first time, they freak out
* The client mulls over tiny details like fonts, colors, and other design features, but can never get you a feature list, or other crucial information you need.
* Client talks about normal and obvious conventions in strange abstractions.  This is a weak example, but I had a client talk about their DIDO database.  DIDO is &#039;data-in, data-out&#039; which all databases can do, but this client drooled over the acronym they made up.

I could go on forever about client red flags...

James</description>
		<content:encoded><![CDATA[<p>You speak the truth.  I&#8217;ve found that the temperament of the client has a huge impact on scope creep and staying within budget.  Great clients are ones that are decisive, go getters, know what they want done, and most importantly, don&#8217;t get distracted &#8212; they&#8217;re focused.  Some red flags that I&#8217;ve come across over the years:</p>
<p>* Client doesn&#8217;t look at you when they talk<br />
* Client only speaks in &#8220;what ifs&#8221;<br />
* When you get down to details, the client doesn&#8217;t know, or has to leave<br />
* When you show a client your software for the first time, they freak out<br />
* The client mulls over tiny details like fonts, colors, and other design features, but can never get you a feature list, or other crucial information you need.<br />
* Client talks about normal and obvious conventions in strange abstractions.  This is a weak example, but I had a client talk about their DIDO database.  DIDO is &#8216;data-in, data-out&#8217; which all databases can do, but this client drooled over the acronym they made up.</p>
<p>I could go on forever about client red flags&#8230;</p>
<p>James</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/#comment-260</link>
		<dc:creator>david</dc:creator>
		<pubDate>Tue, 11 Sep 2007 18:53:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/#comment-260</guid>
		<description>This is great advice that I wish I&#039;d heard a few years ago. Thanks for sharing it.</description>
		<content:encoded><![CDATA[<p>This is great advice that I wish I&#8217;d heard a few years ago. Thanks for sharing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the matt</title>
		<link>http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/#comment-259</link>
		<dc:creator>the matt</dc:creator>
		<pubDate>Tue, 11 Sep 2007 13:07:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/#comment-259</guid>
		<description>and in a software product(s) company, sadly it&#039;s the unfocused boss that can wreak this havoc! been there, twice, miserable.

heya max - kudos on the blog, as well as the new gig!</description>
		<content:encoded><![CDATA[<p>and in a software product(s) company, sadly it&#8217;s the unfocused boss that can wreak this havoc! been there, twice, miserable.</p>
<p>heya max &#8211; kudos on the blog, as well as the new gig!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura</title>
		<link>http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/#comment-258</link>
		<dc:creator>Laura</dc:creator>
		<pubDate>Mon, 10 Sep 2007 20:15:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/rearranging-furniture-for-an-unfocused-client/#comment-258</guid>
		<description>You are SO right!</description>
		<content:encoded><![CDATA[<p>You are SO right!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

