Never Piss Off the Sound Guy

Things I Learned the Hard WayThis is the first in a series of short stories with clear morals that I keep coming back to for reminders. I call them Things I Learned the Hard Way.

When I was in college, I ran an open mic night at the campus cafe. I’d play my songs and then invite others to do the same. Some were wonderful and some were dreadful, but they were all played with heart. (And, yes, this was absolutely a proto-Fray Day.)

My friend Jed was the Sound Guy. We had two mics and four speakers, and it was his job to make sure everyone sounded good. With acoustic guitars and cheap equipment, it was no easy task.

One night, while I was warming up the crowd, a killer brrrrrrrrrwwwp of feedback flew out of the speakers, shaking the rafters. The usual etiquette was to just play on as if nothing happened, but this one was so loud, I stopped and waited for Jed to make it stop. Some knob-fiddling and mic adjustments and we were back on track.

When the song was over and I was transitioning to the open mic portion of the evening, I wanted to assure the crowd and the upcoming performers that everything was okay, so I said something like:

“Well, if Jed’s got the sound under control,” I said, “we can move on to the open mic.” My tone was meant to be a friendly jibe, but I came like a chiding from a petulant boss.

The audience fidgeted uncomfortably. I couldn’t see Jed’s face at the back of the room, but I didn’t have to. I knew I’d fucked up.

Later Jed pulled me aside and let me know he didn’t appreciate it. All I could say was, “You’re right, I’m sorry, it won’t happen again.”

I learned a valuable lesson that night: Never piss off the sound guy. He’s got the power to turn off your mic, turn off your spotlight, or create a feedback loop so loud it could induce seizures. You may have the eyes of the crowd on you, but the sound guy has all the power.

This is a lesson that’s applicable to more than just college open mics. Every time a CEO criticizes a subordinate in front of others, every programmer that mocks the designer who’s trying to make their code usable, every high mucky-muck who depends on the people below to make their promises come true … they should all remember this lesson. Often, when companies fall apart, it’s because the people at the bottom, the ones actually doing the heavy lifting, have become pissed off this way.

Never, ever, piss off the sound guy.

+

Read More Things I Learned the Hard Way »


Fray

9 Comments

Maybe a bigger way to look at it is: always assume others are doing the best they can, even when they make mistakes. If this gets spread around eventually it will find its way back to you when you inevitably make a mistake of your own.

Posted by Richard on 12 January 2009 @ 5am

The best way to learn this lesson, I think, is to be the sound guy from time to time. And then remember not to do to others what was done to you. Or, as in your case, be smart enough to realize what you’ve done (which is rarer than one would think).

Posted by Rasmus on 12 January 2009 @ 10am

Thanks Derek,

I’ve been trying to tell people to never piss of the sound guy for years. A rapper by the name of John Ruben has a song called “soundman” and one of the lines is “never make the sound man your enemy”

Thanks for this blog!
Brandon

Posted by BandonRandon on 13 January 2009 @ 12am

Perhaps another way to explain this would be to say: What goes around comes around, so don’t be a prick.

Many years ago I remember a guy who was quite bright but also arrogant. He seemed to delight in not-so-subtly letting the world know when someone slipped up. He didn’t realise two truths, however:

1) Everyone slips up now and then. It might be a big deal, it might be minor, but we all do it.

2) Pretty much anywhere you go you’re part of a team, even if it’s not obvious. And part of being in a team is helping each other out, which includes helping out when someone slips up.

The guy got promoted and very quickly discovered the two truths above. Whenever he slipped up it was like watching an audience part to let a stage diver crash to the floor. No-one covered for him, no-one helped him out when he screwed up. All his screw-ups and slip-ups were blindingly obvious to everyone.

He lasted about 6 months in his new role then quit. The humiliation was just too great.

Posted by SimonTewbi on 15 January 2009 @ 9pm

Same goes for the IT guy at the office. Additionally, becoming friends with the IT guy can lead to other opportunities interesting for geeks, like “testing” new hardware.

Great series, Derek. Looking forward to the next post.

Posted by Joe on 19 January 2009 @ 3pm

Thanks, D. I learned some lessons about respect as the sound guy. Sometimes I’d get impatient and dismissive and inconsiderate. I also eventually learned that the sound guy also a shares the responsibilities as host, and needs to exhibit at least a modicum of graciousness.

(*Ah…the beer bucket…those wuz the dayz!*)

Posted by Jed on 24 January 2009 @ 11pm

Seems to me there’s more going on here than just ‘don’t piss off the sound guy’. I’ll always remember this piece of advice my dad gave me when I was starting work:

‘Praise in public, reprimand in private.’

People do need to brought into line from time to time, but there’s rarely a need to make a song and a dance out of it. When somebody does, it’s usually less about getting the problem sorted, and more about getting themselves attention.

Posted by Chris Mear on 3 February 2009 @ 1pm

If only this post got some hits from congress.gov or whitehouse.gov…

Posted by Phelps on 3 February 2009 @ 1pm

There’s always another sound guy.

Posted by publica on 3 February 2009 @ 1pm