Scaling Down IT Solutions for Small Ministries

by   |   mreem@bju.edu   |  

People in the technology field are often called upon to give advice to their churches and Christian schools. They are asked about the best way to provide decent technology resources to ministers and students. Unfortunately, many advisors will confidently suggest IT solutions that work well for them in large corporate settings but are, frankly, overkill for small organizations. Worse yet, many churches and Christian schools cannot afford even the modest solutions. The advisor or committee should consider ways to scale down to fit the organization.

Here are some guidelines to keep in mind during the process of advising a small entity:

  • Solve the problem

Too often many of us fall in love with a certain product or technology. We tend to carry that technological hammer around, looking for a nail to drive flat. This results in too many nails that are bent over.

  • Scale the problem

For a church with five desktop computers, the problem may be thorny, but it won’t be large. Often consumer-based equipment will work just fine for the need.

  • Simplify the problem

After cost, simplicity is probably the most important requirement. Most church employees are not technically proficient, nor can they afford training. If they cannot learn how to operate the solution, you do not have a solution.

  • Validate the solution

After suggesting an approach to the problem, be willing to assist or even implement the solution. Then stay around long enough to make sure the problem is indeed solved. Church offices are littered with the debris of previous attempts to solve the problem.

  • Support the solution

If you are willing to provide advice to your church or Christian school, then you must be willing to be available to assist when things invariably go wrong. Because problems arise when the solution is not complete. You didn’t think of something. The user did something you did not anticipate.

Readers are sometimes annoyed because problem-solving tracts instruct them on what they need to accomplish, but not how. So, if you are still reading at this point, we will provide an example of how some of these things work.

Examples of Scaling Down

Let’s go back to the small church with five computers. The local cable company has provided internet service along with a wireless connection for the computers in the office. Let’s say the pastor’s computer died. Along with it went all his sermon files and next Sunday’s bulletin. The advisor will be tasked with recovering the files (if possible) as the first order of business. This is followed up by a demand that you do something to make sure nothing like that ever happens again.

So, the problem is easy to recognize. The pastor needs some way to have a backup copy of his files so that he isn’t in trouble the next time something happens (which it surely will). Remember, the solution must be cost-effective, simple and solve the problem.

Option 1

The first option would be to suggest something like Carbonite, which is an internet-based backup solution. For about $25 per month, each of the office computers will automatically copy any new files out to a secure location on the internet. If the pastor trashes his computer, you may be called in to help recover his files, but they will be easy to find.

Let’s assume there is not enough money to pay $25 for data storage. (Believe it or not, that is often a problem.) The simplest solution is to pay for a year of service out of your own pocket. It’s cheaper than most people pay for a month of cable.

Option 2

If that doesn’t work for some reason, or perhaps the church doesn’t have an internet connection, then purchase a couple of USB disk drives. Come to church early each Sunday morning and copy the critical files from each computer to the disk drive. Then store the disk at your house.

Why two drives? You make two copies, either at the same time or on alternate weeks. Store one at the church and the other at your house.

Why? Just when you badly need those files, the drive might fail. Or if the church burns down, you still have one copy of the information. Having two copies in two different locations is like wearing a belt and suspenders, both. It helps avoid public embarrassment.

So, in bringing assistance to the technology issues in your church, first solve the problem, then scale the problem down, simplify, and keep the costs under control. This kind of focus will be of great benefit to your church and to the ministry of God.

Share:

Tagged:

Marvin Reem is the chief information officer and is responsible for Information Technologies at BJU.