<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: 10 Reasons Why Web Ministry Applications and Initiatives Fail</title>
	<atom:link href="http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/feed/" rel="self" type="application/rss+xml" />
	<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/</link>
	<description>Exploring the Intersection of Church and Technology</description>
	<lastBuildDate>Fri, 10 Feb 2012 06:17:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: The Review - Digital Evangelism, the Religious Gap, and 1 Billion Web Users &#124; churchrelevance.com</title>
		<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/#comment-47226</link>
		<dc:creator>The Review - Digital Evangelism, the Religious Gap, and 1 Billion Web Users &#124; churchrelevance.com</dc:creator>
		<pubDate>Sun, 22 Feb 2009 16:03:16 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=3077#comment-47226</guid>
		<description>[...] 10 Reasons Why Web Ministry Applications and Initiatives Fail (1) Never Built. (4) Bad Modeling. (8) Strategy. Read the post for the other 7 reasons. [...] </description>
		<content:encoded><![CDATA[<p>[...] 10 Reasons Why Web Ministry Applications and Initiatives Fail (1) Never Built. (4) Bad Modeling. (8) Strategy. Read the post for the other 7 reasons. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: human3rror</title>
		<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/#comment-47222</link>
		<dc:creator>human3rror</dc:creator>
		<pubDate>Wed, 18 Feb 2009 11:04:04 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=3077#comment-47222</guid>
		<description>puahaha. the toolbox mentality is great. thanks for that! </description>
		<content:encoded><![CDATA[<p>puahaha. the toolbox mentality is great. thanks for that!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-02-18 &#124; This Inspires Me</title>
		<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/#comment-47221</link>
		<dc:creator>links for 2009-02-18 &#124; This Inspires Me</dc:creator>
		<pubDate>Wed, 18 Feb 2009 10:15:10 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=3077#comment-47221</guid>
		<description>[...] 10 Reasons Why Web Ministry Applications and Initiatives Fail (tags: apps ministry) [...] </description>
		<content:encoded><![CDATA[<p>[...] 10 Reasons Why Web Ministry Applications and Initiatives Fail (tags: apps ministry) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Harrell</title>
		<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/#comment-47220</link>
		<dc:creator>Matt Harrell</dc:creator>
		<pubDate>Wed, 18 Feb 2009 04:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=3077#comment-47220</guid>
		<description>Yes...using simple tools to help members communicate better. Tools that slightly expand on what they&#039;re used to. Just to make it easier for everyone to connect. I like it ;). </description>
		<content:encoded><![CDATA[<p>Yes&#8230;using simple tools to help members communicate better. Tools that slightly expand on what they&#039;re used to. Just to make it easier for everyone to connect. I like it <img src='http://cdn.churchm.ag/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Harrell</title>
		<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/#comment-47225</link>
		<dc:creator>Matt Harrell</dc:creator>
		<pubDate>Wed, 18 Feb 2009 04:38:13 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=3077#comment-47225</guid>
		<description>John, this is an excellent and timely post for me. And this advice is good for not just churches, but any organization. Building, selling and using software has so many facets it&#039;s crazy. I also agree with NicCharalambous that creating software that tries to meet every single need is a mistake. Look at what it&#039;s done to some of the big membership management apps that we continue to hear a lot of frustration with. And look at the crazy success of Basecamp and 37Signals (our inspiration for product design). Churches and orgs cannot be afraid to use different tools for different purposes. It&#039;s ok for your organization to have a toolbelt of software...or even a toolbox.  Good stuff here, thanks! I could comment on almost every point. Maybe if did I could increase my intensedebate count to an acceptable level ;). </description>
		<content:encoded><![CDATA[<p>John, this is an excellent and timely post for me. And this advice is good for not just churches, but any organization. Building, selling and using software has so many facets it&#039;s crazy. I also agree with NicCharalambous that creating software that tries to meet every single need is a mistake. Look at what it&#039;s done to some of the big membership management apps that we continue to hear a lot of frustration with. And look at the crazy success of Basecamp and 37Signals (our inspiration for product design). Churches and orgs cannot be afraid to use different tools for different purposes. It&#039;s ok for your organization to have a toolbelt of software&#8230;or even a toolbox.  Good stuff here, thanks! I could comment on almost every point. Maybe if did I could increase my intensedebate count to an acceptable level <img src='http://cdn.churchm.ag/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: human3rror</title>
		<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/#comment-47224</link>
		<dc:creator>human3rror</dc:creator>
		<pubDate>Wed, 18 Feb 2009 01:44:13 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=3077#comment-47224</guid>
		<description>i purposely left that one out. ;) but yes, thanks for adding it. love the comments that add the love. </description>
		<content:encoded><![CDATA[<p>i purposely left that one out. <img src='http://cdn.churchm.ag/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  but yes, thanks for adding it. love the comments that add the love.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: human3rror</title>
		<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/#comment-47223</link>
		<dc:creator>human3rror</dc:creator>
		<pubDate>Wed, 18 Feb 2009 01:44:11 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=3077#comment-47223</guid>
		<description>dude. you&#039;re speaking my language dude. </description>
		<content:encoded><![CDATA[<p>dude. you&#39;re speaking my language dude.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: human3rror</title>
		<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/#comment-47219</link>
		<dc:creator>human3rror</dc:creator>
		<pubDate>Wed, 18 Feb 2009 01:40:09 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=3077#comment-47219</guid>
		<description>word up man. you&#039;re probably learning this as we speak...! expert. word. </description>
		<content:encoded><![CDATA[<p>word up man. you&#39;re probably learning this as we speak&#8230;! expert. word.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NicCharalambous</title>
		<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/#comment-47218</link>
		<dc:creator>NicCharalambous</dc:creator>
		<pubDate>Tue, 17 Feb 2009 22:41:30 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=3077#comment-47218</guid>
		<description>This point ---------&gt; You don&#8217;t need to satisfy every single problem for every single ministry in one web ministry application or initiative. It&#8217;s ok to have more than one! &lt;---------------- EPIC! </description>
		<content:encoded><![CDATA[<p>This point &#8212;&#8212;&#8212;&gt; You don&rsquo;t need to satisfy every single problem for every single ministry in one web ministry application or initiative. It&rsquo;s ok to have more than one! &lt;&#8212;&#8212;&#8212;&#8212;&#8212;- EPIC!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BenCotten</title>
		<link>http://churchm.ag/10-reasons-why-web-ministry-applications-and-initiatives-fail/#comment-47217</link>
		<dc:creator>BenCotten</dc:creator>
		<pubDate>Tue, 17 Feb 2009 15:05:58 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=3077#comment-47217</guid>
		<description>The &quot;Too Futurist&quot; point hits home with where I am.  There are lots of things that I would like to do with our church in this area that we can&#039;t.  The primary reason is that it wouldn&#039;t make sense for our size and comfort level with technology.  That brings in point 7 about education.  It takes some time to baby-step people into being comfortable (and seeing the value of) some of these tools. 
 
Even if the leadership sees the value and understands its importance, if there isn&#039;t a critical mass of adoption in those you are leading the thing won&#039;t get off the ground.  Timing is everything. 
 
For us the trick has been to get people used to using email as a two-way communication tool instead of just a one-way announcement/broadcast tool.  Using chat, blogs (and getting them to comment), etc.  As the adoption rate of those basic tools increases it becomes easier to introduce other things that require a bigger buy-in.  Ultimately what we are doing is teaching people to be global thinkers instead of local/regional thinkers. </description>
		<content:encoded><![CDATA[<p>The &quot;Too Futurist&quot; point hits home with where I am.  There are lots of things that I would like to do with our church in this area that we can&#039;t.  The primary reason is that it wouldn&#039;t make sense for our size and comfort level with technology.  That brings in point 7 about education.  It takes some time to baby-step people into being comfortable (and seeing the value of) some of these tools. </p>
<p>Even if the leadership sees the value and understands its importance, if there isn&#039;t a critical mass of adoption in those you are leading the thing won&#039;t get off the ground.  Timing is everything. </p>
<p>For us the trick has been to get people used to using email as a two-way communication tool instead of just a one-way announcement/broadcast tool.  Using chat, blogs (and getting them to comment), etc.  As the adoption rate of those basic tools increases it becomes easier to introduce other things that require a bigger buy-in.  Ultimately what we are doing is teaching people to be global thinkers instead of local/regional thinkers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using memcached (Feed is rejected)
Page Caching using memcached
Database Caching 1/5 queries in 0.002 seconds using memcached
Object Caching 479/483 objects using memcached
Content Delivery Network via cdn.churchm.ag

Served from: churchm.ag @ 2012-02-10 03:11:44 -->
