<?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: Why Client Revisions Shouldn&#8217;t Be Allowed</title>
	<atom:link href="http://www.propstm.net/2009/12/07/why-client-revisions-shouldnt-be-allowed/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.propstm.net/2009/12/07/why-client-revisions-shouldnt-be-allowed/</link>
	<description></description>
	<lastBuildDate>Wed, 16 Dec 2009 20:33:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Niki Brown</title>
		<link>http://www.propstm.net/2009/12/07/why-client-revisions-shouldnt-be-allowed/comment-page-1/#comment-183434</link>
		<dc:creator>Niki Brown</dc:creator>
		<pubDate>Thu, 10 Dec 2009 13:58:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.propstm.net/?p=315#comment-183434</guid>
		<description>The design process is about designer-client communication more than anything. The more you focus on this and finding out what the client really NEEDS (not wants) and meet those needs the smoother the project will go. 

Its always a learning process.</description>
		<content:encoded><![CDATA[<p>The design process is about designer-client communication more than anything. The more you focus on this and finding out what the client really NEEDS (not wants) and meet those needs the smoother the project will go. </p>
<p>Its always a learning process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.propstm.net/2009/12/07/why-client-revisions-shouldnt-be-allowed/comment-page-1/#comment-183196</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Mon, 07 Dec 2009 17:42:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.propstm.net/?p=315#comment-183196</guid>
		<description>Shawn I would completely agree with you.  A more collaborative effort on a designer&#039;s part and getting client sign off during the design process are great ways to prevent any chaos.  However having seen more than a few projects come completely apart due to client changes, I think that the process and agreement on the work between client and designer needs to happen before the deliverables hit the table. Changes that occur &quot;after the fact&quot; usually only delay timelines, and derail budgets.</description>
		<content:encoded><![CDATA[<p>Shawn I would completely agree with you.  A more collaborative effort on a designer&#8217;s part and getting client sign off during the design process are great ways to prevent any chaos.  However having seen more than a few projects come completely apart due to client changes, I think that the process and agreement on the work between client and designer needs to happen before the deliverables hit the table. Changes that occur &#8220;after the fact&#8221; usually only delay timelines, and derail budgets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Davis</title>
		<link>http://www.propstm.net/2009/12/07/why-client-revisions-shouldnt-be-allowed/comment-page-1/#comment-183195</link>
		<dc:creator>Shawn Davis</dc:creator>
		<pubDate>Mon, 07 Dec 2009 17:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.propstm.net/?p=315#comment-183195</guid>
		<description>This web comic is really funny, and we&#039;ve all been there, but it&#039;s a great example of not managing your client or the project.  If you have a solid rationale for the designs you&#039;re proposing, then you should be able to defend against unreasonable requests (which is code for stupid ideas).  It&#039;s really a process of educating the client and bringing them to an understanding of WHY you did what you did. You can&#039;t defend a design by saying &quot;because it&#039;s cool looking&quot;, that&#039;s not enough.

Another way to keep things on track is getting sign-offs for steps along the way.  Before you move on to the next phase the client needs to agree to the work and the direction.   After sign-off, if changes occur, then you are free to issue change orders. 

I would agree with you that continued reference to the creative brief is a good way to keep the client focused on the task at hand...and keep the kitten pictures out of your design.</description>
		<content:encoded><![CDATA[<p>This web comic is really funny, and we&#8217;ve all been there, but it&#8217;s a great example of not managing your client or the project.  If you have a solid rationale for the designs you&#8217;re proposing, then you should be able to defend against unreasonable requests (which is code for stupid ideas).  It&#8217;s really a process of educating the client and bringing them to an understanding of WHY you did what you did. You can&#8217;t defend a design by saying &#8220;because it&#8217;s cool looking&#8221;, that&#8217;s not enough.</p>
<p>Another way to keep things on track is getting sign-offs for steps along the way.  Before you move on to the next phase the client needs to agree to the work and the direction.   After sign-off, if changes occur, then you are free to issue change orders. </p>
<p>I would agree with you that continued reference to the creative brief is a good way to keep the client focused on the task at hand&#8230;and keep the kitten pictures out of your design.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

