Sometimes I wonder if the theme song for a typical church tech is “One” by the old band Three Dog Night. After all, one is a pretty lonely number, and for many of us, that’s sort of how things go, and it’s the best we think we’ll ever do.
Getting there early by myself, staying late by myself, solving problems by myself, trying to get focused, encouraged, or motivated by myself.
But that theme song should probably be more on the lines of “It Takes Two” instead: to make a dream come true (as Marvin Gaye and Kim Weston sang), or to make a thing go right and be out of sight (Rob Base).
The point is, none of us was designed to do life alone. I just wonder how many of us either wear loneliness as a badge of honor (proud of how much we can do by ourselves) or as a curse we’re doomed to live out (too much to do and nobody to help, even if I wanted them to).
In the context of church tech ministry, I think often of the passage in Ecclesiastes 4 that extols the benefits of having a partner for one’s work.
“There was a man all alone; he had neither son nor brother. There was no end to his toil ... Two are better than one ... If either of them falls down, one can help the other up. But pity anyone who falls and has no one to help them up.” (Eccl. 4:8-10 NIV)
If we set aside the idea of volunteer recruitment for a minute, how many of us are actively seeking for someone else in our lives that can help us up if we fall down?
I realize that some of us are in a difficult position internally at our ministry. There are limited options of people who can serve on our team or even that we can go to as a resource. I get it; we can’t magically make people want to help.
But if we set aside the idea of volunteer recruitment for a minute, how many of us are actively seeking for someone else in our lives that can help us up if we fall down?
When I was first starting in ministry just over 12 years ago, I was very aware of the fact that I knew very little about this particular world. However, as introverted as I was (and still am!), I knew that the only way I could be successful was to reach out to others in the field who I could ask questions and learn from.
Churches in my backyard in my own city? I made a list and tried to call or email as many as I could, just to build a personal connection.
So, I began a very intentional process that continues to this day. If I went to a conference and attended breakout labs or sessions, I tried to meet the speakers afterwards and continue a professional relationships. If there was a visiting pastor at our church, I made it a point to build relationships with their tech guys. If my pastor spoke at another church, I’d try to get to know the guys there too. Churches in my backyard in my own city? I made a list and tried to call or email as many as I could, just to build a personal connection.
Even though our ministry is large, I’m convinced that knowledge and ability as a church tech have very little to do with how big the church is. There are plenty of people at churches smaller than mine who are much smarter than I am and have much more experience in the field than I do.
There are people who have been in the business less time than me, at churches smaller than mine, who are much more well-versed at certain topics than I am, just because of the unique challenges their ministry may face.
I’m convinced that knowledge and ability as a church tech have very little to do with how big the church is.
I do my organization a disservice if I’m not actively exploring the industry to learn as much as possible about what other folks are doing. And more often than not, those folks are happy and excited to share about what it is they’re working on.
The best part, though, is when you’re able to build relationships that provide support and encouragement. Yes, it’s great to know enough people in town that I can call to borrow a projector from last-minute because one of ours died.
But it’s even better to know that there are other folks who are friends, that have your back, that you can call when you’re having a bad day, or you’re frustrated with your leadership, or you’re stressed about having to solve some new problem.
Those are the times that Solomon was speaking of when he pitied the one working all alone.
I’m so glad that I’ve been able to build a cohort of friends in this industry that I can lean on when I need it. But I know that there are many who still lack that sort of connection.
My challenge or encouragement for all in the church tech world is to take a deep breath and make the ask. Send the email, make the call, shoot the DM. Yes, it may produce anxiety and be totally out of the norm for those of us who are comfortable blending into the background. But it doesn’t change the fact that we all need folks to lean on.
My challenge or encouragement for all in the church tech world is to take a deep breath and make the ask. Send the email, make the call, shoot the DM.
And I promise that, over time, if you stick with and nurture those connections, they’ll be incredibly fruitful and beneficial. You never know when you’ll need to “phone a friend” because of what you’re going through.
Yes, there can be benefits to the crowd-sourcing model of message boards and social media forums. At some point, though, I need people in my own city, or who are a quick call or text away, that can help me when I need it.
One is the loneliest number that we’ll ever do, and it leads to a hard life. But with a brother who is born for adversity (Prov. 17:17 NIV), we can fight any battle with confidence, knowing we have someone else who has our back.