rising above passive aggressive

My last post talked about applying the rules of improv to how we  behave as technical artists in the church.  Since then, I have thought more about the idea of cynicism and negative responses.

Purgatorio

It is so easy to get cynical and negative, as the things that I care about are undermined or disregarded or misunderstood.  As an unusual bunch, it can be easy for us technical artists to feel these things; to become disillusioned with where we are and what is happening.  It can really easy to let the cynicism get the better of us and drive us to become bitter people.  Here are a couple of my own observations as it pertains to doing production in the local church.

God doesn’t call us to be negative and cynical.  I believe it is OK for us to be disappointed in how things go, or wish that the process were better, but to live in a passive aggressive state because you are misunderstood or that nobody cares doesn’t help anyone, especially you.  If you are frustrated with the process, channel that frustration into positive action:  what am I doing that is making the process difficult?  What is something I have control over that we can change to make the process more smooth?  How can I communicate differently so that the production perspective is better understood?

Being passive aggressive is not the abundant life.  In John 10:10, Jesus says: “The thief comes only to steal and kill and destroy; I have come that they may have life, and have it to the full.”  Satan has a field day with church tech people when we give into our cynicism.  Christ didn’t come so that we could wallow in that type of living.  He came so that we could have an abundant life that is way better than whatever version of “tech person cynic” you are living.

You are not a part of the body of Christ so you can complain all the time.  As tech people, we look at the world from a different perspective, which is necessary for the church to function properly.  However, always complaining about how leadership doesn’t understand, or how undervalued production is, or complaining to your volunteer teams that the pastor’s last minute graphics are stupid and evil, isn’t what God designed our role to look like.  If things aren’t right, do something about them, don’t just sit in the back of the room and throw stones.  If you have given it some effort and things haven’t changed, perhaps you should move on.

How are you letting cynicism get the better of you?  How can you channel your frustration into positive momentum instead of letting it drive you to being passive and aggressive?

 

Creative Commons License photo credit: Wetsun

what we can learn from tina fey

I was talking with a co-worker  yesterday, and I was reflecting on how easy it is to be negative about what’s going on in my church.  Negative about leadership decisions.  Negative about direction.  Negative about people.  As a tech person, I think it is easy to be less than positive because things are always changing, or things are last minute, or I’m reacting  in fire drill fashion quite a bit.  It is easy to get cynical.

Tina Fey

Many tech people I talk to call it being a realist.  That may be true, since we tend to look at things from a “how can this be accomplished” perspective.  However, in my earlier years, and sometimes even now, I would lead with “this can’t be done”, or “this is stupid” or “I don’t have time for your creative ideas”.

A different co-worker, later on the same day was talking about Tina Fey’s book “Bossy Pants” and her rules of improv and how they apply to everyday life.  I like them because they speak toward a more positive way handle situations that could really help us tech people, not just in how we approach life, but how we are then perceived by others.

 Start with Yes. –  So often the answer to someone’s idea can be no, simply because there aren’t enough resources of money or time to pull it off.  This shuts things down pretty quick and then forces the person with the idea to come up with something else.

Say yes, and… – If we are able to say yes, then offer a few solutions to pulling off the idea, often times a new, creative and more importantly, a doable idea comes to the surface.

Make statements, don’t ask questions all the time – If we are good tech people, our job is to ask questions to get to the root of what needs to happen.  However, working with non-tech people means that we need help them understand what can and can’t be done, not just assume they know that an idea is crazy difficult.

 There are no mistakes, only opportunities – This sounds pretty cliche, but I really believe that for us to improve and get better as tech people, we need to push ourselves.  This means mistakes will happen.  What we do with the mistakes is what matters.  Will you repeat the same mistakes over and over or will you make adjustments to make sure you learn from mistakes.

How can you apply them to situations you face every day?  How could the rules of improv help how you work with others?  

 

Creative Commons License photo credit: Gage Skidmore

going beyond technical support

We have been having some great conversations on our team about the role of production at our church and it has reminded me of a conversation I had over 10 years ago…probably more like 15, where we were talking about how the technical artist fits into what our church is doing.

Backstage

In a meeting all those years ago, I had been suggesting that the role of production was to support the ministry happening on the stage.  Someone else in the meeting disagreed in the extreme, saying that it wasn’t a big enough vision.  He argued that we were fellow artists with the people on stage and that we were all working together to create something that would minister to people.  After a lot of back and forth, I tend to agree with the former.

All that said, the foundation of what we do as technical artists involves technical support.  Turning mics on, lights aimed right, graphics correct.  All these things are fully supporting what is happening on stage and without good, solid technical support happening, the idea of being fellow artists, blah, blah, blah, is a joke.

However, if that is all I am called to do, that rings a little empty to me.  Is my life just about making sure a camera is color balanced correctly?  For me, I need to be a part of the creating.  I don’t need to be around for the blank page type of creating, but share your idea with me and let’s figure out how technology can help me it the best possible version.

The Willlow Production mission statement reads like this:

to create life changing moments through the fusion of the technical and performing arts.

I want my team to take what they know and what they are gifted to do and combine it with the ideas of the people designing the service to create something no one could have imagined.  There is so much potential in this idea, and unfortunately is not a common occurrence in church, yours and mine, or even outside of church.

So how do we get there?  Here are a few ideas:

Do the support thing with extreme amounts of excellence.  Be trusted to not distract from what is being done on stage.  This is a key component to moving past simply supporting a service.

Put yourself out there and make suggestions on how technology could help to enhance an element or service.  Hold your ideas loosely and be patient.

Don’t enhance something in a vacuum.  Make sure your ideas match the intent of the service.  Many times we can enhance something into unrecognizability (not a real word).  The technical arts by themselves can be distracting, unless they are fused together with the creative element.

How can you move you and your team from simply supporting an event, to making the service far better by bringing the best of your art form to the table?

 


Creative Commons License
 photo credit: okalkavan

the tragedy of the commons

Chicago bus tour traffic jam (edge)-0626.jpg

I only remember one thing from my Psych class in college.  It is this concept called the tragedy of the commons.
It basically speaks to a herd mentality that happens when I assume that my little contribution won’t matter; that I look out for my own self interests at the expense of the whole.  An example would be, I don’t take public transportation because it is kind of a hassle and the exhaust from my one car can’t really make that much difference, so I’ll keep driving myself.

I have been in a couple of all day meetings this week and it has gotten me thinking about how this concept applies in our churches, our volunteers, our staff teams, etc.  During a few lulls in these meetings, I was reflecting on what my own team would look like if we had the interests of the church above our own; if the production team’s interests where those of the church’s.

Instead, what can tend to happen is that everyone is scratching for their own ministry’s interests, looking out for what’s best for them, some times to the determent of the whole church.  Whether this is in the budget process or decisions being made about an event based on what’s best for production, the tragedy of the commons probably happens more often in our churches that I feel comfortable admitting.

I’m not saying that I have needs and concerns and that what matters to the production team isn’t important.  What I am saying is that it is easy to put my own team’s interests above the interests of my church, which in the long run will be destructive.  In the past I have seen less than ideal decisions being made for the sake of what’s easiest for production.  I hear about them happening at your church too.

I know that God will work in your church and my church when and if he wants to.  But how much more if it is full of people and ministries that are working together, towards a common cause and a common goal.  We need to stop thinking only about what matters to us as the most important thing out there and focus on what’s best for our church.

I realize that I have butchered the idea of the tragedy of the commons, but at the foundation of what we are about as production people, let’s not just be looking out for our own interests first, but our interests in light of what the whole church needs.

 

Creative Commons License photo credit: Ruth Flickr

one thing i learned from the global leadership summit

I have the privilege to work closely with some amazing speakers during the Willow Creek Global Leadership Summit.

For those of you who don’t know me, I am an introvert and a type 9 on the Enneagram scale.  These things combined, make it a challenge to work up the extrovert in me to engage with people I don’t know that well.

Usually this extroverted job involves me introducing myself, talking them through the schedule, walking them on stage, pointing out where the cameras are, what kind of podium do they want, doing  a mic check, etc.  Not only am I trying to get useful production information from them, but I tend to think of my job as being a calming influence for the people who will be on our stage.  For some of them, this will be the largest audience that they have ever spoken to, and they can tend to be a little nervous.  For others, it is just nice to have a normal conversation with someone, about nothing in particular.

It seems like after every year I do this, I receive quite a few “thank yous” from the people I have had the chance to work with.  It is always nice to be thanked, especially in as a church technical artist, since we can normally only hear about things when they go wrong.  But I also usually come away from this experience completely energized.  You would think that after a string of 15 hours days I would be wiped out, but I’m not.

So all this set up leads to the thing I learned this year:

do what I do best so that others can concentrate on what they do best.

So much of what we do as technical artists is about setting the stage for others to do something, whether it is play music, singing, acting, or delivering a message.  As my friend Marty O’Connor used to say (and maybe he still says it), we need to “set the table”.  In other words, we get everything ready so they don’t have to worry about any of it.

It is all set up, checked and working when the band walks in.  When someone talks, the mic is on, building trust that the mic will in fact be on each time.  When the pastor calls for a graphic, it is there.  These are all examples of taking care of the things we care about, so that the person using the technology can just focus on what they do best.

Think of the things you stress about for a service.  

Now imagine what your senior pastor is stressing about for a service. 

Do you think they should have any space to add your worries to their brain on game day?  

Take the things you are responsible for and kill it every week.  Set your pastor up to win by giving them a reason not to worry about what you are responsible for, allowing them to focus on what they do best.

last minute additions

When I younger (which is longer ago than I care to admit), I used to feel like the victim in the following scenario:  work out the details in the production meeting; work the plan like crazy; show up on Sunday morning with someone changing the plan; starting rehearsal late; getting slammed in debrief later in the week because rehearsal started late…again.

There was a season where it seemed like the music guy were adding additional instruments on Sunday morning without warning.  As I talked about in my previous post, when you only have 1 hour to do set up, then when you only have 24 channels to work with, there isn’t a whole lot of wiggle room to just start adding things at the last minute.

I am ashamed to admit that I didn’t handle this season of life very well.  I felt misunderstood, undervalued and walked all over and played the part of passive aggressive TD very well.  Now that I am old(er), I have learned a few things about handling the extra thing added at the last minute.

In my mind there are three possible scenarios when something gets added at the last minue:

Not enough inputs – With only 24 channels to work with, it was often full.  When the extra vocalist was added, I would generally freak out about what to do.  Now, I have learned to put the responsibility back on the person who hasn’t planned well.  Something like:  “I can’t wait to add this vocalist!  I’m going to need your help deciding what to take away from the mix.”  As an audio engineer, it isn’t easy to give up those drum channels, but we need to include the music director in the conversation, so that hopefully she will start knowing these things sooner.  This kind of inclusion helps to build trust, which we all know is key to the whole thing working in the first place.

Not enough time – Having a plan altered by a last minute addition can start the dominoes falling:  sound check starting late, rehearsal getting behind, doors open late, service doesn’t start on time.  In this situation, I learned to let the person know that we can add the congas to the band, but it is going to take about 10 extra minutes.  This puts the decision of starting late on the person who has changed the plan.  This was huge for me, because now we could point to a conversation where we decided to start sound check late instead of me just trying to make it happen then being blamed for the late start.

No problem – This was my favorite option.  We have channels available and we have time to spare, let’s do it!  Unfortunately, I used to be so beaten down by the other two situations, that I would withhold this option on principle.  They should have known before now that they were going to add something, and we are past the deadline I gave them.  This is one of those reasons why tech people get a bad name for being difficult to work with.  Please, don’t do this.  There are plenty of reasons to say no to a last minute add, and this is not one of them.

Last minute stuff happens all the time and it won’t stop.  

How do you handle these situations?  

How could you handle them more truthfully and responsibly?  

Help lead through each situation instead of being victimized by them.

 

photo credit:  by Great Beyond

defining normal

load out stage left

After the previous post about my identity being defined by what I do, I have been thinking about how to practically define what it means to be overworked.  One of the keys to me is to know what a normal amount of work should look like.  Without a good idea of what I can realistically accomplish, it is difficult to nail down what overworked really looks like.

When I was just starting out being a  full time TD, we met in a high school auditorium and had to load in all the gear to make church happen.  Starting with an empty stage, we had 1 hour to unload our 48′ trailer and set up the band and any other staging elements before sound check and rehearsal needed to start.  In those early days, starting sound check on time was a rare occurrence.  Much of this came down to me saying yes to more set up than was possible, simply because I didn’t exactly know how much I could get done in 1 hour.  Don’ t get me wrong, the music director would often add instruments at the last minute, but that’s a different blog post.

What I decided to do was start measuring how long it took to do certain tasks and to figure out what could actually be accomplished in 1 hour with my normal volunteer crew size.  Defining normal became a huge win for me, when I could talk in practical terms about what could be done and what couldn’t in the hour we had.  It was also a huge win for my boss, who was already slightly in the dark about what it took to do production, but now had tangible, measurable examples of how his ideas translated into reality.

Once we got into the rhythm of what normal looked like, we were able to start sighting the abnormal, which became a trigger for either finding ways to get more time at the school for set up, bulk up the volunteer crew for that week, or shrink the idea to fit into a 1 hour set up.

This idea of “normal” also helps with figuring out what you can accomplish in a normal work week, so that you can have a life outside of work.  If a normal week is 45-50 hours, what can be accomplished in that amount of time and what falls outside of that?  A co-worker of mine has done a great job of saying, “We are going to start at 2:30, and whatever we can get done in the afternoon, is what we can accomplish.”  If he didn’t do this, he would start pushing his normal week into 60+ hours.

For many of us, a good idea is difficult to put boundaries on, especially if it will feed our sense of identity.

Is your current “normal” too much?  What can you do today to help define what “normal” is or should be?

 

Creative Commons License photo credit: bijoubaby