<?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: Your Client Hates Your Work and You Don&#039;t Even Know</title>
	<atom:link href="http://www.theprojectweb.com/your-client-hates-your-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theprojectweb.com/your-client-hates-your-work/</link>
	<description>Resources to Help Small Business and Freelance Web Designers Get the Project Done</description>
	<lastBuildDate>Wed, 16 Nov 2011 05:53:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brett Widmann</title>
		<link>http://www.theprojectweb.com/your-client-hates-your-work/#comment-138</link>
		<dc:creator>Brett Widmann</dc:creator>
		<pubDate>Tue, 21 Dec 2010 23:39:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.clecompte.com/?p=672#comment-138</guid>
		<description>This is a great article. It is important to maintain a close relationship with your client so they are comfortable in telling you what they do and do not like. It is also good to give them many updates on the design progress to ensure their satisfaction.</description>
		<content:encoded><![CDATA[<p>This is a great article. It is important to maintain a close relationship with your client so they are comfortable in telling you what they do and do not like. It is also good to give them many updates on the design progress to ensure their satisfaction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alice Dagley</title>
		<link>http://www.theprojectweb.com/your-client-hates-your-work/#comment-72</link>
		<dc:creator>Alice Dagley</dc:creator>
		<pubDate>Fri, 02 Apr 2010 08:09:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.clecompte.com/?p=672#comment-72</guid>
		<description>Thanks for sharing your thoughts! It’s really useful.
I must admit that you’re fully right: we should cooperate more closely with our clients during working process to avoid misunderstandings and disappointment by the results. And we should connect our clients as personally fast as possible and as often as possible. However few clients want to get in touch with you every day. They prefer to get the results rather than work with you from the very beginning till the end. Relying on my experience customers hate to fill out different questionnaires, describe their preferences in design and especially describe the functionality they have no idea about. So sometimes it’s very difficult to involve a client into work process. And there are some reasons for that. First, your client may be very busy. In this case you need to extract all the information from the client and discuss all the details on the project and even possible difficulties that you may face during the work. What is more you should get the information in written form to avoid such a response like “I didn’t ask you to do this!” or “It’s not exactly what we wanted”. Secondly, your client may not understand all the features and definitions you use and as a result he is getting tired and trying to avoid cooperation. In that case you need to explain everything as clear as possible. Do not expect from you client to know design or developing features as well as you do! It is stupid! Sometimes you have to be very patient to your clients while they are learning to understand all these features with your help.</description>
		<content:encoded><![CDATA[<p>Thanks for sharing your thoughts! It’s really useful.<br />
I must admit that you’re fully right: we should cooperate more closely with our clients during working process to avoid misunderstandings and disappointment by the results. And we should connect our clients as personally fast as possible and as often as possible. However few clients want to get in touch with you every day. They prefer to get the results rather than work with you from the very beginning till the end. Relying on my experience customers hate to fill out different questionnaires, describe their preferences in design and especially describe the functionality they have no idea about. So sometimes it’s very difficult to involve a client into work process. And there are some reasons for that. First, your client may be very busy. In this case you need to extract all the information from the client and discuss all the details on the project and even possible difficulties that you may face during the work. What is more you should get the information in written form to avoid such a response like “I didn’t ask you to do this!” or “It’s not exactly what we wanted”. Secondly, your client may not understand all the features and definitions you use and as a result he is getting tired and trying to avoid cooperation. In that case you need to explain everything as clear as possible. Do not expect from you client to know design or developing features as well as you do! It is stupid! Sometimes you have to be very patient to your clients while they are learning to understand all these features with your help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris LeCompte</title>
		<link>http://www.theprojectweb.com/your-client-hates-your-work/#comment-71</link>
		<dc:creator>Chris LeCompte</dc:creator>
		<pubDate>Tue, 30 Mar 2010 20:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.clecompte.com/?p=672#comment-71</guid>
		<description>Corey,

That&#039;s awesome. I find being proactive can be very hard some days, especially considering it&#039;s so easy to slip into a reactive mindset, so keep it up.

I&#039;ve experienced exactly what you&#039;ve gone through as well. For the portfolio, it can be a tough call. If you have other sites that represent your skills well enough, I&#039;d say exclude it. However, if your portfolio is sparse, and you really want to show others what you&#039;ve created, then perhaps a screenshot of the site (before modification) without a link to the live one will suffice. The thing you want to get away from is passing off the modified site as your creation, especially if it&#039;s a bad design change.</description>
		<content:encoded><![CDATA[<p>Corey,</p>
<p>That&#8217;s awesome. I find being proactive can be very hard some days, especially considering it&#8217;s so easy to slip into a reactive mindset, so keep it up.</p>
<p>I&#8217;ve experienced exactly what you&#8217;ve gone through as well. For the portfolio, it can be a tough call. If you have other sites that represent your skills well enough, I&#8217;d say exclude it. However, if your portfolio is sparse, and you really want to show others what you&#8217;ve created, then perhaps a screenshot of the site (before modification) without a link to the live one will suffice. The thing you want to get away from is passing off the modified site as your creation, especially if it&#8217;s a bad design change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corey</title>
		<link>http://www.theprojectweb.com/your-client-hates-your-work/#comment-70</link>
		<dc:creator>Corey</dc:creator>
		<pubDate>Tue, 30 Mar 2010 17:15:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.clecompte.com/?p=672#comment-70</guid>
		<description>I think I&#039;m proactive when working with clients throughout creating their website.

However, I just experienced (after the website has been done for a few months) the client hire another designer and change the color scheme of the website. I&#039;m talking from cold to hot. (blue to pink)

What would you suggest keep it in the portfolio or should I have to throw it out? (I did the design / development for it)</description>
		<content:encoded><![CDATA[<p>I think I&#8217;m proactive when working with clients throughout creating their website.</p>
<p>However, I just experienced (after the website has been done for a few months) the client hire another designer and change the color scheme of the website. I&#8217;m talking from cold to hot. (blue to pink)</p>
<p>What would you suggest keep it in the portfolio or should I have to throw it out? (I did the design / development for it)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
