Churches with well-functioning lines of communication between pastoral or worship staff and the tech team tend to not communicate only when there are problems.
If you're not already doing a post-service review, this might be a good place to start. It should involve the key leaders from all aspects of the service: teaching pastor, worship leader, and tech team leader. Discuss what went well, as well as what could have used improvement.
But also listen to the reason why something didn't go well. Pastoral and worship leaders tend to throw things into the service at the last minute, and frequently what seems like a small request is a much bigger deal than you may be aware. Be open to suggestions on how to make this work better, such as planning further ahead, or seeking input on the ramifications of making the request.
Also, communicate early. When does your tech team find out the makeup of the worship team that week? Do they get notified of what is going to be happening earlier in the week so they can set up for the correct thing when they arrive (usually first) Sunday morning? Or do they use up valuable time setting up for a band that isn't playing that week, and then have to scramble to recover?
If so, your team could become frazzled instead of mentally prepared to focus and mix well.
Technical ministries are usually far more complicated then it may appear. Techs like to be organized and prepared so they can perform the best they can in supporting the service. Would you be thrown for a loop if 30 minutes before the service started you were asked to preach on a different topic? Or if, as a member of the worship team, you were handed a list of new songs that were to be played that morning instead of the ones you practiced all week? Would you be able to do your best if either of these things happened? Likewise, keep your tech team in the loop and make them a part of the planning process for events and services.
Next time, we'll talk specifically about dealing with problems.