<?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; reasons</title>
	<atom:link href="http://twitterforchurches.com/blog/tag/reasons/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>In Their Own Words: Park Church on Twitter</title>
		<link>http://twitterforchurches.com/blog/2009/01/29/in-their-own-words-park-church-on-twitter/</link>
		<comments>http://twitterforchurches.com/blog/2009/01/29/in-their-own-words-park-church-on-twitter/#comments</comments>
		<pubDate>Fri, 30 Jan 2009 02:14:54 +0000</pubDate>
		<dc:creator>Anthony Coppedge</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Park church]]></category>
		<category><![CDATA[reasons]]></category>
		<category><![CDATA[schraeder]]></category>
		<category><![CDATA[tim]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://twitterforchurches.com/blog/?p=31</guid>
		<description><![CDATA[Twitter. 140 characters to communicate a message, an idea, or  a thought. I don’t know about you but I’m addicted. Twitter provides a great way to stay connected with people you know, people you want to stalk (that was sarcastic) and provides a great way to network and connect with people you might not normally [...]]]></description>
			<content:encoded><![CDATA[<p><a style="display: inline;" href="http://timschraeder.typepad.com/.a/6a00d8341c972753ef010537027d19970c-pi"><img class="at-xid-6a00d8341c972753ef010537027d19970c" title="Whatareyoudoing" src="http://timschraeder.typepad.com/.a/6a00d8341c972753ef010537027d19970c-800wi" border="0" alt="Whatareyoudoing" /></a></p>
<p>Twitter. 140 characters to communicate a message, an idea, or  a thought.</p>
<p>I don’t know about you but <a href="http://twitter.com/timschraeder">I’m addicted</a>.</p>
<p>Twitter provides a great way to stay connected with people you know, people you want to stalk (that was sarcastic) and provides a great way to network and connect with people you might not normally have the chance to interact with.</p>
<p>Using Twitter for yourself is one thing – but using it for your church is something completely different.</p>
<p><a href="http://www.churchmarketingsucks.com/archives/2009/01/its_twitter_tim.html">Church Marketing Sucks</a> gave <a href="http://parkcommunitychurch.org">Park</a> a nod in an article they posted about churches that use Twitter, so I thought I’d take a minute to tell you why and how we decided to use it, and how we hope to expand our use of it in the future.</p>
<blockquote><p>Before I go further I’ll say this… <em>we have absolutely no shortage of ways to communicate. Facebook, texting, Twitter, email, websites… you name it. <strong>Just because we can doesn’t mean we should.</strong> We should only use technology that fits the context and the everyday life of the people in our churches and in the communities where we find ourselves.</em></p>
<p><em></em><em>Before you decide to invest time, energy and resources in any new media, you need to stop and ask yourself why. Are you engaging in a conversation on a medium people in your community are using? Or, are you just trying to up your “cool” factor? </em></p></blockquote>
<p>So Twitter&#8230;</p>
<p>I set up an account for Park on Twitter about 6 months ago and connected it to the email address where a majority of our churchwide emails generate from (mine).</p>
<p>I didn’t do anything with it but let it sit there. I sat and watched. And I saw more and more people who were in our church were finding us (through the Search feature on Twitter) and saw that it was indeed something people in our church were using.</p>
<p>After we crossed 50 followers (who actually attend Park) I decided enough of our people were using it to go public with it and start using it… which we did a little over a month ago.</p>
<p>Since that time, we’ve accumulated quite a few followers and have seen it take off and are excited to see where it goes from there.</p>
<p><strong>How we plan to use it…</strong></p>
<ul>
<li>communicate churchwide news and announcements</li>
<li>notify people about upcoming events</li>
<li>give people a sneak peek into the life of our church office(we have fun ideas planned!)</li>
<li>advance previews of videos and print</li>
<li>as a means to communicate prayer needs for our church family</li>
</ul>
<p><strong>Who we will Follow…</strong></p>
<ul>
<li>People who attend Park, or people who follow that live in Chicago</li>
<li>Chicago-based media and news outlets</li>
</ul>
<p><strong>Other benefits of using it…</strong></p>
<ul>
<li><strong>Transparency</strong> – not that we’ll share all of the nitty gritty of church life, but it’s a great way to be transparent, to share and to lower the barrier between people who attend Park and our staff. It creates space for us to interact.</li>
<li><strong>Research</strong> – it will serve as a great window into the lives of some of the people who attend Park – we’ll be able to see and observe what they care about, what’s on their mind, etc.</li>
<li><strong>Presence</strong> – I think it’s great to be present where people are talking… and if a conversation our people are having is happening on Twitter, then we should be there too.</li>
<li><strong>Connection</strong> – You never know who you might be able to connect with via Twitter. Some people would never come up to you in person, but will interact with you online. Obviously, you don’t want to sacrifice personal contact, but this could serve as a bridge to creating personal contact.</li>
</ul>
<p><strong>Who Owns it…</strong></p>
<ul>
<li><strong>For the interim, I do</strong> but we are exploring ways of having multiple staff members to have access to it and to update our status and to reply and interact with Park people who use Twitter.</li>
</ul>
<p><strong>Final Thought&#8230;</strong></p>
<p>I want to re-iterate what I said earlier&#8230; just because you can, doesn&#8217;t mean you should. I think  we often tend to look at what other people (or in this instance, other churches) are doing and be quick to jump on the bandwagon.</p>
<p>Before you do, just make sure it&#8217;s the right direction for your church. If it&#8217;s not going to put you into closer relational proximity to the people in your church, don&#8217;t do it.</p>
<p>I’m no expert on how to use Twitter for a church&#8230; I&#8217;m still learning!, but <a href="http://twitter.com/anthonycoppedge">Anthony Coppedge</a> recently released a $5 e-book entitled <em><a href="http://www.twitterforchurches.com/" target="_blank">The Reason Your Church Must Twitter</a></em>. I encourage you check it out!</p>
<p>Down the road we&#8217;re going to see how it goes and possibly expand Twitter to other audiences in our church&#8230; singles, 30s, small group leaders, etc. In the meatime, feel free to follow us <a href="http://twitter.com/ParkChurch">@ParkChurch</a></p>


<!-- 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/01/29/in-their-own-words-park-church-on-twitter/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
