Build Teams That Outlast the Project

The proudest moments of my career have a strange shape. They are the Sundays a production ran perfectly while I sat in the congregation. The launches that shipped after I had moved on. Two decades of building teams, most of them volunteer, taught me a goal nobody puts on a job description: work toward your own unnecessity.

I should say up front that volunteer teams are the best leadership laboratory I know, and I got twenty years in it. When I ran production teams at churches in Georgia and Alabama, nobody on the crew owed me forty hours or a career. They were teenagers, retirees, people with demanding day jobs, giving up their Thursday nights and Sunday mornings because they wanted to. You cannot compel a volunteer with a paycheck or a performance review. You can only build something worth belonging to. Strip away the leverage and what remains is leadership in its purest form, and everything I learned there turned out to work even better in rooms where people do get paid.

The years that tested the ideas hardest were the church I planted and pastored in Columbus, Georgia. We started with nothing: no staff, no teams, no systems, zero people. Over three years it grew to about a hundred and fifty, and every team that growth required, hospitality, kids, worship, production, had to be built from people who had never done the job before. There is no faster education in what actually builds teams and what merely manages them. Here is what survived that education.

Recruit for hunger, train for skill

Every strong team member I ever recruited had the same profile: limited experience, unlimited curiosity. Skills are trainable in weeks. Hunger is not trainable at all. The volunteer who asks what does that button do will outgrow the experienced operator who guards what they know. I stopped recruiting from talent and started recruiting from interest, and my teams got better.

The counterintuitive part is that experience can actually be a liability when it arrives with the wrong posture. I have onboarded people with impressive resumes who treated every procedure as a debate and every teammate as an audience, and I have onboarded a student who had never touched a video switcher and was directing multi-camera services within a couple of months, calmly, because she wanted it and the system supported her. After enough repetitions of that pattern you stop being surprised by it. Skill has a ceiling you can see during the interview. Hunger compounds for years.

So my recruiting changed shape. I stopped asking "who here has done production?" and started watching for something smaller: who lingers near the equipment after the service, who asks a second question after the first one is answered, who shows up early without being asked. Those are the tells. When I invite that person in, I am explicit about the deal: I do not need you to know anything. I need you to want to know things. Everything else is my job.

Teach the why behind every how

A team trained only on procedures collapses at the first situation the procedures did not anticipate. A team that understands why, why this mix for the stream, why this deadline, why this tone in public replies, improvises correctly when the plan runs out. Explaining why takes longer. It is the difference between operators and owners.

Live production supplies the proof every single week, because live means the plan always runs out. The speaker skips a segment. The video file will not play. The service order changes while the service is happening. A camera operator who only knows "hold this shot until told otherwise" freezes in those moments, waiting for instructions that nobody has time to give. An operator who knows the why, that the camera's job is to show the congregation what they would want to see if they were closer, makes the right move without being told. I have watched volunteers do exactly that in moments that would have rattled professionals, and the common thread was never talent. It was that someone had taken the time to explain the purpose, not just the procedure.

The habit that builds this is cheap: narrate your reasoning out loud, constantly. When I set a mix a certain way, I say why. When a deadline is what it is, I explain what is downstream of it. It feels slower, and for the first month it is slower. Then it starts paying interest, because people who understand the why begin generating better hows than the ones you gave them. The first time a team member improves your own procedure and can defend the improvement in terms of the purpose, you have crossed the line from operators to owners, and there is no going back across it.

Handoff is the goal, not the emergency

Most leaders document in a panic, right before a vacation or a resignation. Healthy teams treat handoff as a habit: runbooks anyone can follow, a second person shadowing every critical role, and deliberately stepping back while you are still present to catch what wobbles. If the team cannot run a normal week without you, that is not indispensability. That is a single point of failure with your name on it.

The stepping back is the part leaders skip, so let me describe how it actually works. Documentation alone is not a handoff; nobody discovers what a runbook is missing by reading it. They discover it by running the week while the author is still nearby. So the progression I use is deliberate. First, they shadow you. Then you shadow them, saying nothing unless something is about to catch fire. Then you sit in the congregation, or take the Sunday off, while they run it, and Monday you ask what wobbled. The wobble list goes into the runbook, and the runbook gets truer every cycle. Do that for a season and the week I am absent looks identical to the week I am present, which is the whole point.

There is an emotional honesty required here that deserves naming. Being needed feels good. The phone calls, the "we could not have done it without you," the certainty that the thing collapses in your absence: all of it flatters, and all of it is a warning sign wearing a compliment's clothes. I have had to talk myself down from that feeling more than once, because the alternative is the story every organization knows, the irreplaceable person who eventually, inevitably, leaves anyway, and takes the entire operation's knowledge out the door with them. Train your replacement while nothing is wrong. It is the most generous thing a leader does, and the most neglected.

Make it safe to wobble

None of the above works in a room where mistakes are expensive. Volunteers especially, but honestly everyone, will retreat to the smallest safest version of their role if an error earns a public correction. And a team operating at its smallest safest version cannot grow, because growth requires reps at the edge of ability, and the edge of ability is where mistakes live.

So the culture rule in every room I have run is simple: mistakes get debriefed, never punished, and the debrief targets the system before the person. A wrong graphic on screen is a checklist question before it is a person question. Ninety percent of the time the system had a gap: an ambiguous label, a missing confirmation step, a run sheet that two people read two ways. Fix the gap and the mistake becomes a donation to the team's future. Shame the person and you get something worse than the mistake: a team that hides problems from you, which means you now find out about failures the same way the audience does.

The leader sets this tone with one behavior above all others: narrating their own mistakes first. When I miscalled a camera cut or mangled a schedule, the team heard about it from me, in the debrief, with the same system-first analysis. A leader who is safe to be wrong around produces a team that is honest, and an honest team fixes things while they are still small.

Multiplication is the metric

The question that measures leadership is not how good is your team. It is how many leaders has your team produced. People I trained have gone on to run rooms, departments, and organizations of their own, and that lineage matters more than any single production I ever ran.

This reframe changes daily decisions, not just annual reflections. When multiplication is the metric, the person you delegate to is not the one who does it best today; it is the one who will grow most by doing it. The interesting project gets given away instead of hoarded. The training hour beats the polishing hour, because polish depreciates and people compound. Some Sundays the stream was five percent worse because a developing director was in the chair instead of me, and that five percent was tuition, paid gladly, for a leader the organization would still have five years later.

Years down the road, the return on that tuition is the only part of the work that still moves me. Productions are forgotten by Tuesday. Websites get redesigned. Even the organizations change shape. But somewhere tonight a person I handed a headset to at seventeen is leading a team of their own, teaching the why behind every how to somebody new, and that chain does not show up on any resume, including mine. It is just the actual product.

Projects end. That is what projects are for. Build the kind of team that keeps going when this one does.