One of the topics that permeated both the Spring and Fall CITRT (Church IT RoundTable) events was whether Information Technology in the church is a ministry. For some, the answer to that was simply yes, while many seemed unsure, and a few others said no.
As I typed this post, I was sitting in a Q&A session with my boss, Clif Guy, and his boss, Brent Messick. Brent is the executive director over operations, one of two executive directors at Resurrection. We were there with a group of interested guests, who were visiting in connection with Leadership Institute, a leadership event Resurrection holds annually. Without my prompting, this topic came up! Brent mentioned that some people have asked if he considers operations a ministry. Brent restated his answer to us, “It is a ministry. Absolutely. I say that unabashedly!” He marked some obvious points of contact such as guest services or finance.
Here’s how I’ve thought about it. If work roles that support ministry are inherently ministry, such as information technology roles, then where does ministry stop? Are the vendors who sell us equipment and supplies performing ministry? Without vendors we couldn’t perform ministries the same way right? Banks. Are banks performing ministry when they assist finance to get invoices and salaries paid? Is supporting ministry inherently ministry too? Or is work a ministry only when it directly impacts the lives of people, such as discipleship and service? It seems to come down to the interpretation of ministry and where you draw the line.
I just got off the phone with a staff member who told me about her experience buying a new laptop. She said that she and her husband were looking at a PC, but everyone has told her that she won’t like Vista -including the sales people she talked to. She said, “Why would I buy something if you’re telling me that I’m not going to like it?” The sales person said, “Well, we have Apple laptops.”