What Ted Lasso Can Teach Your Production Team (A Dispatch)
Filed from the sound booth, not the touchline.
I've spent a fair amount of time around teams — the kind that win, the kind that lose, and the kind that fall apart before either happens. You start to notice patterns. And somewhere between a mid-table football club in Richmond and a church tech booth on a Sunday morning, the patterns turn out to be the same one.
Here's what I mean.
Culture beats talent, every time. The most talented roster in the world will underperform if nobody trusts each other. We've all watched it happen — the gifted volunteer who won't pass the mic, so to speak, and a team that quietly stops trying because talent alone was never going to be enough to hold it together. The teams that actually go the distance aren't the ones with the best individual mixer or the sharpest lighting eye. They're the ones where everybody believes they're better together than they are apart. That's not a soft metric. That's the whole game.
Curiosity beats judgment. There's a piece of advice about darts that's made its way well outside of darts at this point — something about how the people who underestimate you were themselves underestimated once, and if you'd just been curious instead of certain, you might have known that about them. Swap "darts" for "the guy who keeps missing his lighting cue," and the lesson holds up fine. Judgment closes a conversation before it starts. Curiosity — why is this happening, what's actually going on with him this week, what don't I know yet — is usually the thing that actually fixes it.
"I believe in believe" isn't a poster. It's a discipline. It's easy to hang encouragement on a wall. It's harder to keep believing in a volunteer after their third rough week in a row, or in a young production hire who hasn't found their footing yet. But a team that only believes in people when they're already succeeding was never really believing in them at all — it was just enjoying the results. Real belief costs something. That's what makes it real.
Be a goldfish. Ten-second memory. It's a joke in the show and it's genuinely good advice everywhere else. The volunteer who missed a cue during announcements doesn't need to carry that into the offering, and the tech director who had a rough exchange with a staff member on Tuesday doesn't need to bring that same posture into Thursday's rehearsal. Mistakes deserve a moment of attention and then release — not a running tally that gets pulled out every time someone's patience runs thin.
Nobody wins alone, and nobody should have to. The best moments in that show aren't the trophy moments — they're the ones where somebody who'd been struggling gets carried, quietly, by a team that decided his win mattered as much as their own. That's a culture decision, not an accident. It gets built one small choice at a time: who gets checked in on, who gets the benefit of the doubt, who gets covered for without being made to feel like a burden. Teams that do this well don't announce it. You just notice, eventually, that nobody's fighting alone.
Leadership is mostly just consistent care, applied for longer than feels convenient. There's no single dramatic gesture in that show that fixes a broken team. It's the daily stuff — showing up, asking real questions, remembering what somebody told you three weeks ago, being the same person on a good day and a bad one. Production ministry, and production work generally, rewards the same unglamorous consistency. The volunteer who feels cared for isn't usually responding to one big moment. They're responding to a pattern.
Consistency isn't the only thing worth borrowing from that locker room, though. There's joy in it too, and it's just as instructive.
"Football is life." There's a young striker on that Richmond roster who says this more or less constantly, about more or less everything, and it would come off as naive if he weren't so relentlessly right about it. He means it two ways at once — football is everything, and football is also just life, ordinary and full of the same joy you'd find anywhere else if you were paying attention. Production people could stand to borrow that same double meaning. Yes, get the mix right, hit the cue, nail the transition — it matters, treat it like it matters. But don't mistake the stakes of a Sunday morning or a Saturday gala for something separate from actual life. The volunteer running the camera is somebody's dad. The kid on the lighting board is figuring out who he is. The room you're serving is full of people carrying whatever they walked in with. Production is life too, if you let it be — not a departure from the meaningful stuff, just another place it shows up.
That kind of joy is contagious, by the way, and it's underrated as a leadership tool. A team led by someone who genuinely loves the work — who treats a well-run transition like it's worth celebrating, not just worth surviving — tends to play looser and perform better than a team led by someone grinding through it. Danny doesn't win because he's the most talented player in the league. He plays like every touch matters because to him, it does. That's a choice available to anybody running a board, not just anybody running down a pitch.
Joy only gets a team so far, though, if nobody's allowed to admit when things are actually hard. That's where the club's therapist earns her keep.
The toughest person in the building is usually the one who admits they need help. The club's sports psychologist spends most of her screen time getting stonewalled by men who'd rather implode quietly than say out loud that something's wrong. It takes most of them the better part of a season to figure out that asking for help isn't the opposite of strength — it's usually the first real evidence of it. Production culture has its own version of this. The volunteer who's clearly overwhelmed but keeps saying "I've got it." The tech director who's been running on fumes for months because admitting he needs a break feels like admitting he's failing. A team only gets healthier once it's actually safe to say "I'm struggling" out loud — and that safety doesn't happen by accident. Somebody has to build it, on purpose, by not punishing the people who say the hard thing.
What's underneath the behavior is usually the actual problem. She's not interested in fixing the outburst in front of her — she's interested in what's underneath it. A player who suddenly can't take a joke, a coach who's suddenly short with everyone, a volunteer who's suddenly snapping at people who don't deserve it — none of that shows up out of nowhere. The behavior on the surface is rarely the real story. Leading people well means being willing to ask what's actually going on, instead of just managing the symptom in front of you and moving on.
You don't have to have your life figured out to help someone else with theirs. Even the person whose literal job is mental health spends real time in that show figuring out her own stuff — a rough patch, an old wound, a question she hasn't answered for herself yet. That never disqualifies her from being useful to everyone else. It's a good reminder for anyone leading a volunteer team: you don't need to have it all sorted to be the person somebody trusts with their hard week. You just need to actually be present for it.
None of this makes the technical side matter less. A good culture with a bad mix is still a bad mix. Belief and curiosity don't replace competence — they're what make competence sustainable. The teams that last are the ones that took both seriously: care for the people, and rigor about the craft. Pick one at the expense of the other, and eventually it shows.
Consider that filed. Whether you're running sound on a Sunday morning or managing a production crew at a Saturday gala, the lesson's the same one that show kept returning to: the scoreboard matters less than whether the people on your team actually believe you're for them. Get that right, and the technical stuff has a much better shot at falling into place behind it.
New Gear Isn't the Solution (Here's What Actually Is)
Every few months, a church reaches out to us with the same starting point: "Our sound is bad. We need new speakers." Or, "Our video always looks off. We need a new camera." Or, "The livestream keeps having issues. We need to upgrade the switcher."
And sometimes — sometimes — that's true. Gear does wear out. Systems do get outdated. There's a real ceiling that equipment puts on what a team can accomplish.
But more often than not, when we actually walk through a church's space, sit in on a rehearsal, and talk to the volunteer team, the gear isn't the problem. It's the easiest thing to blame, because it's tangible. You can point at a mixing board and say "that's old." You can't point at a training gap or a workflow breakdown the same way — even though that's usually what's actually driving the frustration.
Why Gear Becomes the Scapegoat
New equipment is an appealing fix because it's simple. It's a line item. You raise the budget, place the order, install it, and there's a sense of "we did something." It feels like progress.
Fixing the actual root cause is slower, less visible, and often more uncomfortable — because it usually means having conversations about training, roles, expectations, and how the team works together. That's harder to put in a budget proposal. It's much easier to say "we need a new console" than "we need to rebuild how our volunteer team is trained and organized."
The problem is that new gear on top of an unaddressed root issue doesn't fix anything. It just moves the same problems onto newer, more expensive equipment.
The Three Root Causes We See Most Often
1. Training gaps
A volunteer running a soundboard they were handed with a five-minute walkthrough is going to produce inconsistent results no matter how good the board is. Most audio, lighting, and video issues we're called in for aren't equipment limitations — they're a lack of foundational understanding of how the system is supposed to be used. New gear doesn't fix a training gap. It just gives the same untrained hands a more expensive tool to be inconsistent with.
2. Ministry and volunteer philosophy misalignment
This is the one churches think about least, but it might matter most. Production teams function differently depending on what the church actually believes their role is. Is the tech team there to be invisible and support the service, or are they seen (and treated) as a creative ministry in their own right? Is volunteering on the tech team framed as a serving opportunity with real discipleship and growth attached to it, or just a scheduling slot that needs to be filled? When there's no shared philosophy across leadership and volunteers about why the team exists and what excellence looks like, you get inconsistency — regardless of the gear in the room.
3. Organization and workflow issues
A lot of what looks like a "tech problem" during a service is actually a communication or process problem upstream. No standardized show flow. No clear point of contact between worship planning and the tech team. Last-minute changes with no system for communicating them. Unclear roles on a Sunday morning, so two people assume someone else is handling something and nobody does. These are organizational issues, and they'll create the same chaos whether you're running a ten-year-old system or a brand-new one.
What Actually Solves It
Before any equipment conversation, we'd rather ask:
Does your team understand why the system works the way it does, not just which buttons to press?
Is there a shared philosophy across leadership and volunteers about what the tech ministry is for?
Is there a clear, repeatable workflow for planning, rehearsing, and running a service?
Are the people running the room trained to actually use what they already have?
If the answer to those is no, new gear won't move the needle much. If the answer is yes and you're still hitting a hard limitation, then it's genuinely time to talk equipment — and at that point, an upgrade will actually deliver the results you're expecting, because the foundation underneath it is solid.
Where We Come In
This is why we start every engagement with listening, not a gear list. Before we ever talk about equipment, we want to understand your team, your workflow, and what "good" actually looks like for your church. Sometimes that conversation leads to an equipment recommendation. Just as often, it leads to a training plan, a workflow overhaul, or a conversation about philosophy and roles that ends up mattering more than anything you could buy.
New gear can amplify a healthy system. It can't fix a broken one.
If your church keeps hitting the same production issues no matter what you buy, let's talk about what's actually underneath it.