<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Twitter For Churches &#187; response</title>
	<atom:link href="http://twitterforchurches.com/blog/tag/response/feed/" rel="self" type="application/rss+xml" />
	<link>http://twitterforchurches.com/blog</link>
	<description>Helping Churches Leverage Twitter</description>
	<lastBuildDate>Thu, 19 Aug 2010 13:02:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Crisis Communications for the Social Media Age</title>
		<link>http://twitterforchurches.com/blog/2009/06/29/crisis-communications-for-the-social-media-age/</link>
		<comments>http://twitterforchurches.com/blog/2009/06/29/crisis-communications-for-the-social-media-age/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 15:55:06 +0000</pubDate>
		<dc:creator>Anthony Coppedge</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[coppedge]]></category>
		<category><![CDATA[crisis communication]]></category>
		<category><![CDATA[response]]></category>
		<category><![CDATA[sherman]]></category>
		<category><![CDATA[Social media]]></category>
		<category><![CDATA[web worker daily]]></category>

		<guid isPermaLink="false">http://twitterforchurches.com/blog/?p=293</guid>
		<description><![CDATA[Aliza Sherman of Web Worker Daily wrote a very interesting piece about how companies should prepare and react to crisis via social media networks. I thought the same principles apply for non-profits and churches, too, and wanted to share this with churches to consider. Here are two compelling quotes from the brief article: My advice [...]]]></description>
			<content:encoded><![CDATA[<p><strong><a href="http://webworkerdaily.com/author/alizasherman/">Aliza Sherman</a></strong> of <a href="http://webworkerdaily.com/">Web Worker Daily</a> wrote a very interesting piece about how companies should prepare and react to crisis via social media networks. I thought the same principles apply for non-profits and churches, too, and wanted to share this with churches to consider.</p>
<p>Here are two compelling quotes from the <a href="http://webworkerdaily.com/2009/06/01/crisis-communications-for-the-social-media-age/" target="_blank">brief article</a>:</p>
<blockquote><p><em><strong>My advice is to plan now. Don’t wait for that communications crisis to take place before planning for how you’ll handle the fallout when something bad (inevitably) happens.</strong></em></p></blockquote>
<p>Here&#8217;s #5 from the list of things to do:</p>
<blockquote><p><strong><em>5. Don’t overthink. Running through committees, endless drafts and approval processes to get a response out there can cause far more damage than good. As long as you have taken the time to assess the situation and can take a rational, respectful tone in your response, even an awkward response is OK to start with, and buys you time to continue to respond to the problem.</em></strong></p></blockquote>


<!-- Begin TwitThis script (http://twitthis.com/) -->
<div style="text-align:left;">
<script type="text/javascript" src="http://s3.chuug.com/chuug.twitthis.scripts/twitthis.js"></script>
<script type="text/javascript">
<!--
document.write('<a href="javascript:;" onclick="TwitThis.pop();"><img src="http://s3.chuug.com/chuug.twitthis.resources/twitthis_grey_72x22.gif" alt="TwitThis" style="border:none;" /></a>');
//-->
</script>
</div>
<!-- /End -->

]]></content:encoded>
			<wfw:commentRss>http://twitterforchurches.com/blog/2009/06/29/crisis-communications-for-the-social-media-age/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

