Gibbs' Rules for the Church Tech Booth

There's a particular kind of leader who doesn't say much, but when he does, it's worth writing down. NCIS's Leroy Jethro Gibbs built an entire reputation on that — a gruff, no-nonsense team leader who ran his unit on a short list of hard-earned rules instead of a stack of policy manuals. Say less. Mean more. Earn trust the slow way, through consistency, not charisma.

It's an unlikely place to look for church leadership wisdom. But strip away the crime scenes and the coffee obsession, and what's left is a pretty solid philosophy for running any team well — including the one running sound, lights, and cameras on a Sunday morning.

Never Screw Over Your Own Team

One of Gibbs' most repeated principles boils down to a simple idea: loyalty to your own people isn't negotiable. Whatever disagreements happen inside the team stay inside the team, and you never throw a teammate under the bus to make yourself look better or to get out of a hard moment.

Production teams need this same rule, badly. It's tempting, when something goes wrong in front of the congregation, to quietly signal "that wasn't me" or let a volunteer take the blame alone for a mistake that was really a system failure. A team that protects each other — publicly and privately — builds the kind of trust that makes people willing to take risks and admit mistakes instead of hiding them.

Never Be Unreachable

Gibbs' team could always get him when it mattered. Not because he had nothing else going on, but because being available when it counted was simply part of the job he'd taken on.

Leading a volunteer team means something similar. Volunteers need to know that if something goes wrong on a Wednesday night rehearsal or a Sunday morning, there's someone they can actually reach — not someone perpetually too busy to respond. Availability isn't the same as being on call every hour of every day. It's making sure the people counting on you know you're actually reachable when it matters most.

Always Work as a Team

Gibbs never solved a case alone, no matter how sharp his own instincts were. Every rule he had about trusting his gut was balanced by an equally strong belief that the team, working together, got further than any one person working solo.

This is worth remembering anytime a production is running well because of one especially gifted volunteer. A team that depends entirely on one person's talent is fragile — that person gets sick, moves away, or burns out, and the whole system collapses. A team that's actually built to work together, where knowledge and responsibility are shared, is a team that survives turnover. Build for the team, not just the star player.

It's Better to Ask Forgiveness Than Permission

This is one of Gibbs' more controversial rules, and it's not a blank check for recklessness — it's a statement about ownership. Somebody who's paralyzed by needing sign-off for every small decision isn't actually leading. They're just managing risk to themselves.

There's a version of this that's healthy for volunteers and staff alike: trusting people enough to make good calls in the moment, rather than requiring permission for every reasonable judgment call during a live service. A tech team that has to stop and ask before adjusting a fader or catching an obvious mistake isn't actually equipped to run a live event. Build people you can trust to make the call — and back them up when they do.

Sometimes, You're Wrong

Gibbs isn't infallible in that show, and to his credit, he doesn't pretend to be. One of the more memorable moments in the series is simply an acknowledgment that even the most experienced, most trusted leader gets it wrong sometimes — and that admitting it is part of what makes the trust real in the first place.

This matters enormously for anyone leading a tech or production team. A leader who can't admit a mistake teaches the whole team, without saying a word, that mistakes are something to hide rather than own. A leader who says "I got that wrong, here's what I'm changing" gives everyone else permission to do the same. That's not weakness. That's the thing that actually makes a team safe enough to grow.

Pay Attention — There's Usually a Pattern

Gibbs had a habit of noticing things other people walked past — a detail out of place, a pattern nobody else caught, a gut feeling worth chasing down instead of dismissing. It wasn't magic. It was the product of paying close, sustained attention over a long career.

The same instinct serves a production leader well. The volunteer who's been a little off for three weeks running. The recurring technical issue that keeps almost-but-not-quite causing a problem. The small friction point in the run of show that nobody's addressed because it hasn't broken yet. Leaders who pay attention catch these things before they become real problems. Leaders who are too busy to notice usually find out the hard way instead.

The Bottom Line

Gibbs never ran his team on charisma. He ran it on consistency, loyalty, hard-earned trust, and a willingness to admit when he'd gotten something wrong. None of that requires being the loudest person in the room or the most naturally gifted. It requires showing up the same way, day after day, and treating the people on your team like they're worth protecting.

That's a rulebook worth borrowing — whether you're solving a case or running FOH on a Sunday morning.