TechShepherds.com

Outsource to Free Up Staff, Not Cut It

In a recent article in Baseline Magazine, John McCormick  addresses the subject of outsourcing IT.  Now, I have been in the place where I had to fight for IT budget and resources for the local church.  You have been there, too:  that place where you had to justify your position and the need for technology in ministry.

The very thought of outsourcing may cause thoughts of the inability of the IT staff to handle their job.  However, McCormick makes a great point:  outsourcing the mundane but necessary tasks frees the IT staff to be able to vision cast and push the ministry forward.

So, get out of the rut of fixing printers,  defragging hard drives, etc.  Outsource those tasks so you can push forward.

To whom do you outsource?
This becomes the big question.  There are two options available. 

1. Consultants:  These are experts in the IT industry.  This option is good when you need help and need it now.  Because you are paying them a fee, you can expect quicker response during emergencies.
2. Volunteers:  You might be surprised at how many IT experts you have in your church.  While this can be a challenge, it can also be very rewarding.  Fellowship Church's IS Director, Terry Chapman, shares on his blog about how they use volunteers in the IT ministry.

What benefits can come from this "outsourcing"?

1. Volunteers get involved and find their place in ministry.
2. You expose consultants to the Gospel (if you treat them in a Christ-like manner)
3. Staff will be able to focus on identifying needed technology enhancements and deliver them to members and guests, thus increasing the reach of the Gospel.

What may be hindering your project?

Implementing new technology of any type can be a challenge in and of itself.  However, rarely is the technology itself the reason for difficulty in implementing the technology.  I am currently part of a team that is implementing a new church management solution from Fellowship Technologies called Fellowship One. 

To be completely upfront, we have run into some challenges in the implementation.  However, Fellowship One has nothing to do with those challenges.  I give my full endorsement for Fellowshp One and believe that every church seriously take a look at it.

The challenges we have faced have come from people.  This was surprising to me until I read an article in Baseline Magazine called "Projects Don't Fail, People Do."  I recommend you take time to read this one-page article.

I have learned a lot through this project that I hope to share in the coming days.  However, here are some thoughts I have to share to get this started:

Senior Manage/Leadership MUST be behind the project 100%:
This is absolutely crucial.  If senior leadership does not have total buy-in to the project, you will not be able to get it from the rest of the staff or church.

Don't go it alone in the discovery phase:
Having representation from vital ministry areas on the team that evaluates a product/solution will increase excitement among staff and ministries.  The more people excited about it throughout the process, the more tolerant they will be through the transition.

Assemble an on-sight implementation team:
While much of the IT project will need to be handled by people with an IT mind-set, there are usually other non-IT related aspects that can be handled by other staff.  The other part of that is that they will have a better idea of how it should be done in the first place.  The more heads that get together to think through all of the items, the more thorough and smooth the implementation will go.

ROI is bigger than budget expenditures:
Too often churches only look at the expense items that have a hard number and dollar sign associated with them.  The finance committee or staff in charge of the money are rightly concerned with ensuring good use of money.  However, return on investment (ROI) needs to be considered in any IT project.  If the technology solution will not save time and money, then it may not need to be implemented in the first place.  Once it is determined that the solution will make be a valuable tool for the organization, then whatever you do -- do not underfund the project.  This only delays full implementation and ends up costing more in the long run.