In late 2016, Fairview started using Breeze ChMS. Breeze is easy to use and their customer service is outstanding.
In early 2017, we went with Ministry Designs for our web site. Easy to use. Great customer service.
We have a theme.
I decided I really wanted to use Breeze as a central “hub” for all church scheduling. I can list our rooms and other areas on campus, enter all event information, and display graphics. Plus I can give all Pastors, Deacons, Ministry Leaders, and Church Members access to view the calendar.
Unfortunately, my other idea to create a separate Breeze Calendar for events that would be displayed on the public calendar wasn’t so easy.
Embed codes weren’t doing what I anticipated and I couldn’t get Breeze and Ministry Designs integrated. I joked: Fairview Baptist Church, Breeze, and Ministry Designs were NOT forming a holy trinity.
Then a few weeks ago, we had integration success. I was able to directly integrate our Breeze calendar to display on our web site.
Success. Fireworks. National Holiday. Happiness.
I literally emailed our Pastors, IT Committee Chairman, and the guy who heads up the Greeters/Connections team at 10pm on a Friday night.
This was going to be great! Now, when I entered an event in the ChMS, and I published it to the public calendar, it would automatically display on the web site. No longer would I have to copy and paste information from the ChMS over to the web site and vice versa. No more chances for typos, different information on the two different sources. If the date and time was changed or updated, if the event description changed, if the location on campus changed…if anything was updated or changed in the ChMS, it automatically went to the web site.
It would also free up some time.
You see, it’s quite common in the ‘church communication world,’ to work long, often-unpaid, hours. A majority of my peers (and I) consider our jobs more of a ministry and less of a ‘job.’ We use the term ‘serve’ rather than ‘work.’ And most of us genuinely enjoy what we do. Because we know we’re serving someone greater (Jesus Christ). Our bosses are usually Pastors – sometimes our own Pastors if we’re blessed enough to also attend the church where we
work serve (who sometimes list Jesus Christ as the ‘contact person’ or ‘event coordinator’ on our communications request forms). You can laugh at that, but it’s true. The web site, social media, and ChMS are just tools we use in getting to play our small part in connecting people to a church family and to Jesus Christ.
And while I certainly don’t mind putting in an extra 10-20 hours a week in ‘service hours,’ there are weeks that it’s just not practical. I do love what I do. In many respects, it’s my hobby. Some people like knitting or horseback riding. I like working with the church management software and the web site. But sometimes, other things (and people) need my attention. I have a husband. I have four kids. I have friends. I’d like to keep all of them around for awhile and not become the crazy cat lady (except instead of cats, it would be fonts).
Plus, it can lead to burn out. Just Google ‘church Pastor burn out.’ You’ll find a lot of articles on not just Pastors, but church staff and volunteers who leave their churches often because of burn out. Nobody wants that. I like my job. I like my church. Since I know what can cause burnout, I’d like to avoid that.
So there it is. This awesome integration that is going to increase accuracy in information, possibly reduce errors, and increase productivity. This is good for the church. This is what’s best.
This sounds like I just won the Church Communications Lottery.
But wait. Take a step back. What else happens?
We’re going to have to retrain group leaders how to take attendance. We’re going to have to take a fresh look at the events page on our web site and how that’s displayed. We’re going to have to look at how small groups are listed (right now it’s publicly displayed as one single ‘Life Groups’ time on Sunday mornings; this would force us to take a look at listing each group separately/individually). [For the record, I’m a fan of listing each group separately.] But this changes what group leaders see when they log in (display). This changes ease-of-use and aesthetics.
So, I decided to pull the plug and keep doing what I’ve been doing.
Wait! What!? Why!? Why pull the plug on the possibly the best software update and integration to date?
A few reasons. I’ve already addressed. It changes ease-of-use and aesthetics. It requires (re) training people who aren’t entirely comfortable with what we have. We’ve had the software less than a year. Not everyone is using it. Not everyone is trained. Those that are, are just now comfortable with it. A few are just now understanding why we use it. It’s too soon to pull the rug out from under them and replace it with a new rug.
Next: why should they trust me? Everything I do is guided by my relationship with Christ. Every decision starts with prayer. I have a few very trusted peers at other churches who work with their ChMS and web sites. I have to use wisdom an discernment and at the end of the day, I believe that the Church is the Bride of Christ and we have to play a part of presenting her blameless and spotless. Unblemished. But – do the church members know that? Do they trust that? I’ve worked there just over a year. Have I earned enough trust to make a change?
I love software updates. I understand why software companies make them and I understand how they (usually) benefit their clients (the churches). But do the church members I serve know that? Have I successfully communicated that to them?
And while organization, administration, accuracy, streamlined productivity, and reduced possibility of burnout is important, there is something more important.
And that is earning trust, setting examples in leadership, and truly loving and caring about the people we get the privilege to serve.
My prayer for all of my church communications peers is that we can know when to look past the processes and procedures and focus on the hearts of the people and recognize our jobs as ministries.