I’ve been building web applications and leading teams that build web apps for a long time now, mostly for the Fortune 50 and marketplace.
I’ve had much more failures than success (and the fact that I’m writing this right now is proof of that… because if I was a “success,” as typically understood, I’d be a billionaire sitting on some nice beach chair in the middle of the Mediterranean).
Jumping into the “ministry” and “church” world has been “interesting.”
I’ll leave it at that.
But the conversations that I’ve had in the past few months with a host of people has brought me to very similar conclusions about why web applications and initiatives fail.
Here’s my Top 10 Reasons why Web Ministry Applications and Initiatives Fail:
1. Never Built
People love to dream. I love to dream. The problem is that there are so many great ideas out there and not enough gumption to actually get off your butt and go do it.
I’ve heard absolutely amazing ideas about how the web can impact the way we do ministry. So far, I’ve seen almost zero follow through.
That’s just sad. Things don’t get beyond the “conceptual,” beyond the drawing board, beyond the prototypes on paper napkins.
2. Heresy and Unorthodoxy
This is a big for me. Many times things on the web fail because of pressure from the “historical powers that be” that tell you that what you’re doing is as close to “heresy” as possible without saying the actual word.
So you get scared. You balk. You run away.
On the other side of the coin I’ve seen (and heard) of some pretty ridiculous uses of web technology that are truly “unorthodox” and borderlines stupidity, not just from a conceptual perspective, but from a time, strategy, and a resource one as well.
A few of these have absolutely no connection with the ministry, or the organization that sponsors it, and not even the closest touch point for the Gospel of Jesus Christ. What a waste.
We need to be wise with our resources, for they are truly limited.
3. Too Futurist
I use this term loosely but to prove a point because there’s some theological and historical implications with using the word, so bear with me here.
The simple fact is that there are a lot of great ideas but perhaps they are ideas that are just not “at the right time” for you, for your ministry, or for the world.
Perhaps you’re too advanced in your thinking. This isn’t necessarily a bad thing, but it can be one if managed unwisely. You may just be too ahead of the curve for your idea to hold much merit.
This can be a painful lesson to learn. I’m learning it nearly every day. I see the “merit” of a web application or methodology; the rest of the ministry doesn’t.
My job is to meet the needs of the ministry today. My other job is to educate them for tomorrow, in humility. Often times I forget both of them; sometimes at the same time.
4. Bad Modeling
Here’s a good one. Some argue that online web experiences should model near identical experiences in the offline world.
WRONG.
The mediums are completely different. Their uses and applications distinct. Just because the typical schedule of a Sunday Service (Praise/Worship, Sermon, Tithes/Offering, Communion, Benediction, etc) “works” doesn’t mean that it’ll “work” in the online setting.
Now, there is some wisdom in comparing and using it as a jump-off, but a near-identical experience sometimes just doesn’t work.
5. Problem Solvers
Sometimes we think that the web can do everything and that our web apps should be a model of that mantra.
WRONG.
Web apps for ministry have had the best success that have focused on a specific need and been built to provide that specific need, without adding the thousands of “bells and whistles” that are possible.
Find a need and fill the need. If the guy is thirsty, give him water. Then, after he’s full, ask him if he’s hungry.
You don’t need to satisfy every single problem for every single ministry in one web ministry application or initiative. It’s ok to have more than one!
6. Not The Right Person
I’ve talked to a few of these already. Often times the people that are the most enthusiastic about social technology are the people who are the most ignorant of how to actually get it done and are the wrong people to actually go do it.
In a technologically-social world where democratization is uplifted and where everyone is an “expert” we have to remember that that’s just not the case: Not everyone is an expert. And that’s ok. We need non-experts too, but just because you use the software and “use every social network under the sun” doesn’t mean you have the means or know-how to build one yourself.
Just because you think you’re a leader doesn’t mean that you are one or that people will follow. Ask Seth Godin about that one.
Find the “right” people to lead your team, to build the app, to blog about your ministry.
7. Terrible Salesmanship Instead of Education
This may have a little to do with #6 above, but oftentimes things can’t get moving because you can’t simply “sell” the idea to your ministry team or those that hold power over the “budget.”
You simply can’t convince them that this is a necessary next step.
But perhaps you’re approaching it the wrong way. Perhaps you need to focus more on “educating” them about the technology, the application, and the potential. Perhaps you need to do a little research, provide metrics, and case-studies.
Perhaps you have to do a little “work.” Just telling them they “have to have it” apparently doesn’t work too often, right?
8. Strategy
I’d love to spend some more time on this, but I won’t. The sad thing is that more than a few web ministry applications and initiatives have launched without a strategy.
That’s terribly scary to me.
So, they fail because they don’t have one, not because they couldn’t get launched.
9. Ego
The web application and ministry initiative is ego-driven. FAIL.
10. The Almighty Greenback
The web application is built with the ultimate purpose of making money. This may not “fail” out the gate, but long term I can’t really see anything good coming of it.
Whew…
So, there you have it. In my limited experience in the ministry-sector, that’s what I’ve seen already. There is hope, though. I believe it, or I would have quit already.
Adam_S says
You forgot the one that I have seen before (related to 10, but from a different side). 11) If it is a Christian product, why are you charging for it? All things Christian should be free.
There is some point to this, many Christian organizations really don't have much cash, so you need to consider this when you are building something, especially if it is targeted to church plants or other low income organizations.
But at the same time just because you are Christian doesn't mean you shouldn't be paid for your services. (I speak as a consultant to Christian non-profits who donates a lot of time to different ministries.)
human3rror says
i purposely left that one out. 😉 but yes, thanks for adding it. love the comments that add the love.
BenCotten says
The "Too Futurist" 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't. The primary reason is that it wouldn'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't a critical mass of adoption in those you are leading the thing won'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.
human3rror says
dude. you're speaking my language dude.
Matt Harrell says
Yes…using simple tools to help members communicate better. Tools that slightly expand on what they're used to. Just to make it easier for everyone to connect. I like it ;).
human3rror says
puahaha. the toolbox mentality is great. thanks for that!
NicCharalambous says
This point ———> You don’t need to satisfy every single problem for every single ministry in one web ministry application or initiative. It’s ok to have more than one! <—————- EPIC!
human3rror says
word up man. you're probably learning this as we speak…! expert. word.
Matt Harrell says
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's crazy. I also agree with NicCharalambous that creating software that tries to meet every single need is a mistake. Look at what it'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'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 ;).