October 4, 2011 | Anna Belle Leiserson
Arguably the single most important step of a congregational website redesign is figuring out what users need — not what you think they need and certainly not just what you need — but what they really can use.
Sometimes you already know. For example, if your congregation doesn’t have a site at all, your number one need is a no-brainer. Of course even then you have to determine what specifically is most needed for the site-to-be. You can’t do it all with one design or redesign.
The easiest way to get this information is (no surprise here) to do needs assessments. It’s also one of the most enjoyable aspects of redesign — for everyone involved. People love to be asked their opinions, especially if it’s close to their hearts. At the same time, it builds support and enthusiasm for the project.
1. Identify the site’s “stakeholders.” The Web is divided into three great parts: users (your site visitors), builders (those who put the site infrastructure in place, i.e. you and me) and stakeholders (typically the leaders of the organization).
At my church the primary stakeholders are the staff and the committee chairs responsible for programatic parts of church life such as Worship and Fund Raising. As we move towards having a real intranet, the Board is also becoming a major stakeholder. In any event it’s a good idea to keep the Board happy, so why not do a needs assessment with them too?
2. Schedule meetings with the primary stakeholders. In my experience this is the most challenging step. Everyone is so busy.
What I did was to email the senior minister and the chair of the board. I told them a bit about the redesign and explained the benefits of the needs assessment. I’m married to the Committee Council Chair so it was easy enough to contact him. The minister invited me to the very next staff meeting, and the Board Chair suggested lunch. That was great fun, and turned into an invitation to the Board’s retreat. The Council meets very little and I wasn’t able to schedule with them. Instead, I set up a general session and encouraged Council members in particular to come.
The time required varies according to the number of people. Our staff of 5 took 45 minutes (though an hour would have been better). The Board of 12 took 1.5 hours. The general session we gave 1.5 hours.
3. Figure out the questions most likely to elicit the information you need. The questions I came up with were:
For the Board I did a full Communications Needs Assessment. (It has to do with our strategic plan.) In case it might be helpful, here are those questions too.
4. Conduct the meetings. What’s needed for these again depends on the number of people. If it’s 10 or more people, you’ll need another person to help, so one can run the meeting while the other records the answers. You’ll also need a flip chart to do the recording on. Between 5 and 10, a flip chart and second person help but aren’t critical. For 5 and under, one person and a pad of paper are fine.
5. Write up your notes. Do this as soon as you possibly can, so you can fill in blanks. Then share your notes with the stakeholders.
My guess is you’ll be delighted with the results for relatively effort on your part.
For all three of our sessions, there were excellent ideas (some that didn’t even have to wait for redesign) and the enthusiasm and support were palpable. These sessions have created a sense of group ownership like never before. In the past the website has been somewhat siloed — perceived as work for only our Communications Committee. But now, a variety of leaders know and care about it. More to the point some are already building new web pages. The best example is our chair of Fund Raising. She wanted a Web page listing books and linking to Amazon as an affiliate. A retired librarian at that same meeting gladly volunteered to manage it. I’ve now set up a WordPress page for them and they will launch it as soon as our affiliate status is in place.
Similar to needs assessments, surveys can also help you get at what’s most needed. And they are remarkable easy to do using tools like SurveyMonkey. However, before you go down that path, be sure to get permission from leadership. At times, congregations can be over-surveyed. (That’s the case right now for my congregation.) In addition, I’ve never found the data from them as useful as the data from needs assessments, nor do they help build support. As a result, I wouldn’t recommend doing surveys instead of needs assessments, but they can be a helpful supplement.
If you’re interested in doing a survey, I’d suggest that you be as brief as possible and start with a warm but quick welcome — for example, “We value your opinion. Please help us improve our site by answering just 4 questions.” Here are some questions you might want to consider (but please don’t use all of them):
The next step in our series will be drafting a “roadmap” of work. But that’s a couple of weeks away, since this weekend is Mr. Web Diva’s birthday and we’re having a tree climbing party. Consider it a little break. Until then, happy redesign.