<?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: Setting Boundaries on Burnout</title>
	<atom:link href="http://www.to-done.com/2005/08/setting-boundaries-on-burnout/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.to-done.com/2005/08/setting-boundaries-on-burnout/</link>
	<description>Working To Live</description>
	<lastBuildDate>Tue, 28 Nov 2006 15:04:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nathan Smith</title>
		<link>http://www.to-done.com/2005/08/setting-boundaries-on-burnout/comment-page-1/#comment-621</link>
		<dc:creator>Nathan Smith</dc:creator>
		<pubDate>Mon, 22 Aug 2005 02:19:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/08/setting-boundaries-on-burnout/#comment-621</guid>
		<description>Steve, that&#039;s true. I should clarify that not each and every church I&#039;ve worked with are slow on delivering content. For the most part, it&#039;s like you said - clients that want to get online are ready with their message. I just thought I would share some of my experiences (and my own mistakes), to help others avoid burnout.

Here&#039;s a good article on client deliverables...
http://www.yourtotalsite.com/archives/methodology_tools/client_deliverables/</description>
		<content:encoded><![CDATA[<p>Steve, that&#8217;s true. I should clarify that not each and every church I&#8217;ve worked with are slow on delivering content. For the most part, it&#8217;s like you said &#8211; clients that want to get online are ready with their message. I just thought I would share some of my experiences (and my own mistakes), to help others avoid burnout.</p>
<p>Here&#8217;s a good article on client deliverables&#8230;<br />
<a href="http://www.yourtotalsite.com/archives/methodology_tools/client_deliverables/" rel="nofollow">http://www.yourtotalsite.com/a.....iverables/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Clancy</title>
		<link>http://www.to-done.com/2005/08/setting-boundaries-on-burnout/comment-page-1/#comment-620</link>
		<dc:creator>Steve Clancy</dc:creator>
		<pubDate>Sun, 21 Aug 2005 13:32:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/08/setting-boundaries-on-burnout/#comment-620</guid>
		<description>I agree with a lot of what you&#039;re saying, because I have had some experience dealing with small clients who want to get on the web. I think in most cases though, these people always have content they can be posting - it&#039;s just a matter of getting them to deliver it. With your church example, surely you could be posting Sunday bulletins and mass schedules on the site. You just need to get them to the point where they are willing to do this.</description>
		<content:encoded><![CDATA[<p>I agree with a lot of what you&#8217;re saying, because I have had some experience dealing with small clients who want to get on the web. I think in most cases though, these people always have content they can be posting &#8211; it&#8217;s just a matter of getting them to deliver it. With your church example, surely you could be posting Sunday bulletins and mass schedules on the site. You just need to get them to the point where they are willing to do this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Rohde</title>
		<link>http://www.to-done.com/2005/08/setting-boundaries-on-burnout/comment-page-1/#comment-618</link>
		<dc:creator>Mike Rohde</dc:creator>
		<pubDate>Sun, 21 Aug 2005 05:28:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/08/setting-boundaries-on-burnout/#comment-618</guid>
		<description>Nice article Nathan â€” a good reminder about why designers design things â€” to communicate. :-)</description>
		<content:encoded><![CDATA[<p>Nice article Nathan â€” a good reminder about why designers design things â€” to communicate. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Smith</title>
		<link>http://www.to-done.com/2005/08/setting-boundaries-on-burnout/comment-page-1/#comment-610</link>
		<dc:creator>Nathan Smith</dc:creator>
		<pubDate>Fri, 19 Aug 2005 22:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/08/setting-boundaries-on-burnout/#comment-610</guid>
		<description>If you&#039;re not interested in the job because there&#039;s something lacking in the vision of what they want to do, then I would just explain that plainly to them.  Just because you don&#039;t say &quot;yes&quot; right away doesn&#039;t make you a mean person.  In fact, it is to their benefit that they have something interesting on their site when it is created.

I would just tell them that while you want to help them, there is really just not enough to go on. Often times, if they are pretty sure about wanting to hire you (as opposed to just get a site done), they will provide you with more content. The problem I&#039;ve run into is that I will tell a client that they need more content to go on, and they will promise to write it concurrently as the site is being worked on, only to have them never finish the content.

If for some reason the project simply does not interest you, there&#039;s nothing wrong with saying that either. For instance, I had someone contact me about doing 80 blog designs for a network of blogs.  Without going into great detail, the premise of the email was to crank them out one after the other.  I did my best to explain to the individual that what I try to focus on is quality and not quantity, and because of that it did not really appeal to me.

This mass-production mentality didn&#039;t really jive with me, something in my gut just told me it would too labor intensive for the amount of time I had to spend.  Additionally, the timetable / budget seemed to be a bit stringent.  I think in this case, it was the &quot;get-rich-quick&quot; mentality that was the primary motive, aka Blog = Money, without really considering the initial investment necessary to launch an entire network from nothing.</description>
		<content:encoded><![CDATA[<p>If you&#8217;re not interested in the job because there&#8217;s something lacking in the vision of what they want to do, then I would just explain that plainly to them.  Just because you don&#8217;t say &#8220;yes&#8221; right away doesn&#8217;t make you a mean person.  In fact, it is to their benefit that they have something interesting on their site when it is created.</p>
<p>I would just tell them that while you want to help them, there is really just not enough to go on. Often times, if they are pretty sure about wanting to hire you (as opposed to just get a site done), they will provide you with more content. The problem I&#8217;ve run into is that I will tell a client that they need more content to go on, and they will promise to write it concurrently as the site is being worked on, only to have them never finish the content.</p>
<p>If for some reason the project simply does not interest you, there&#8217;s nothing wrong with saying that either. For instance, I had someone contact me about doing 80 blog designs for a network of blogs.  Without going into great detail, the premise of the email was to crank them out one after the other.  I did my best to explain to the individual that what I try to focus on is quality and not quantity, and because of that it did not really appeal to me.</p>
<p>This mass-production mentality didn&#8217;t really jive with me, something in my gut just told me it would too labor intensive for the amount of time I had to spend.  Additionally, the timetable / budget seemed to be a bit stringent.  I think in this case, it was the &#8220;get-rich-quick&#8221; mentality that was the primary motive, aka Blog = Money, without really considering the initial investment necessary to launch an entire network from nothing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Bennett-Chamberlain</title>
		<link>http://www.to-done.com/2005/08/setting-boundaries-on-burnout/comment-page-1/#comment-607</link>
		<dc:creator>Jesse Bennett-Chamberlain</dc:creator>
		<pubDate>Fri, 19 Aug 2005 19:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/08/setting-boundaries-on-burnout/#comment-607</guid>
		<description>Quote:
-----
&lt;strong&gt;This is why I would propose, that in order to help protect both yourself and your client&#039;s time investment (and sanity), that you not be afraid to just say a flat-out &#8220;No&#8221; to potential website projects.&lt;/strong&gt;
-----

Any advice on how to do this tactfully? I get many requests for jobs that I&#039;m just not interested in and have a hard time saying no because I&#039;m just not sure how to tell them. </description>
		<content:encoded><![CDATA[<p>Quote:<br />
&#8212;&#8211;<br />
<strong>This is why I would propose, that in order to help protect both yourself and your client&#8217;s time investment (and sanity), that you not be afraid to just say a flat-out &ldquo;No&rdquo; to potential website projects.</strong><br />
&#8212;&#8211;</p>
<p>Any advice on how to do this tactfully? I get many requests for jobs that I&#8217;m just not interested in and have a hard time saying no because I&#8217;m just not sure how to tell them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
