Every church has a leadership pipeline on paper. Most of them are reading lists. A person completes the material, feels prepared, and then discovers on their first Sunday running something that none of it transferred.
Hadley Baker of Rowlett, Texas, northeast of Dallas, develops leaders at City On A Hill Community Church, and his method is less tidy than a curriculum. He hands over responsibility earlier than is comfortable and stays close enough to catch what falls.
Real Responsibility or None
There is a version of leadership development where the new person shadows, assists, observes, and never actually decides anything. It looks like training. It produces people who have watched a job for two years and still cannot do it.
Baker gives away decisions that matter. The first time someone owns an outcome is the first time they learn anything durable about leading.
The handoff has to be real to work. If everyone knows the pastor will quietly reverse a decision he does not like, the responsibility was never transferred and the person leading knows it.
Baker lives with outcomes he would have chosen differently. That is the price of the thing actually being handed over.
Let Them Do It Badly the First Time
Correcting someone before they have failed teaches them your preferences. Correcting them after teaches them the job.
This is harder than it sounds. Watching a person you are responsible for handle something worse than you would have handled it requires sitting on your hands.
Baker’s read on this is simple. If nobody is allowed to do it imperfectly, nobody new ever does it at all, and the church quietly becomes dependent on four people who cannot take a vacation.
There are limits, and they are about harm rather than quality. A mediocre first attempt at running a small group is fine. A pastoral situation that could damage a family is not a training exercise.
Knowing which is which is most of the skill. Baker draws that line before handing anything over, not after.
Character Shows Up in Small Administrative Moments
You learn very little about someone’s integrity from a conversation about integrity. You learn a great deal from whether they follow up on a small commitment nobody was tracking.
Baker watches those moments. Not as a test people are being graded on, but because leadership eventually puts a person in a position where nobody is watching, and what they do then was already visible in the small things.
Leadership begins with service in his reading of it, and it stops being leadership the moment it becomes position.
This is easier to say than to hold. Every organization drifts toward rewarding visibility, and church work is not immune.
The check is what a person does with a task nobody will see. Setting up chairs is a better indicator than a good meeting.
The Part That Takes the Longest
Developing a leader takes far longer than filling a role. There is a constant pull toward hiring competence instead of growing it, especially when something needs to be covered this Sunday.
Baker keeps mentoring anyway. The people he has handed responsibility to are now handing it to others, which is the only version of this that compounds.
The payoff arrives late and belongs to somebody else. A pastor who needs credit for the leaders he developed will not last at it, because the visible win usually goes to the person now doing the job.
Baker treats that as the design rather than a flaw in it.
There is a practical benefit he will admit to. A church where responsibility is widely held can survive a pastor being sick, traveling, or simply having a bad month.
Organizations built around one indispensable person are fragile in a way that looks like strength right up until it does not.
If you have been in the same volunteer role for six years and nobody has ever asked you to lead anything, that is worth a conversation with somebody.