
“You’re not hanging on a cross.” I have a friend who says that to me any time I decide to whine or complain. She reminds me that I’m not hanging on a cross and that somebody did hang on a cross. For me.
I’ve used her exact words with other people. Life sucks sometimes. Get over it. You’re not hanging on a cross.
Earlier this week, I called a friend of mine who lives in another state. It had been way too long since our last phone conversation. She reminded me of a lesson she and her husband (an Executive Pastor) learned several years ago: there’s a difference between being called to ministry and working for a ministry.
Today was a day I was grateful for these friends. And my family.
Ministry isn’t easy.
You’ll lose sleep, cry more than you thought possible, and sacrifice times with your family. Times like nights, weekends, holidays, major holidays, birthdays, anniversaries, sporting events, and Sunday afternoons.
You’ll have minor wins – like finding a way for your church to get some free custom printed mugs.
You’ll have setbacks – like forgetting to save three hours worth of work on a major graphic design project. (Ask me how I know?)
You’ll make mistakes. And you’ll realize that there are some people who equate the church with Jesus in such a way that when the church makes a mistake they think Jesus makes mistakes.
Then you’ll lose more sleep, cry more, and find something else to sacrifice – all because Jesus is perfect. And your goal is to be more like Him.
I have a great job. I have an awesome boss. I get to be a part of helping people find and follow Jesus and I get paid to do it.
My workload is heavy right now and I’ve got stuff [still] on my to-do list from last week last month four months ago. Take my neurotic obsession with our church management software and website content and development, combine it with my goal of perfection, and the result is my current to-do list. Make that an ‘overdue’ list.
And, yet, Sunday comes.
Every. Single. Week.
And as much as I try to get ahead, I find myself printing bulletins later in the week.
So there I was today – bulletins not printed, trying to pull information and correct image sizes for some other communications assets – and I get a call. A sick kid. My cell phone rang. My daughter’s voice on the other end, “Mom…” A. Sick. Kid.
Give me credit. I didn’t cry. I didn’t scream. I didn’t throw anything. I did read Exodus 20:13.
I did email my boss.
People over process.
People. Over. Process.
We’ve been talking a lot this week about processes and what needs to change to meet the needs of a growing church.
I wrote: we need to work on changing some processes because I don’t ever – ever – want to have to choose between a sick kid and printing bulletins.
I called my husband, who fortunately had enough margin and flexibility in his schedule to work from home.
In ministry you’ll lose sleep, cry, and make sacrifices.
But you’ll also realize how blessed you are to have a family and friends.
And at the end of a difficult day week four months, you’ll be thankful that you’re not hanging on a cross, and that you’ve been called to ministry to help people know the one who already did: Jesus.






Just like you can’t do it all; you also cannot do it alone. Being the software administrator, you’re probably also in some type of leadership position at your church. While teaching others how to manage their own areas of the software and not trying to do it all, you also need other leaders around you. Here are some ways that have helped me:
As a software administrator, I found myself in a position that wouldn’t be considered ‘healthy.’ I was managing the software alone. I input events, made sure the event image matched the print and web site materials (especially if the event was linked to the public web site). I made sure all event information was communicated the same across all platforms. I also checked financials and ran financial reports for our finance team, controlled who had access to the software and at what levels. I managed our physical resources (using the software) – including rooms and other resources (tables, chairs, A/V equipment, etc. I built the check-in system for events. I built forms for registration. Almost no one else used the software, yet everyone knew it was there. Working for them.