This week has been pretty interesting.  Much of it comes from recovering from Easter.  We are a little outside of our normal routine, especially with a hefty load out, and we are working hard to make sure members of the team can have some recovery time.  Vacation or an extra day off, whatever.

As a result, we hit this weekend with lots of little things undone, making it unpleasant for several volunteers.  We started analyzing what went wrong and how we could have prevented them from happening.  This is a useful exercise, but I think there is a better way to look at this.  Instead of beating ourselves up for what we should have done differently, we should be looking forward to how to prevent something similar from happening again.

A process problem

Some of what we experienced this week, was a result of process:  an inconsistent process, a less than thorough process, a letting slip of parts of the process that matter.

It is really easy to complain about how the process doesn’t work; in fact I think it is a favorite of most technical artists.  The trick is what to do about fixing it for next time.  Whether it is in your job description or not, if the current process affects you and your team negatively, how can you contribute to making it what you and your volunteers need?

A knowledge problem

Sometimes things happen that we didn’t plan on, and they aren’t a result of a bad process, but just simply a lack of knowledge.  When I first got involved doing production stuff in the local church full time, there was a stretch of time (maybe 6 months) that something went wrong each week, making us start rehearsal late.  At a certain point, the music director at my church was like:  “what the heck!”  The interesting thing about this particular run of problems, was that each one was different.  I would learn some new thing, fix it, then the next week something completely different would break.

I learned 2 things here.  One is to over-communicate when things are not going well.  If something is broken, tell your worship pastor what’s going on.  Having them be in the dark is never a good thing.  In my example, from the music director’s perspective, the same problem was happening every week:  rehearsal was starting late.  From my perspective, a completely new problem would happen each week.  I just needed to let him know that we had fixed a particular problem, and that a new, unforeseen problem was cropping up the this week.

A knowledge problem leads to a process solution

The other thing I learned was that with each new knowledge problem I tackled, I needed a new process to make sure it didn’t happen again.

In another example with the same music director, I had taken a vacation and had lined up my best volunteers to make the weekends happen.  We were meeting in a high school and had 3 semi trailers full of gear to haul over to the school and unload each week.  One of our cases would come off the trailer each week to be loaded up with things from our offices and then on Saturday would be put on the trailer to go to the school.  On one of these weeks that I was gone, a case that never came off the trailer was taken out and left in the offices.  As a result, some key equipment wasn’t available for set up, making rehearsal start late, my music director’s favorite thing.

When I got back from vacation, he lit into me about how could I let something like that happen, and who was to blame and I can never take another vacation over a weekend again.

It dawned on me:  how can I plan for something that has never happened before?  The answer I came up with is that you can’t plan for something that has never happened.  There was no point in wondering how I could have prevented it from happening the first time, since I didn’t even know it could happen.  The trick was figuring out how it wouldn’t happen again.

When something happens that you didn’t plan on, it is either a process problem or a knowledge problem that needs to lead to a process change.

The next time something you didn’t plan for happens, don’t dwell on what you should have done different, use your energy to figure out what to do differently next time.

Back in the summer of 1940, Britain was getting severely bombed.  As a way to keep people moving forward with their lives amid the ruin of their surroundings, the British government developed a series of posters to put around London to help solidify the resolve of the British people to face each day.

Many of us are familiar with one of these posters, which Has taken over most gift shops on coffee mugs, key chains and iPhone covers:  Keep Calm and Carry On.  Interestingly, this particular poster was never put up.  It was saved for when Britain was invaded, which never happened.

One of the posters that was used extensively was this:

Your Courage, Your Cheerfulness, Your Resolution Will Bring Us Victory.

There is so much about this particular poster that I love.  Not just thinking about it in terms of the Battle of Britain, but about how it can apply to my own life.

I don’t often go around wondering how I am going to achieve victory, but if I think about it in terms of effectiveness, for myself or the team that I am working on, this makes great sense.

Going to work in the world of the technical arts in the local church and applying personal courage, cheerfulness and resolution to what I do every day, definitely point things in a direction of being more effective.

Courage:  To not be afraid of who I am or the opinions I have and to have courage enough to act on them (in appropriate ways, of course), will make the team I am on much better.  For the body of Christ to function properly, we all need to have the courage to be our fullest version of ourselves.

Cheerfulness:  Production people are known for being grumpy.  What if I showed up to work with a great attitude each day?  What if I didn’t immediately shoot down someone’s idea, but took a minute to engage with what is right with it?  To not always look at what is wrong, but to see what is right.  How could your team look different if people showed up (yourself included) with cheerfulness?

Resolution:  No, we are talking about 720 vs. 1080.  As a technical artist, this is more about fighting for the things that you were designed to care about.  Will you do the necessary work to make your services the best they can be?  Even when a relationship is strained will you push through for the sake of the whole team?

While we are fighting every day for victory per se, my courage, my cheerfulness and my resolution will all contribute to my team being the best it can possibly be.

Some rights reserved by drbexl

Here’s a quick encouragement from a leader of my church, that I think can apply to all of you who are killing it this weekend:

You guys have a heavy lift and make it look easy to the rest of us who get to simply enjoy it. What you guys do contributes so critically to how people experience church and therefore often how they experience God. Big responsibility, and thank you for stewarding it so well!

That feeling of tired means that you are making the powerful message of the Gospel available to countless people who need it.

Way to go.

I was at a rehearsal for Easter the other night, and noticed that there was a meeting happening in a room near by.  Without staring through the window in the door, I could tell that it was our Elder board meeting.  Throughout the night, I kept passing this room and they were still in there, meeting.

Not unlike the volunteers in produciton, here are a group of people that are volunteering their time and are staying late and missing time with their families. Yet I was struck by the intensity of this kind of volunteering,  to help guide and direct our church, as well as the time and mental commitment it requires of the people who take on this task.

I am pretty sure that I have never thanked any of our elders for what they do.  If I think I’m behind the scenes, this group is probably even more so.  And different from volunteering in production, where you are changing batteries in the wireless mics, these people are responsible for the spiritual health of our congregation.  Whoa!

Many times, the nitty gritty parts of leadership are thankless.

When was the last time you thanked someone in leadership at your church?

During the run up to Easter, take a few minutes to thank someone in leadership for all they do.

Some rights reserved by woodleywonderworks

The cobbler praises God every time he makes a decent pair of shoes.

I read this quote a few weeks ago.  It is attributed to Martin Luther…you know, the guy who helped kickstart the reformation.  Using the interweb, I went looking to see if he actually said this, and I only found anecdotal evidence.  Instead of spending any more time looking, it seemed like it was time to just write what I was thinking about it, since it is a great idea, whether or not Martin Luther said it or not.

As a technical artist in the local church, it is real easy to lose sight of the fact that what I do matters.  And it doesn’t just matter from the standpoint of executing a service flawlessly, or helping to create an environment where people can experience God.

The reality of Herr Luther’s statement is that doing what God created me to do and doing it well, is an act of worship.  My personal act of worship.  Martin Luther talked about a guy making shoes.  I’m talking about those of us behind the sound board, or backstage, or editing videos.

God doesn’t create all of us to be on stage leading people in worship, or teaching God’s word for our congregations.  Most of you who read this blog are behind the scenes.  For most of us, it is easy to assume that we do all this work for the sake of other people, so they won’t be distracted and can worship freely.

While true, it is just a shadow of the truth.  So many times, technical artists that I talk to end up worshipping excellence or the perfect mix; the goal of their art form is the art or the technology itself.  There is so much more to what we are doing.

God created us as technical artists to worship him.  By practicing our art with excellence, by creating the perfect mix, when editing the next video we were designed for  worshiping God.

What motivates you?  Is it the technology?  Is it facilitating worship for others?  Is it using how God has made you to return worship to him?

In part one of this post, I talked about making sure you know what you are trying to do in your services and how volume fits into that.  This is a leadership question, more than a dB question.  As a church, what is your goal for the service?  How loud it gets will be a part of that answer.

In this post we are going to take a look at a different aspect of the “perfect volume”:  the appropriate volume at the appropriate time.

In your service and in mine, there are moments that need to be loud, and there are moments that need to be quiet.  Here are a few examples from my current experience:

Beginning of the service

When people first walk in, we tend to want to grab them with a high energy song; something that people can really engage with.  The trick with this is high energy tends to mean high volume.  It is difficult to take people from the volume levels of lobby noise, right to 95dB without a clutch.  So, even though the band might be killing a high energy song on the stage, we try to ease into it, so that we don’t blow people’s heads off.  By the end of the first song, we are usually up to a volume that matches the energy of what’s happening on stage.

Quiet moment

Years ago, we hosted the band Delirious? at Willow Creek.  One of the things I really marveled at was how loud it was at times, but then how quiet is was at times.  They were really good at building a set with great dynamic range, having a quieter song at just the right moment.  It gave everyone’s ears a nice rest.

If you are mixing audio at your church, it is really important to let these quiet moments get quiet.  If the level of the kick drum is the same on a quieter song as on a upbeat song, you aren’t doing the moment justice.  In our auditorium, it is really difficult to make the space feel intimate, but by bringing the volume down for a quieter song, actually helps to draw people into the intimacy of the moment.

Many times the people on stage need help striping down arrangements to make them more simple for these types of songs.  As the person out in the room trying to create something small and intimate, you can assist the band by suggesting potential ways to make things simpler and less busy.

In the case of the quiet moment, just giving ourselves a maximum, not to exceed dB level, doesn’t really address the need for us to make quiet moments, as quiet as they need to be.

Loud moment

I was once asked to mix FOH at a Willow Conference in Germany.  This is a story in itself, but one thing I remembered is that the closing speaker had people whipped up into a frenzy, trying to get them as loud as possible.  Someone in the booth grabbed the Radio Shack dB meter we had brought from the states, and turned it on.  The crowd was at 103db, A weight, slow.

From there, the worship team was going to lead us in one last song.  This was one of the few times that I couldn’t get the PA loud enough.  We struggled to get the band and vocals heard above the volume of the audience.  When it was all said and done, I think we hit 110dB.

I would never say that we should be shooting for our loud moments in the service to be at 110dB, but the point is that for us to match the moment of what is happening in our service, sometimes we need it to get loud.

In this example, having a maximum ceiling on our dB levels, doesn’t take into account a situation that requires that it be louder.

Mixing is an art form.

The “perfect volume” is something that changes with each nuance of the music and the changes happening throughout the service.  To put all the responsibility for “how loud it is” on a dB meter is too simplistic and the wrong way to go about determining the audio levels in your services.

Some rights reserved by superUbO

I get a lot of questions about how loud we run our services at Willow Creek.  I always find it difficult to give a standard answer.  Much of that comes from the fact that I think in terms of grey, as opposed to black and white.  Each situation is different, so I tend to give the answer, “It depends”.

Audio volume is so subjective and dependent on so many factors.  Saying that there is a perfect volume level, or a maximum not to exceed, is ridiculous to me.  What isn’t ridiculous to me is the reality that not many people are willing to do the difficult work to figure out what is the right volume for your church.

Know what you are trying to do.

At every church, in every environment, it is important to know what you are trying to accomplish.  It is important to know this before you get going, so that we all know what a successful volume actually is.  Are you trying to make it like a rock concert?  A campfire sing along?  What is your service trying to accomplish?

When I was first starting out as a volunteer  audio engineer, I used to get really upset by the long line of people at the sound booth after a service to complain about it being too loud.  I remember talking to the music pastor about it, and he told me not to worry about it.  He said that if he thought it was too loud or the senior pastor thought it was too loud, then we’d have a conversation.  As far as he was concerned, it was exactly the volume it should be.

Because we had talked about it and we knew what we were trying to accomplish, I was able to be OK with the line each week, and I knew that I just needed to send them to my boss if they thought it was too loud.

The other thing this taught me was that it wasn’t necessarily my responsibility to carry the burden of how loud it should or shouldn’t be.  As the audio engineer, it was my job to interpret what the leadership of my church had decided was the proper volume based on the goals of the service.

This responsibility thing cuts both ways.  In one aspect it was nice that someone else could deal with the complainers in the congregation.  In another way, I need to mix based on the desired outcome that the leadership had determined…not necessarily on my own personal taste.

If you are a leader and a decision maker when it comes to how loud it should be, give your audio team the direction they need to succeed when it comes to volume.

If you are an audio engineer, ask your leadership to clarify what your church is trying to do with the audio mix, so that you have a better idea of where the mix should live.  Once they have helped define the desired volume, mix to that standard and not your own.

There is way more to this topic, so we’ll continue this in another post…

Some rights reserved by jmegjmeg

37signals.com, the makers of project management software Basecamp, have some pretty cool values that help determine the kind of company they want to be.  After a short break from looking at these values, we are back to check out value #7, Software should be easy:

Our products are intuitive. You’ll pick them up in seconds or minutes, not hours, days or weeks. We don’t sell you training because you don’t need it.

While production tends to not be easy, this value made me think about simple and intuitive. 

When I was the TD at Kensington, way, way back, we met in a high school auditorium.  We would have to empty our 3 semi length trailers and set up the entire church in under 2 hours…then naturally need to tear it all down at the end of the day.  As the leader of this process, and as newly graduated Industrial Engineering student, I was always thinking about more efficient ways to get this job done. 

One of my first thoughts revolved around making each task a one person job; to reduce each part of the process into a series of jobs that one person could accomplish.  There were definitely things that we needed several people to lift or to get into place, but the majority of the tasks could be done by just a single person.  What this did was keep everything very simple and doable within the time frame we had to work with.

As a technical artist, I was always finding myself fighting against this idea, simply because I wanted to try new things or expand our technical capability.  Keeping things simple enough for one person jobs was not easy, but it helped us involve the largest number of volunteers possible, and it sustained us being portable for so long.

In my current life, my boss Bill Hybels is always pushing me and my team to not make things too complicated.  He has caught onto the fact that as technical artists, we are trying to push the technology envelope, and wanting to try new ways of doing things.  However, what can sometimes happen as a result of this push for new, better ways, is that we can make something so complicated that it is bound to fail.

We have this joke between us that why would we have a person do a task, if we could figure out a way to have a computer do it?

37signals.com says their products are intuitive and are easy to use.  Does what you are doing make the most sense to the largest number of people, or is it so complex you need a PhD to figure stuff out?

In our drive for the newest technology, or “better” technology, are we losing sight of doing things most effectively?  Most simply?  Will the new way introduce new levels of risk that we don’t need to take on?  Is a new way necessary or just cool?

At the foundation, the technical arts in the local church are in place to amplify the message of God’s word.

Our use of technology should only be as complicated as the content/message requires.

Are your processes and systems so complicated that they are getting in the way of the message we are trying to support?

Some rights reserved by DBduo Photography

I have the privilege of working in Germany from time to time.  I also have the privilege of having family who lives in Germany that I get to stay with.  Along with those privileges, I get the chance to go and see things that tend to blow my mind.

I am flying back to Chicago right now, reflecting back on this latest trip, and one of the things that really struck me.

I went to the city of Mainz, where among other things, Guttenberg did his early work with the printing press and movable type.  Here was the 15th century version of a technical artist, someone who was pushing technology to make the Bible more relevant and available to more and more people.  Pretty cool.

Going to the museum, I was expecting to be impressed by the printing press itself, or the amazing manuscripts of Guttenberg that were on display.  Unexpectedly, the thing that caught my attention was Johannes’ choice of font for his printing press.  Or should I say lack of choice of font.  He had 2.  For the time, I realize that he was using cutting edge technology, but come on!  Only 2 font choices?!

When I stop and think about it, I love the simplicity of his dilemma.  So often I find myself caught up so many choices that I get distracted by them.  They either stop me from making a choice, because I can’t decide, or I end up getting buried by all the possible options and spend all my time trying one thing then the next.

I think that as technical artists in today’s church, with so many options, the way we use technology can get so overwhelming that it overshadows the message or dominates the conversation.

The thing I love about about Guttenberg’s limited options, is that it was about making the Bible available to as many people as possible.  It wasn’t about font choice.  He wasn’t trying to wow people with his creativity; he was just trying to crank out as many Bibles as possible.  This isn’t to say that he still didn’t spend some energy on some handcrafted art work, but the bottom line idea was let’s print a bunch of these so people can have them.  For some people, the hand drawn, illuminated Bible was what they wanted/needed, but Gutenberg’s idea was to use technology to print more, was for the purpose of making it accessible to more.

For me, much of technology is in place to help us reach a larger number of people.  Amplifying words and music, making graphics so that people can follow along with the scriptures, using IMAG so that more people can make “eye contact” with the teacher.

In today’s local church scenario, where the message being understood is so dependent on technology, it isn’t very far to it becoming the center of attention and take away something from the message.  In Guttenberg’s case, it could have easily been about him and his font choices, instead it was all about God’s word.

How are you using technology in your church?  Are you distracted by all the options and therefore taking away from the message?  Or are you taking the technology and using it to maximize the message?

Some rights reserved by wilhei55