Our CM programs are tired
“We’ve been operating the same programs, schedule, and curriculum for a long time. They are ‘safe,’ and ‘comfortable.’ How can we bring new life into our CM programs without disrupting our good foundation?”
The concept of “If it isn’t broken, don’t fix it” does apply to CM programming, but so does the concept of being “fresh.” A program that is “comfortable” and that has been effective for years should not be discontinued just because it is “old.” It is possible to add some “freshness” to a regular program that is still effective. It is also possible to successfully end a “tired” program in a way that doesn’t disrupt your good relationship and trust from the parents.
“Call to me and I will answer you and tell you great and unsearchable things you do not know.” Jeremiah 33:3
In ministry, we can get very comfortable with what is currently working. The children seem happy, the parents aren’t complaining, the pastor hasn’t told us to change anything, and our CM team seems to be doing just fine. Why should we change anything? There may be no real reason for making changes; but that doesn’t mean you shouldn’t consider it. Today’s society craves whatever is “new” or “updated.” Marketing professionals will encourage product makers to “improve” products periodically by updating the packaging or adjusting the products. All of us have had mixed reactions to changes throughout our lives. Maybe you remember saying, “Why did they change that? I liked it better the old way.” In CM, we face those same pressures and fears. What do we “improve,” and what do we leave the same? This challenge can only be faced with our knees bent in prayer and our eyes and ears wide open to hear and see the reactions and needs of the people. A program can be “freshened up” with a new “look” (title, signs, slogans, colors, schedule, or music), while still keeping the same purpose and curriculum. A “tired” program might need to be “freshened up,” or retired completely. For more help, click on the links below.
Visit other articles in the “Developing Programs APPENDIX“