<?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: Development Fatigue</title>
	<atom:link href="http://www.asmallchange.net/development-fatigue/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.asmallchange.net/development-fatigue/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=development-fatigue</link>
	<description>Making Sense of Fundraising</description>
	<lastBuildDate>Wed, 08 Feb 2012 18:58:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Stephen Peacock</title>
		<link>http://www.asmallchange.net/development-fatigue/#comment-372</link>
		<dc:creator>Stephen Peacock</dc:creator>
		<pubDate>Fri, 31 Oct 2008 18:32:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.asmallchange.net/?p=221#comment-372</guid>
		<description>Jason,
Your post addresses an issue that is often overlooked.  I too have &#039;hit the wall&#039; in terms of development fatigue and have practiced your recommendations myself.  I&#039;d like to emphasize the importance of number one.  Taking a daily break, for lunch or otherwise, away from the office was really key for me.  Even if only for 20-30 minutes the breaks allowed me to quickly reflect on the morning, set priorities for the afternoon and decompress at the same time.

I would also concur with Leanne, communicating with the team, your boss and sometimes even a board member helps keep everyone up-to-date on the day-to-day development work experience, engages them in helping to overcome challenges and provides an opportunity to support one another.</description>
		<content:encoded><![CDATA[<p>Jason,<br />
Your post addresses an issue that is often overlooked.  I too have &#8216;hit the wall&#8217; in terms of development fatigue and have practiced your recommendations myself.  I&#8217;d like to emphasize the importance of number one.  Taking a daily break, for lunch or otherwise, away from the office was really key for me.  Even if only for 20-30 minutes the breaks allowed me to quickly reflect on the morning, set priorities for the afternoon and decompress at the same time.</p>
<p>I would also concur with Leanne, communicating with the team, your boss and sometimes even a board member helps keep everyone up-to-date on the day-to-day development work experience, engages them in helping to overcome challenges and provides an opportunity to support one another.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leanne</title>
		<link>http://www.asmallchange.net/development-fatigue/#comment-371</link>
		<dc:creator>Leanne</dc:creator>
		<pubDate>Wed, 15 Oct 2008 16:23:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.asmallchange.net/?p=221#comment-371</guid>
		<description>Jason,
I&#039;ve been reading your blog for awhile now and have thoroughly enjoyed your posts.  This particular subject hits very close to home.  In addition to the points you raised, I&#039;d like to suggest adding one more.

Communicate with your team/boss.

In these unstable and uncertain times, the pressure for Development Directors and other fundraisers to produce &quot;results&quot; is huge.  Communicating the reality of the situation (donors may take longer to give after an ask, may not give as much as usual, or may not give at all) goes a long way.

I have found that doing this brings a greater awareness to the funding climate the rest of the team usually is not aware of and it opens up dialogue for greater collaboration.</description>
		<content:encoded><![CDATA[<p>Jason,<br />
I&#8217;ve been reading your blog for awhile now and have thoroughly enjoyed your posts.  This particular subject hits very close to home.  In addition to the points you raised, I&#8217;d like to suggest adding one more.</p>
<p>Communicate with your team/boss.</p>
<p>In these unstable and uncertain times, the pressure for Development Directors and other fundraisers to produce &#8220;results&#8221; is huge.  Communicating the reality of the situation (donors may take longer to give after an ask, may not give as much as usual, or may not give at all) goes a long way.</p>
<p>I have found that doing this brings a greater awareness to the funding climate the rest of the team usually is not aware of and it opens up dialogue for greater collaboration.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

