Blogs

Delivering Change

Why Do We Need a Data Integrity Team?

Church silos continue to be a problem at many churches I visit. What many churches don’t understand is that there is more than one type of silo. Communication between ministries (written and verbal) is the easiest to comprehend. Many churches will say they haven’t spoken to anyone in the children’s ministry in as long as they can remember. By establishing cross functional or cross ministry teams you can help tear down that silo wall. There is another silo that exists in churches that I think is more harmful to a churches ability to minister to their congregation. Information silos.

When I first began working at Fellowship Technologies we called them islands of data. The children’s ministry uses an excel spreadsheet to track their volunteers. The children’s ministry spreadsheet contains the most recent contact information they can get from their volunteers. The men’s ministry uses Outlook to track and communicate with the men in the church about upcoming events. The women’s ministry had one of its ladies develop an Access database to track the women in the church. Where did all of these silos come from?

A Church usually starts with a central database to track contributions and should be using this database to track any updated information on its congregation. Did one day the Sr Pastor send out an announcement saying “I want you all to track only your people in separate databases!” Of course not. There are three common reasons for ministries to begin tracking "their" data in a separate database:

  • The church thinks their current database doesn't provide the functionality they need
  • The finance or member services ministry implements a "all changes to personal information must be submitted in writing and in triplicate" policy
  • Or they think other ministries don't need access to "their" data 

I am guessing at this point you might think I jump on the bandwagon and begin trashing my competitors. I mean there is blood in the water it is easily justifiable and the church would probably love to hear me agree with them. I never do. I usually say your current database probably has the ability they are complaining about. The problem is that the staff is under trained or the current database is difficult to work in.

As for the second issue that the finance/member services ministry wants everyone to submit any changes to a person’s communication values in writing via email; that is just silly. Ministry happens with or without a database. Pastoral staff and administrative staff move on to tracking their information in the easiest way possible with little or no regard to the church as a whole. They create a big honking silo. (honking is a technical term)

Don't even get me started on the third issue.  If you need an explanation for that one please read "Politics, Silos, and Turf Wars" by Patrick Lencioni.

This is where the data integrity team comes to the rescue of the church. A key element of the data integrity team is that there is a member on the team from every ministry. Does that mean the worship team needs to submit a person to something they have little or no interest in? Absolutely yes. The data integrity teams goal is to keep from saying things like “quit messing up my database”, or “I am going to lock every user out of this system if I see one more miss typed email address!” Their job is to train and empower the end users in how to properly input data.

Should every user be able to input data? Absolutely NOT! But when a user needs to input data to perform their roll in ministry they should be properly trained and vetted by the data integrity team. If that user offends… retrain them. If the user continues to mess up the database restrict their access and retrain them.

Lastly the only way to be successful as a data integrity team leader is to face each day by saying “what am I going to do today so that the church does not need me anymore”. Scary I know. But you should think of the data like sand, the more you squeeze it in your fist the more sand escapes.

God Bless,

Matthew McMaster
Delivery Manager 
(with lots of help from most of my team!)

P.S.  If Granger agrees with me then I must be on the right track!

 

http://kemmeyer.typepad.com/less_clutter_noise/2008/02/we-dont-have-a.html

 

Published Thursday, February 07, 2008 8:48 PM by FTDeliverySvcs
| Filed under:

Comments

 

pschott said:

As noted, I don't completely agree with Kem's post, but I'm a data guy to start with.  That being said, you are right on the money here.  And this concept doesn't just apply to church life, it applies to business life as well.  At my former company, there was definitely a cycle that affected the business from the Marketing department getting new customers on board all the way through our loan servicing department.  If one department started to fall down, the others all noticed, even if slowly.  Even worse, when one department kept their information to themselves, we couldn't make wise business decisions because we were too focused on a small area of business.

I'd like to say on the Church front that I think this is even more critical.  Every ministry has details about their members that only they know.  The small groups keep the most recent demographics and really know the person.  The Education (SS, Bible Study, etc) areas pretty much know how often people attend and whether they seem to be growing (overlap with small group, but different fronts).  Finance people know how often people give, whether it's faithfully or not, and whether the people could be counted on to continue to do the same.  Children/Youth people know the kids better than any others and can be a great source of outreach to parents and friends  Etc, etc, etc.

Once people start maintaining this data outside of the main system, it's really hard to stop.  It's a quick step just to enter in someone and think "I'll put this in the main system later", then we go into the phase of "I'll enter a batch into the system later", and finally into "There's too much here to put into the main system, I'll just make this the main system for my area for now."

One of my former churches had something similar, but it was more of a session to share our information with each other and keep everyone informed about the current happenings.  We didn't really have a ChMS at the time worth speaking of.  Those meetings were really helpful to keep us from doing something in our own area and leaving others out of it.  If we'd had some shared data as well, I think we could have done even better in our ministry and follow-up efforts.  We had a huge back-door that just wasn't being closed and we lost a lot of members who just fell through the cracks.

Good post, Matt.  I hope people take this to heart.  It's so important not to silo the information.

February 7, 2008 5:17 PM
 

jlandon said:

Here is a great post by Kem Meyer from Granger on this subject.  She even has a visual illustration!

http://kemmeyer.typepad.com/less_clutter_noise/2008/02/we-dont-have-a.html

Jeff Landon

February 11, 2008 10:26 AM
Anonymous comments are disabled