Technicians are a different breed. Many are introverts who are content to stay in the back room pushing buttons and not talking to anyone. Many church techs have told me that despite trying, they have never personally led anyone to Christ — and it bothers them.
God created us to worship Him, and we are doing so through our technical talents. But why didn’t He create us to be platform speakers or missionaries who boldly go and teach the gospel around the world? After all, God gave us the Great Commission: “Go into all the world and preach the gospel to every creature” (Mark 16:15).
Believing they are missing out on fulfilling that commission can cause tech people to crawl into a shell and feel like they are just “doers,” a service department whose technicians simply do what they’re told.
I have visited a fair number of churches that not only miss the calling of a tech but also reinforce a tech’s naturally negative suspicion that he is just there to “do things.”
1. Get acquainted with other teams.
Make sure the tech team knows what the other teams are doing and appreciates the contributions of their team members.
Do this by encouraging one-on-one engagement. Having prayer time together and a few minutes of interaction before rehearsal are positive ways to know what members of the worship, facility, and other teams are going through.
If possible, get the worship and production teams together for outings that build relational bridges.
2. Provide a path so your team members can propose ideas.
Don’t kill the ideas that your tech team proposes; instead, encourage the team and have a process for vetting ideas.
Make sure the box that the team operates in is clearly defined but leaves enough room for creativity and freedom to make the work of the technician an art, not a job.
3. Refocus the team.
Use a system to review what all the ministry teams are doing, and provide praise or correction as needed.
Also, hold a brief meeting for the teams right before the service where you can provide a breather, offer a quick prayer for the service, and refocus the teams on the real reason why they do tech.
