<?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: Turning Down Projects</title>
	<atom:link href="http://www.jwphill3.com/2008/11/11/turning-down-projects/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jwphill3.com/design/turning-down-projects/</link>
	<description></description>
	<lastBuildDate>Sat, 12 Dec 2009 14:19:38 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Phillips</title>
		<link>http://www.jwphill3.com/design/turning-down-projects/comment-page-1/#comment-12531</link>
		<dc:creator>John Phillips</dc:creator>
		<pubDate>Wed, 12 Nov 2008 12:41:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwphill3.com/?p=152#comment-12531</guid>
		<description>Dominic, that&#039;s a great idea for a next post, but will take tons of thought. It&#039;s no easy feat to have to do that.

Sean, content development always seems to be a hurdle. I notice that many clients don&#039;t like focusing on the content until the end, when it&#039;s far more beneficial to have it done before you start designing. You have to know what kind of content your design for.</description>
		<content:encoded><![CDATA[<p>Dominic, that&#8217;s a great idea for a next post, but will take tons of thought. It&#8217;s no easy feat to have to do that.</p>
<p>Sean, content development always seems to be a hurdle. I notice that many clients don&#8217;t like focusing on the content until the end, when it&#8217;s far more beneficial to have it done before you start designing. You have to know what kind of content your design for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean S.</title>
		<link>http://www.jwphill3.com/design/turning-down-projects/comment-page-1/#comment-12530</link>
		<dc:creator>Sean S.</dc:creator>
		<pubDate>Wed, 12 Nov 2008 07:48:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwphill3.com/?p=152#comment-12530</guid>
		<description>What we have done is identify a number of problem areas in phases throughout the project and address questions that will help us determine if these problem areas are going to be an obstacle with the potential client...

We have found that content development and the clients commitment to putting the work in on their side and how well they are prepared to tackle these issues once the project is underway are the biggest questions we need to hear the right answer to...</description>
		<content:encoded><![CDATA[<p>What we have done is identify a number of problem areas in phases throughout the project and address questions that will help us determine if these problem areas are going to be an obstacle with the potential client&#8230;</p>
<p>We have found that content development and the clients commitment to putting the work in on their side and how well they are prepared to tackle these issues once the project is underway are the biggest questions we need to hear the right answer to&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dominic Massad</title>
		<link>http://www.jwphill3.com/design/turning-down-projects/comment-page-1/#comment-12529</link>
		<dc:creator>Dominic Massad</dc:creator>
		<pubDate>Wed, 12 Nov 2008 06:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwphill3.com/?p=152#comment-12529</guid>
		<description>I couldn&#039;t agree more with this post... The next post should be, &quot;How to pass off the project when the client becomes problematic.&quot; I think one of the top red flags is when the client starts changing the scope a lot. You don&#039;t always find this out until the middle of the project and what was thought to be a cool client then becomes troublesome.</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more with this post&#8230; The next post should be, &#8220;How to pass off the project when the client becomes problematic.&#8221; I think one of the top red flags is when the client starts changing the scope a lot. You don&#8217;t always find this out until the middle of the project and what was thought to be a cool client then becomes troublesome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Phillips</title>
		<link>http://www.jwphill3.com/design/turning-down-projects/comment-page-1/#comment-12528</link>
		<dc:creator>John Phillips</dc:creator>
		<pubDate>Wed, 12 Nov 2008 03:58:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwphill3.com/?p=152#comment-12528</guid>
		<description>Dunrie, identifying statekholders is extremely important. Having the &quot;design by committee&quot; because you don&#039;t know who makes the decisions can be a headache.

Tim, I agree, taking on someone else&#039;s mess is definitely touchy, because you can&#039;t really detect what went wrong to drive another developer away from the project. At at the point, since the project had already been started, a discovery meeting can be odd.</description>
		<content:encoded><![CDATA[<p>Dunrie, identifying statekholders is extremely important. Having the &#8220;design by committee&#8221; because you don&#8217;t know who makes the decisions can be a headache.</p>
<p>Tim, I agree, taking on someone else&#8217;s mess is definitely touchy, because you can&#8217;t really detect what went wrong to drive another developer away from the project. At at the point, since the project had already been started, a discovery meeting can be odd.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://www.jwphill3.com/design/turning-down-projects/comment-page-1/#comment-12527</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Wed, 12 Nov 2008 03:22:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwphill3.com/?p=152#comment-12527</guid>
		<description>A recent client was in a &quot;bad&quot; situation with her previous developer with lawyers and all that. She wanted us to come in and clean it up. As it was a big ecommerce site we thought it had a lot of potential. A month into the project we found out we were the fifth developer in. Now it&#039;s one of those stressful ones.

When she was talking about the developer and her legal trouble I should have been trying to hear &quot;their&quot; side of the story, not hers. Taking on someone&#039;s mess is very touchy.</description>
		<content:encoded><![CDATA[<p>A recent client was in a &#8220;bad&#8221; situation with her previous developer with lawyers and all that. She wanted us to come in and clean it up. As it was a big ecommerce site we thought it had a lot of potential. A month into the project we found out we were the fifth developer in. Now it&#8217;s one of those stressful ones.</p>
<p>When she was talking about the developer and her legal trouble I should have been trying to hear &#8220;their&#8221; side of the story, not hers. Taking on someone&#8217;s mess is very touchy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
