<?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: Do Less</title>
	<atom:link href="http://thingsthatarebrown.com/blog/2008/10/do-less/feed/" rel="self" type="application/rss+xml" />
	<link>http://thingsthatarebrown.com/blog/2008/10/do-less/</link>
	<description>Smart, nimble web design by Matt Brown and Tiffani Jones Brown.</description>
	<lastBuildDate>Fri, 11 Feb 2011 02:11:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Grant</title>
		<link>http://thingsthatarebrown.com/blog/2008/10/do-less/comment-page-1/#comment-349</link>
		<dc:creator>Grant</dc:creator>
		<pubDate>Wed, 22 Oct 2008 23:20:03 +0000</pubDate>
		<guid isPermaLink="false">http://thingsthatarebrown.com/blog/?p=61#comment-349</guid>
		<description>Thanks for the input. I like the idea of an up-front dialogue on what we&#039;re limiting and why.
&lt;blockquote&gt;&quot;Really, the interesting thing to me about limiting scope is that it tends to focus the work on the most important things like discovery, messaging / brand, copy, layout, etc. It shifts the focus away from the tech / features, and towards the essentials.&quot;&lt;/blockquote&gt;
Yeah, that&#039;s what intrigues me about the idea. It seems to bring things into focus on a given project in a way they never were before.</description>
		<content:encoded><![CDATA[<p>Thanks for the input. I like the idea of an up-front dialogue on what we&#8217;re limiting and why.</p>
<blockquote><p>&#8220;Really, the interesting thing to me about limiting scope is that it tends to focus the work on the most important things like discovery, messaging / brand, copy, layout, etc. It shifts the focus away from the tech / features, and towards the essentials.&#8221;</p></blockquote>
<p>Yeah, that&#8217;s what intrigues me about the idea. It seems to bring things into focus on a given project in a way they never were before.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://thingsthatarebrown.com/blog/2008/10/do-less/comment-page-1/#comment-344</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Mon, 20 Oct 2008 22:30:35 +0000</pubDate>
		<guid isPermaLink="false">http://thingsthatarebrown.com/blog/?p=61#comment-344</guid>
		<description>@Grant:  I try to prep my clients on my approach in all the pre-signing negotiations.  Also, my contracts have clear language of what I&#039;m doing for them, as well as what I&#039;m not (scope &quot;known unknowns&quot;).
You&#039;re right though -- there&#039;s always going to be the issue of doing too little for a client, or finding later on that their needs have changed.  But I find that being upfront as soon as possible and amending the contract works very well for both parites.
Really, the interesting thing to me about limiting scope is that it tends to focus the work on the most important things like discovery, messaging / brand, copy, layout, etc.  It shifts the focus away from the tech / features, and towards the essentials.</description>
		<content:encoded><![CDATA[<p>@Grant:  I try to prep my clients on my approach in all the pre-signing negotiations.  Also, my contracts have clear language of what I&#8217;m doing for them, as well as what I&#8217;m not (scope &#8220;known unknowns&#8221;).</p>
<p>You&#8217;re right though &#8212; there&#8217;s always going to be the issue of doing too little for a client, or finding later on that their needs have changed.  But I find that being upfront as soon as possible and amending the contract works very well for both parites.</p>
<p>Really, the interesting thing to me about limiting scope is that it tends to focus the work on the most important things like discovery, messaging / brand, copy, layout, etc.  It shifts the focus away from the tech / features, and towards the essentials.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant</title>
		<link>http://thingsthatarebrown.com/blog/2008/10/do-less/comment-page-1/#comment-343</link>
		<dc:creator>Grant</dc:creator>
		<pubDate>Mon, 20 Oct 2008 21:25:51 +0000</pubDate>
		<guid isPermaLink="false">http://thingsthatarebrown.com/blog/?p=61#comment-343</guid>
		<description>I totally agree with this philosophy and approach. One question, though: how much to you feel you have to educate your clients up front and through the process with solutions such as this?
I&#039;ve tried to scope down projects in the past and often run into the problem where clients try to feature-creep their projects once the process has started (usually, the don&#039;t even know they&#039;re doing it). It frustrates both parties as I try to keep them on track with the original plan, or remind them that changes will take more time/money.</description>
		<content:encoded><![CDATA[<p>I totally agree with this philosophy and approach. One question, though: how much to you feel you have to educate your clients up front and through the process with solutions such as this?</p>
<p>I&#8217;ve tried to scope down projects in the past and often run into the problem where clients try to feature-creep their projects once the process has started (usually, the don&#8217;t even know they&#8217;re doing it). It frustrates both parties as I try to keep them on track with the original plan, or remind them that changes will take more time/money.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

