Mike, you have some very good questions which can contribute to the overall solution.  The issue does come down to a mind set; the “Volunteer” mindset compared to a “Corporate” mindset.  By volunteer I am not referring to the webmaster but an over arching structure.  In a volunteer heavy environment when one person leaves and another steps up with wild and crazy ideas, the leadership may be hesitant to say anything for fear of loosing all vested.

I especially like and dislike the governing structure idea.  My dislike comes out of my observation of many committee’s falling down on the job.  However, if care is taken this can be a great method to get ownership into the hands of decision makers which will value it more.  The more people that help draw up the plan, the more that will support or defend it.

On a personal note I wish to also thank all of the very talented and gifted men and women out there who have shed blood, sweat and tears on such grand projects.  I also want to remind you of something that I have learned in ministry.  If and when they leave your work on the side of the road remember that it is not a personal attack or invalidation of your devotion.  Often time it is the cause of well intentioned people who do not see past there own enthusiasm and desire to serve.  Each and every one of you are worth a great deal.  If you doubt that statement simple turn to John 3:16.  You are worth enough to God that He died for you.

Keep up the great work for the kingdom everyone.  If that means you get paid for your service, then go for it.  if you are able to donate your time, then go for that.  Just remember, it’s all about Jesus.

In His Service
Mike

I think you are heading in the right direction. You are asking the right questions. Here are my thoughts.

Designing and implementing a ministry website needs to be a team effort. It’s important to never do ministry alone. It’s really about more than building the site. It’s about getting to know other Christians and building character through a shared goal. I have heard before that there should be no superstars, only superteams.

There are many roles that need to be filled on a web team and many aren’t technical. For instance, you mention the need for good content. There probably needs to be a writer on the team. Someone to contact various ministry leaders and write the content. This person more than likely needs little if any technical knowledge. Other roles might include someone to coordinate the team, someone to develop a communication strategy and someone to develop the web strategy. The exact structure of the web team should vary between churches, but it’s important to make it a team effort. This will most likely prevent anyone from joining the team and making sweeping changes once you are gone.

It’s also important for everyone on the team to seek out and train a replacement from day one even if the person has no intention of moving on. It’s a good way to bring those on the fringe into a supportive small group team. It also allows plenty of training time. Eventually once the person is trained, you can move on to other important areas on the web team and then again seek out a replacement and begin to train him or her. It’s a never ending process that helps to continually expand the team with competent successors.

There is a difference between a committee and a team. A team does ministry and a committee usually just gives advice or discusses a topic without much action. I wouldn’t suggest a committee. Everyone on the team needs to be doing ministry. A team creates ownership.

Thanks for reading my comment.