Years ago, when I was in college and working at IBM as an intern, I learned much about personal computers and how they worked. I had to...job security. There were numerous times I would be called in by the executives in the building to come to their offices and fix their computers. The PC was still a fairly new machine and for a corporate culture that was built and relied on mainframes, learning the world of the PC was a shift for many long-time employees.
Nevertheless, I learned quickly that the first and often the best fix for the desktop computers was to simply turn off the machine, wait about thirty seconds, and turn it back on. The rebooting of the computer often reset the software and memory to a point that speed was regained and work could continue.
Computers have changed dramatically over the years, with the advent of smaller, more powerful microchips and, of course the move toward mobility with smart phones and tablets. However, even now, and maybe especially now, the simple rebooting of the machine is often needed.
On a Mac or Windows-based PC, the ability to "multi-task" by having multiple programs running at once is both a great help and at times, a great hindrance. Sometimes the computer (or phone) will slow down and cause the user great distress. Often this is remedied by closing programs that are open and running in the background. For the iPhone, it's a simple double-click of the button and a swipe of the app. It's simple, but does wonders.
It is my assertion that the local church can become much like these computers and phones at times. We, too, have many programs running. The larger the church, the more programs. I am not saying that there is anything wrong with these various programs, but over time, churches have shown a tendency to do more because it's the "right thing to do" but fail to increase resources to keep the work at a high level and productive. In computer terms, we are running more programs but have not added any memory, or maybe storage space, to the machine.
And we become bogged down.
We are considering this reality here at our church, and it is illustrated clearly when I look at our planning calendar and see markings and events on just about every day of the year. Some program is doing something, somewhere, in the name of the church (or at least using the resources of the church.)
I think it's time for a reboot.
It's almost impossible to truly reboot a local church, especially one that has property and has been in existence for decades. To turn everything off for a season will cause great distress. However, maybe distress is what is needed?
Ministry programs are good, but as the old saying goes "sometimes good is the enemy of best" and as many church leaders know, despite our best efforts, "sacred cows" tend to appear over time.
One pastor stated at a conference that "Sacred cows make the best hamburger." He elicited a laugh from the crowd, but most pastors just wondered how this could ever happen.
Summer is a good time to reboot.
For our church, the school calendar pretty much runs the family calendars of our community. Therefore, the eight weeks or so of summer become a down-time for many families (or a short-time in which to cram any vacations or get-aways.)
While we still have the typical summer events on the calendar (VBS, camps, mission trips, etc.) we are cancelling our mid-week gatherings on Wednesday evenings. Some are shocked because in the Baptist world, Wednesday is like "Sabbath, Jr." but truth-be-told, over the past three years, the attendance on Wednesdays has been so low, the people basically voted to not come, by...not coming.
If I could, I would probably cancel everything except Sunday morning worship this summer. It would be risky because our church culture is so set, but I know a reboot is needed.
What happens when you reboot?
For a computer, programs and memory gets reset. For the church, leadership should take the time set aside during the reboot to evaluate every program and ministry offered by the church. It is during this time that "sacred cows" can be put out to pasture. It is at this time the hard questions such as "Should we even be doing this?" should be asked and then when the church is turned back on...some of the programs don't reappear. In other words, some programs need to be uninstalled.
Most pastors I know would love to do something like this, but find each week to be jam-packed with meetings, study time, visitation, etc. and the needed evaluation and restart never happens. We're just too busy. That's the problem with a continually running machine. You are always working to keep the machine running.
- Finances may suffer. Here's a practical reality, if you reboot some programming, giving may suffer. Just because your church isn't meeting on a certain day (or days) does not mean the expenses cease. In a consumer-based culture where people pay for their luxuries and activities, the unfortunate reality is that some feel as if they're "paying for their spiritual fix" weekly. Therefore, the risk of losing offerings is very real. However, this should not drive the decision. Just be aware.
- A good idea vs. a God idea. Far too many of us pastors read about what some other church has done and then attempt to do the very same thing. While what was done at another local church may have been God's perfect plan for them, it may not be for you. Therefore, rebooting your church over the summer or some other time may just be a "good idea" and not "God's idea" so tread lightly and pray fervently.
- The congregation doesn't "get it." Just because something makes perfect sense to you as a pastor and leader, the fact is that most in the congregation are not privy to the inner workings of the organization and would not automatically understand. So, communicate clearly and do so over and over again, BEFORE pulling the plug.
Does your church need a reboot? Perhaps. If you're on the verge of personal burnout, there's a good chance the church is as well. So goes the shepherd, so go the sheep. Giving permission for people to slow down is not a bad thing.
Even if you stop doing some church events, remember that the Great Commission and Great Commandment never get put on "pause." The church is not the building (we keep saying that even though we don't act like we believe it) so this may force leadership to truly equip the saints for the work of the church, in their families, communities, workplaces and even on vacation.
Oh, one final warning. Sometimes when I would reboot a computer, it would not come back on correctly. That was an indication that a more serious issue needed to be addressed. Is it possible to reboot a church and find some things not coming back online? I believe so. In these cases, church health is the issue and when you recognize a real problem, you're better positioned to deal with it.
Okay. I'm logging off now. I think I need a personal reboot.