<?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: How do you prevent scope creep when a client can not make up their minds or articulate what they really want?</title>
	<atom:link href="http://www.processedidentity.com/discussion/how-do-you-prevent-scope-creep-when-a-client-can-not-make-up-their-minds-or-articulate-what-they-really-want/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.processedidentity.com/discussion/how-do-you-prevent-scope-creep-when-a-client-can-not-make-up-their-minds-or-articulate-what-they-really-want/</link>
	<description>Creative Process of Logo and Brand Identity Design</description>
	<lastBuildDate>Wed, 25 Jan 2012 00:58:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Speider</title>
		<link>http://www.processedidentity.com/discussion/how-do-you-prevent-scope-creep-when-a-client-can-not-make-up-their-minds-or-articulate-what-they-really-want/comment-page-1/#comment-122</link>
		<dc:creator>Speider</dc:creator>
		<pubDate>Sat, 27 Nov 2010 03:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://processedidentity.com/?p=531#comment-122</guid>
		<description>It starts with a creative brief and a contract, stating terms, and change fees. If the client refuses to sign it, then expect trouble. Start work without a contract and you get what you deserve.

Part of it all is getting 50% of the fee up front and having milestones for partial payments, or at least being able to walk away with the 50% and counting yourself lucky.

If the client doesn&#039;t at least accept a creative brief and says, &quot;I&#039;ll know when I see it,&quot; then you should be running away quickly at that point.</description>
		<content:encoded><![CDATA[<p>It starts with a creative brief and a contract, stating terms, and change fees. If the client refuses to sign it, then expect trouble. Start work without a contract and you get what you deserve.</p>
<p>Part of it all is getting 50% of the fee up front and having milestones for partial payments, or at least being able to walk away with the 50% and counting yourself lucky.</p>
<p>If the client doesn&#8217;t at least accept a creative brief and says, &#8220;I&#8217;ll know when I see it,&#8221; then you should be running away quickly at that point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PM Hut</title>
		<link>http://www.processedidentity.com/discussion/how-do-you-prevent-scope-creep-when-a-client-can-not-make-up-their-minds-or-articulate-what-they-really-want/comment-page-1/#comment-121</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Wed, 07 Jul 2010 16:45:15 +0000</pubDate>
		<guid isPermaLink="false">http://processedidentity.com/?p=531#comment-121</guid>
		<description>2 things:

- Learn how to say no to your client/customer
- Make sure you gather &lt;a href=&#039;http://www.pmhut.com/on-gathering-the-right-project-requirements&#039; rel=&quot;nofollow&quot;&gt;the right project requirements&lt;/a&gt;.

It is very hard to fight scope creep when it &quot;creeps&quot; on you in the middle project, this is a sign that you did not do your job properly (bad requirements gathering), or you&#039;re allowing clients to &quot;speak their mind&quot; with no consequences.</description>
		<content:encoded><![CDATA[<p>2 things:</p>
<p>- Learn how to say no to your client/customer<br />
- Make sure you gather <a href='http://www.pmhut.com/on-gathering-the-right-project-requirements' rel="nofollow">the right project requirements</a>.</p>
<p>It is very hard to fight scope creep when it &#8220;creeps&#8221; on you in the middle project, this is a sign that you did not do your job properly (bad requirements gathering), or you&#8217;re allowing clients to &#8220;speak their mind&#8221; with no consequences.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Zelle</title>
		<link>http://www.processedidentity.com/discussion/how-do-you-prevent-scope-creep-when-a-client-can-not-make-up-their-minds-or-articulate-what-they-really-want/comment-page-1/#comment-120</link>
		<dc:creator>Steve Zelle</dc:creator>
		<pubDate>Thu, 08 Apr 2010 17:13:17 +0000</pubDate>
		<guid isPermaLink="false">http://processedidentity.com/?p=531#comment-120</guid>
		<description>Thanks John, great points and like most good direction about managing clients, the key is in exposing as much about the process as possible, dealing with their fears, and treating them fairly.  These two past Processed Identity articles also deal with the subject: http://processedidentity.com/article/revisions-redesigns-and-the-creative-process/ and http://processedidentity.com/article/do-clients-deserve-the-blame/</description>
		<content:encoded><![CDATA[<p>Thanks John, great points and like most good direction about managing clients, the key is in exposing as much about the process as possible, dealing with their fears, and treating them fairly.  These two past Processed Identity articles also deal with the subject: <a href="http://processedidentity.com/article/revisions-redesigns-and-the-creative-process/" rel="nofollow">http://processedidentity.com/article/revisions-redesigns-and-the-creative-process/</a> and <a href="http://processedidentity.com/article/do-clients-deserve-the-blame/" rel="nofollow">http://processedidentity.com/article/do-clients-deserve-the-blame/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JanMichael Guzman</title>
		<link>http://www.processedidentity.com/discussion/how-do-you-prevent-scope-creep-when-a-client-can-not-make-up-their-minds-or-articulate-what-they-really-want/comment-page-1/#comment-119</link>
		<dc:creator>JanMichael Guzman</dc:creator>
		<pubDate>Tue, 06 Apr 2010 13:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://processedidentity.com/?p=531#comment-119</guid>
		<description>Very well put, I find the best way to avoid creep is by using a collaborative tool that visually illustrates and denotes  where and when in the project you are. I find clients are less likely to back track when they can see the work that has gone into the project thus far.

I&#039;ve created my own, but a good public example is Basecamp or Action Method.</description>
		<content:encoded><![CDATA[<p>Very well put, I find the best way to avoid creep is by using a collaborative tool that visually illustrates and denotes  where and when in the project you are. I find clients are less likely to back track when they can see the work that has gone into the project thus far.</p>
<p>I&#8217;ve created my own, but a good public example is Basecamp or Action Method.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alice Dagley</title>
		<link>http://www.processedidentity.com/discussion/how-do-you-prevent-scope-creep-when-a-client-can-not-make-up-their-minds-or-articulate-what-they-really-want/comment-page-1/#comment-118</link>
		<dc:creator>Alice Dagley</dc:creator>
		<pubDate>Fri, 02 Apr 2010 09:48:40 +0000</pubDate>
		<guid isPermaLink="false">http://processedidentity.com/?p=531#comment-118</guid>
		<description>Thanks for the article. I quite agree with you. We should involve our clients into work process. However few clients like getting in touch with you during the process. Sometimes it’s hard to extract the information from them. As a result you have to face disappointment by work outcomes from both sides. I also agree with you on getting info in writing. It will help you to avoid misunderstandings. What is more you always can remind your clients their requirements to avoid such an expression like “This is not quite the thing we required!”</description>
		<content:encoded><![CDATA[<p>Thanks for the article. I quite agree with you. We should involve our clients into work process. However few clients like getting in touch with you during the process. Sometimes it’s hard to extract the information from them. As a result you have to face disappointment by work outcomes from both sides. I also agree with you on getting info in writing. It will help you to avoid misunderstandings. What is more you always can remind your clients their requirements to avoid such an expression like “This is not quite the thing we required!”</p>
]]></content:encoded>
	</item>
</channel>
</rss>

