As many of you know, I switched to a Mac laptop last year - see this post for my reasons. Based on anecdotal evidence, I have gotten the impression over the past few months that the Mac was making inroads into the corporate world. An article on MSNBC today confirms these impressions.
If you are thinking about a new computer, think about a Mac. I have been using a Mac and living in Google mail, calendar, and documents for nine months now, and I don’t plan on switching back.
I have begun reviewing the results of my survey on Internet ministry this week - over 300 churches and ministries responded and I am finding the results quite fascinating. As part of the survey, I gave respondents the chance to make themselves available to me for further, in-depth research. Many, many respondents gave me the OK to do this and I am now reviewing the web sites of those ministries in order to select a few for follow-up.
One of the most interesting trends I have found in reviewing these sites is that many of the sites who rated their Internet implementations as very successful are NOT those who have the coolest, most modern looking sites. In fact, many of these successful sites are very “web 1.0″ looking: Frontpage-style templates, simple coloring, and not a bit of flash animation! So what makes these sites so successful? I will find out the details when I contact the organization, but from the sites themselves I can see one key theme: quality content that is updated frequently. These sites had blogs, calendars, and pages that were full of recent, relevant information about the ministry.
This reinforces my ideas about what really makes Internet ministry successful: it is not the technology, it is the people and the processes. My research into these organizations is going to seek to answer questions about how this gets done: How do organizations keep their content fresh and updated? How much time does it take? Stay tuned…
As I have been working on a web site for my church, I have started to wonder if the whole idea of having an all-encompassing web site is becoming obsolete. It seems that all the effort going into designing, developing, and maintaining a web site is a tremendous amount of work that must be re-done every two or three years. And now, with the advent of XML, where the form and content have been separated (see this video for a good explanation of what I am talking about), it seems that we should instead separate content creation from web site design.
What I mean is this: for each type of content we want to make available, we should find the appropriate tool and use it. Then we should allow those who are consuming our content to view it in any way that they would like. For example, for a church calendar, use Google calendar (my personal favorite) to manage the calendar and then make it “public”, which allows someone to integrate it into their personal calendar, bring it in to their “home page” via an RSS reader, or just view it directly.
Or take another example: each ministry wants the ability to communicate with their members. A youth pastor could use a blog as a way to keep his youth group up to date on what is going on in the ministry, complete with photos (linked from Flickr) and videos (from YouTube). The members of his group could keep up to date by subscribing to the blog via email, importing it into their Facebook profile, or just viewing the blog directly.
OK, you say, this is all fine and good, but we still need a web site! Well, yes, you do need something that is a place with your basic information and a place to direct search engines, but it should really be an aggregation of all these other tools.
One key to successful web ministry is a distributed model of updating. By allowing each ministry to update their own information, you will get the most dynamic web site possible. But the challenge to this then becomes: how do you change the culture within your organization so that each ministry is willing to do this kind of updating?
So do you agree or disagree? Could a church (or other parachurch or nonprofit) have a successful web ministry without a full-fledged web site? Or am I going out of my mind?
Many of you know that I was in a bad car accident about 18 months ago. I survived what looked to be an unsurvivable accident, but my classic 1968 Mustang did not. For the past few months I have been looking for a “new” classic Mustang to replace it. I monitored several Craigslist listings using a custom Yahoo pipes feed that I created and finally, a few weeks ago, found the exact car I wanted. For those who want details: “A” code 289, pony interior, a/c, power steering. I really feel that the Lord led me to this car and its seller, a young man working in youth ministry at a nearby church. We made the deal a few days ago and I now have my new car. While nothing can ever replace my old car with all its memories, this car is a new adventure that I plan to keep and drive as long as I am able.
I just want to use this post to publicly thank the Lord for this blessing. And to thank my wife as well for supporting me in getting this car. And yes, I will let her drive it. 
The Internet Ministry Survey is now officially closed. I will now begin using my trained monkeys to analyze the results!
Oh my it’s been a long time since I’ve posted! Got sidetracked during spring break and busy with other projects. Well I’m back and will get posting again.
Warning: If you kept meaning to take my survey on Internet ministry but have not yet, take note: I will be closing the survey tomorrow! Go to the survey here. I am going to begin working over the data starting next week.
And if you haven’t registered for the Internet Ministry Conference yet, get busy.
When I teach my class on the management of information systems here at Biola, the first thing I present to the students is the concept of an information system being much more than just computers. My students learn on the first day of class that the five components of an information system are hardware, software, data, people, and processes. And it is the people and processes where information systems have the biggest impact on an organization. As I study how the Internet is used for ministry, I am becoming convinced that this breakdown of an information system can be modified slightly and used as a model for the implementation of Internet ministry. For a ministry to successfully implement a web presence, they must deal with three key areas: technology, people, and processes. And again, as with information systems, it is the people and processes components that are the biggest impact.
You can find books, blogs, vendors, consultants, and volunteers to help with technology. In fact, it seems as if everyone I know has an idea or is a self-proclaimed expert at one sort of technology or the other. And technology changes so fast that there is no way to always be doing the best and greatest of everything. Of course, technology is very important and a lack of good technology will get you in trouble, but it is not the key factor to success of an Internet ministry.
I am working with our church to develop a new web presence (to be unveiled soon). The technology we are using is suitable to our environment and is a huge step forward from our existing web site. As we are getting closer and closer to being ready to go live, though, I am getting more and more concerned that the people and processes will not be ready to go. I am finding that implementing technology is a whole lot easier that changing people’s work habits. Because of this, I have delayed the “go live” date of our web site by a month so that we can have adequate time to be sure that the people at the church fully understand their role in keeping the web site current and the existing processes can be modified properly so that the web site becomes fully integrated into the day-to-day activities of the church.
I think one of the biggest mistakes a ministry can make is to focus solely on the technology and the features of their web site and forget about who they are: the people who work in the ministry and the different tasks performed by the ministry. Both of these must be taken into account before any technological solution can become successful.
I am a guest blogger over at the Church Marketing Sucks blog. They have asked me to write a short series to give a sneak peek on how my research on Internet Ministry is going. Check it out…
Computerworld recently ran a cover page story on how businesses are using crowdsourcing to more quickly develop products and get feedback from target groups. Crowdsourcing is a method of using the Internet to allow multitudes of people to quickly give input to your organization via Internet-based software tools. Crowdsourcing can be used to get input from your customers on products, to do brainstorming from a larger group of people, or to simply increase customer loyalty by giving them a place where they can feel a part of your company. In a separate article written a couple of months ago, it is put this way:
Also compelling is the increasingly popular notion among companies desperate to stay competitive that the best, most direct and possibly cheapest sources of innovation lie outside the corporate walls, among customers and other previously hidden sources of talent.
One example of crowdsourcing given is Dell’s Ideastorm, where people can suggest ideas and then promote or demote the ideas. Dell examines the most popular ideas and, in some cases, implements them!
So how can this be used in Internet ministry? Would your church or organization have enough guts to give people the ability to give you suggestions? Would you be willing to think “outside the box” sometimes? Is there anyone doing this?
The Church Marketing Sucks blog has just completed an online poll on the three categories of Internet ministry that I posted about a couple months back. Interesting post and results…I’m still trying to figure out what the 5% people are replacing.
