I've been having a few computer issues lately. For the most part the computer works. I can both input and retrieve information, take care of e-mail, and thankfully receive alerts concerning appointments and reminders.
Truth is, I could live with the computer just as it is. But a software issue has kept my fairly new laptop from operating at 100 percent. There was a time when I would have been satisfied with 90 percent functionality. After all, the main functions work well and that is 90 percent more capability than I had in my pre-computer days.
My software issue revolves around a needed update. Halfway through updating I receive a message that I need to quit a procedure that doesn't appear to be running. Basically, I can't enjoy the functions of the new and improved until I quit the tried and true.
Ever notice how hard it is to quit something you don't know you are doing? Or how hard it is to risk forgoing the effective and reliable for something that might prove to be even more so?
The way we conduct Vacation Bible School can be like my computer issue. VBS works - in fact, it works well. Ninety percent functionality gets the job done.
Sure, VBS could be improved, but why bother? After all, the way we conduct VBS is already effective and reliable. It's comfortable for the kids, for the workers, and most of all for the leadership.
Sometimes we have to quit something that is good in order to have the capacity and resources to do something that is even better. Sometimes we need to quit doing things we do not even realize we are doing.
For example, the way we enlist and train workers, the way we register kids, or the way we assign rooms.
Have you ever noticed how we tend to put the same grades, or the same workers, in the same rooms year after year without considering the potential size of the group. After all, if the room worked for second grade 10 years ago it should work today. Right?
I finally found the hidden culprit and was able to quit the process. Updating was a success and now my laptop is working at 100 percent!
What aspects of your VBS need updating? What processes do you need to quit in order to update VBS 2017 to the new and improved?