The Volunteer Pipeline Nobody Builds Until They’re Desperate

Just about every organization I know builds its volunteer or leadership pipeline the same way: in a panic, three weeks before it’s needed.

Someone’s about to step down. A service is about to launch. A department’s about to lose its only person who knows how the thing works. And suddenly there’s a scramble to find somebody, anybody, who can fill the role well enough to keep the lights on.

I’ve done this. I’ve watched churches, nonprofits, and businesses do this. And I’ve come to believe it’s the single most expensive habit a leader can have, because it optimizes for the wrong thing at exactly the moment the stakes are highest.

Here’s the shift I think we all need to make: stop asking “who can fill this?” Start asking “who am I developing, right now, whether I need them yet or not?”

Warm bodies are not the goal

A filled seat feels like progress. It isn’t, at least not by itself. A church doesn’t need more greeters standing at the door. It needs people who understand why hospitality matters enough to greet like they mean it, on a bad week, without being told what to do. A business doesn’t need someone who can technically operate the role. It needs someone who can make good decisions when no one’s watching.

The difference between those two things is training and time. And training and time are exactly what a panic-hire skips, because panic only has room for “can you start now.”

So the first mental shift is this: recruiting fills a role. Developing builds a person. Those are not the same project, and an organization that only does the first one will spend the rest of its life refilling the same gaps.

Build the pipeline before you can see the gap

The uncomfortable truth is that the best time to start developing your next leader is right now, before you have any specific opening in mind. That feels inefficient in the moment. You’re investing in someone for a role that doesn’t exist yet. It’s actually the opposite. It’s the only way to have a ready person instead of a rushed one when the role does exist.

Practically, that means:

Name your bench, on paper, before you need it. Every key role in your organization should have at least one name next to it under the heading “who could step into this in six months if they had to.” If that line is blank, you don’t have a pipeline. You have a single point of failure with a job title.

Give people real responsibility before they’re “ready.” Readiness is mostly manufactured by being given the thing and supported through it, not by waiting until someone feels prepared. The apprenticeship model has this exactly right: shadow, then assist, then lead with someone watching, then lead alone. Most organizations skip straight from shadow to lead alone, and then act surprised when it goes poorly. The model from nursing even takes this one step further as they employ the see one, do one, teach one model. The teach one aspect here is how the leadership pipeline naturally builds beyond its first generation.

Make the informal formal. If you’re mentally tracking “she’d be great at this eventually” but you’ve never said it out loud to her, that’s not development. That’s a private hunch. Say it. Put a timeline on it. People rise toward what’s actually been named for them.

The right person, trained the right way, matters more than the right number

A pipeline built purely to hit headcount will hand you people who can occupy a role and not much more. The goal isn’t more names on a roster. It’s fewer roles that depend entirely on one irreplaceable person, and more people who’ve actually been formed for what they’re carrying.

You don’t need more warm bodies filling seats. You need the right people, trained the right way, ready before you need them…not found after you already do.

This is where “the right person” actually gets defined. It’s not primarily about talent, though talent matters. It’s about character under pressure and a track record of small faithfulness, someone who did the unglamorous version of the job well before anyone was watching. That’s a much better predictor of how they’ll do the job when it’s hard than how impressive they sounded in an interview or how quickly they said yes.

What this actually costs you

Real development is slower than recruiting and less visible in the short term. You will spend time on someone who isn’t producing much yet. You will sometimes invest in a person who ultimately isn’t the right fit for the role you had in mind, and that will feel like a loss.

It isn’t. An organization that develops people, even the ones who don’t end up in the role you originally imagined for them, ends up with a deeper bench across the board because development rarely stays contained to one slot. The person you trained for one role often turns out to be exactly right for a different one two years later, precisely because you invested before you had a specific use for them.

Compare that cost to the one you already know: the scramble hire, the person who technically fills the gap but needs constant oversight, the burnout of the two or three people who always get asked because they’re the only ones ready. That’s not actually the cheaper option. It just hides its cost until later, and then it hides it in your best people’s exhaustion.

Start this week

You don’t need a program to start. You need a list and a conversation.

Write down every role in your organization that would hurt if the person in it left tomorrow. Next to each one, write a name of someone with the character for it, even if they don’t have the skill yet. Then have one honest conversation this week with one of those people: I see something in you. Here’s what I’d like to start handing you.

That’s the whole pipeline, at the start. Everything else is just repeating that pattern faithfully, long before you’re desperate enough to need it.