To partially quote Matthew 6:24:
“No one can serve two masters. Either he will hate the one and love the other, or he will be devoted to the one and despise the other.”
The Good Book was talking about God and money, of course, but it could have been talking about Web site visitors. You see, church Web sites have an interesting challenge in front of them: they have to search two audiences equally well.
Here are 5 aspects to serving these two masters:
First, we have the Visitors. These are the people that found your URL next to your listing in the phone book (you have it there, right?), on the side of your bus as it drives around town (it’s there too, right?), or perhaps just through searching the Web (Google’s local search will play a big part in this). These folks are perhaps looking for a church home, and have come to your site as part of their search.
On the other side, we have the Members. These are people who already belong to the church and are active in various activities and groups. (The word “Member” here doesn’t imply any formal church member â€” just that they attend regularly and are somewhat involved in the operations and activities of the church.)
These two groups have vastly differing needs and expectations for your Web site.
1. Visitors want brochureware. (What’s brochureware?) They need quick, relatively superficial information about the church. How do I get there? What time are the services? What denomination does the church represent? Who are the people that I’ll be seeing up front on Sunday morning? If I decide to make this my church home, what types of activities could I become involved with?
In a lot of ways, you sell your church to Visitors in the same way that a company sells its product â€” by carefully asking the question, “what information would I be looking for if I was in the same position” Just like a company doesn’t display its help ticketing system or knowledge base on their front page, neither should your church print meeting minutes or the upcoming budget details on yours.
It’s not hard to satisfy Visitors. Brochureware has generally been easy. But the complication arises when you take the Members into account. What does this group need from your Web site? Sales-ish brochureware? Nope…
2. Members want an intranet. Ah yes, an intranet â€” usually the province of corporations. But churches are sometimes quite the same thing. You have a group of people, united in the same cause, who work at tasks to further that cause. To this end, the Member needs a lot of information quickly, without unnecessary hand-holding.
- They need schedules. They don’t need superficial information about the events and ministries available â€” they need to know when the preschool playground cleanup project will begin on Saturday morning, how they should be dressed for it, and what side dish they need to bring for the potluck afterwards.
- They need contact information. They know that Pastor Bob went to seminary in Cleveland and did his dissertation on the Gospels, but right now they just need every phone number and email address at which they might be able to contact him because Mary’s cousin was in a serious car accident and the family needs someone to lean on.
- They need news. They spend five months a year in Arizona so they don’t know that the furnace went on the fritz and there’s a goodwill offering to get it fixed.
- They need records. The new sanctuary project is on schedule, but they like to review the Building Committee meeting minutes anyway because they were in contracting for 20 years and they can spot a construction problem ten miles away.
The problem with throwing all this information at every Visitor who walks through the virtual door is that you run the risk of alienating them. I keep thinking of the undersea current which the Surfer Dude sea turtle rode in Finding Nemo â€” a huge current of non-stop, straight-to-the-point information that assumes a lot of background knowledge can make the Visitor seem like there’s no way to “jump into the flow.” Your church can come off looking very clique-ish if you’re not careful.
So, given that these two audiences are so different, how do you meet both their needs with the same Web site? It’s a tricky question, but here are some ideas:
3. Balance it carefully
This is what usually happens â€” not by plan, but by lack of one, really. However, if you’re careful, you can have discrete links on each page that allow the Member to get the information they want without alienating the Visitor.
For instance, at the bottom of a page describing the local MOPS chapter, you could have a link with something like “If you’re interested in MOPS, visit our Events Calendar for a list of upcoming meetings.” The trick to this is taking time to acknowledge that there are two different groups and keep both sets of needs in mind as your develop and expand the site.
Visitors get the home page, but Members bookmark a “hidden” home page
Well, not “hidden,” but not the default domain home page either. The index.html page that comes up for “www.mychurch.com” can be for the Visitors, full of all sorts of brochure-ish information about the church.
However, Members know â€” via a slug on the home page, through the grapevine, through a mailing list, etc. â€” that they should bookmark “www.mychurch.com/news.html” or because that’s where the meat of the site really is.
4. Use an alternate means of Member communication
Leave your entire Web site for the Visitors, and use another Net-based means to communicate with the Members. A listserv can go a long way, and it works well because you usually have email addresses for your core members. If you have some Net saavy folks, perhaps issue the core news via RSS.
Obviously, there are some limitations here. For instance, how are you going to get contact information on demand from a list-serv? There are ways, but none of them are obvious or elegant.
(Drawbacks or not, this model gets used a lot in today’s churches. Like the venerable “meeting after the meeting,” a lot of the real communication in churches happens via mailing list over any other method.)
5. Have two Web sites
Drastic, sure, but it can work well in a lot of situations. Hosting accounts are cheap, and this lets you use a brochureware system on your Visitor site (“www.mychurch.com”) and a more focused site for the Members (“intranet.mychurch.com”).
An added benefit of this is that your Members can even use a dedicated community/intranet system rather than a standard Web site. Intranets.com or CommunityZero would serve your core members exceptionally well, with their built-in calendars, file libraries, and news systems.
A drawback: if you have to pay by the user, this can get painful. However, there are any number of self-hosting, open-source solutions (PostNuke, for instance) that would do the same thing with some hacking. For you Microsoft fans, SharePoint works very well out-of-the-box, and you can get a lot of that functionality with a copy of FrontPage.
So, there you have some thoughts about how to handle the unique needs of a church Web site. Even just acknowledging the problem and keeping it in the front of your head while developing the site can make a world of difference.