Walking in Your Shoes as a Web Design Client
There’s an old saying that goes, “You don’t know a man unless you’ve walked a mile in his shoes.” Well, recently I had the opportunity to try on a pair of shoes I don’t normally wear: your shoes – that is the shoes of an OurChurch.Com client.
I am leading the effort to have the website of my own church, Cypress Meadows Community Church in Clearwater, FL, redesigned. After almost 11 year years of helping churches to create and maintain websites, I hope my insight and experience will help us develop an exceptional website to help advance the ministries of my church. Plus, I thought it would be a great opportunity to see things from a new perspective, that of an OCC client. So, I’ve asked the OCC staff to treat me like any other client (probably easier said than done since I’m also their boss). Not only will I be able to provide valuable feedback to our sales and design staff, but I’m also going to blog about the experience for the month or more so you get an idea of the design process from start to finish – working with the OCC staff, working with staff at my church, design decisions, and so forth.
I’m really excited about sharing this experience with you and I hope you find it interesting and insightful.
A Little About My Church
First, I want tell you a bit about Cypress Meadows. It’s a suburban church with an average Sunday attendance of around 400 in 2 services. We are very focused on reaching our community with the Gospel, and so our Sunday services are “seeker focused” with modern worship music, usually a drama or video, and a teaching that is applicable to every day life and designed to help spiritual seekers take steps towards faith in Christ. Having an excellent website is very important to our church, because we want people who are seeking God to find out about Cypress online and feel comfortable about visiting for a Sunday service.
Background on the Current Website
A year ago, Chris, our director of worship redesigned the church’s website. I advised him somewhat on the development. One of the first issues we faced was whether to develop a conventional website using Dreamweaver or develop the site with a content management system (CMS). Developing the site with a CMS would have enabled multiple people to manage the content of the site more easily and would have enabled the inclusion of functionality like a calendar, newsletter, and blogs. On the other hand, developing the site with Dreamweaver would enable the site to be completed more quickly and with more control over the design. In the end the decision was made to use Dreamweaver.
The new website looked excellent. However, all the website updates had to be done by Chris. As director of worship he’s a very busy guy and after a while the backlog of changes and additions that needed to be made to the website grew out of control. Information on the site was several months old, we weren’t getting information out to effectively inform people about upcoming events, and visits to the website began to decline. Not Chris’s fault – between music, helping an understaffed student ministry, and other responsibilities, he’s got more to do than hours in a day - but, it became a point of frustration for everyone involved.
Time for Change
Several weeks ago, Tim, the executive pastor (think COO) of the church called me concerning a solicitation he received from another Christian website services company. Tim and I are good friends and so we talked about the church website over lunch one day. He explained that everyone really loves the look of the site and they don’t want to change that, but something needed to be done to ensure that the information on the website could be kept current.
I explained the concept of a content management system (CMS) and how it would enable each ministry team leader to update their own pages on the website from the church or from home. I also explained how it would enable the church to integrate the newsletter, calendar, blogs, and more into the site. We even talked about the possibility of doing all registration for classes, events, and trips online through the CMS.
We also talked about the possibility of my leading the redevelopment of the website, and OurChurch.Com doing that redevelopment. We agreed to keep talking about the issue.
Shortly after that lunch, I started working on a “Vision for the Cypress Meadows Website” document. Not that I was going to dictate to the church how our website should look and function. But if I could be leading the redevelopment of the church’s website, I wanted to be able to clearly present to everyone involved what I had in mind so other could understand it and contribute towards a shared vision for the website.
- The appearance of a website is important, but having current, accurate information is even more important.
- No matter how awesome and faithful your site’s administrator is, if he/she is the only one who can update the site there will be times when your website is not up-to-date because he/she is busy, sick, or on vacation.
- A content management system (CMS) can make it easier to update a site and enable several people to update it, making it more likely the information on the site will be current and accurate.
Next post I’ll talk about the vision document and my meeting with the staff as I try to catch you up to where we are in the development process.
If you found this article interesting or helpful, please vote for it on Blogs4God so others will see it.