don’t say someone’s “no” for them, part 2

It's a No!

Yet another post about saying “no” for other people. (check out part 1 here)

This one is one is based on a stereotype of tech people everywhere: We always say “no”.

Usually we say it with attitude. Many times we don’t even hesitate; it just comes right out of us.

“Hey I have this idea to..” “NO!”

We don’t even wait for the punch line.

I think this comes from being overwhelmed by the task we already have in front of us, and from a general misunderstanding of what we actually do by the people with the ideas.

I think the reasons that we jump to “no” so quickly only perpetuate being overwhelmed and misunderstood.

With our production team that works the weekend service, we have been doing a lot of work on becoming one team with our creative team counterparts.

When we say “no” so fast, it doesn’t allow the creative team into our world. They will never understand what is going on under the surface if we never open up the conversation about why we are overwhelmed.

Contrary to what I used to think, people with awesome creative ideas tend to not to fully understand what it will take to pull it off…that’s what we are there for. I think this is the way God designed us to work together. But it only functions properly if we open the door to what is really involved.

Opening yourself up requires, well, opening yourself up. To either acceptance or rejection. Either becoming more like one team or becoming more separated.

Working production in the local church requires some relational risk taking. Without opening yourself up to the possibility, you are shutting down the very thing that will help your creative and technical arts work the way God designed it.

Take a chance. Don’t say “no” immediately. Talk about what is really going on. You might be surprised by the response.

 

 

Attribution Some rights reserved by sboneham

photo by: smlp.co.uk