A long row of plain wooden chairs set out along a concrete wall in an empty room

leadership

Your Leadership Team Is Bigger Than Your Payroll

Anton Brown4 min readleadership

Churches tend to count their leadership by payroll, which undercounts the people the church actually runs on. The real number includes elders, deacons, and the ministry leads who have never appeared on an org chart, and it changes what a church is able to see about itself.

Ask a pastor how many leaders his church has, and the answer usually comes from the payroll. Four. Five. Two and a half, if he counts the part-time music position honestly. It is the number closest to hand, because it is the number that shows up in the budget every month.

Then walk the building on a Wednesday evening. Elders. Deacons. Ministry leads. The woman who has run the food pantry for eleven years without a title on any chart. The man who has handled the building, the keys, and every vendor call since before the current pastor arrived. Count everyone the church actually depends on in order to function, and the number is rarely four or five. In most churches it is twenty or more.

The distance between those two counts is not a rounding error. It changes how a church understands its own structure, and it does so in two costly directions.

Churches underestimate their own complexity

Structural load does not follow the payroll. Single points of failure, concentrated dependency, and overlap between roles live in the unpaid layer as much as the paid one, and often more. The reason is not mystery but documentation. Paid positions tend to have written descriptions, review conversations, and some defined handoff when the person leaves. Unpaid positions frequently have none of that. No one wrote down what the role does, because the role is simply whatever that person does.

So the church learns the scope of the job the hard way, by discovering everything that stopped. The volunteer who has held a ministry together for a decade is frequently the most load-bearing role in the building, and she appears on no org chart. The places where structure is most fragile are exactly the places where the record is thinnest.

Counting yourself out on the wrong number

The second consequence is quieter. A pastor reads that a tool maps a church's leadership network, runs the arithmetic on his staff, and thinks, "We only have four on staff. We are too small for that." The arithmetic is fine. The count is wrong. The question was never how many people the church pays. It is how many named leaders the church has, paid and unpaid together.

By that count, churches with small payrolls are squarely in scope. Often they are the clearest case, because a larger share of their structure sits in the undocumented layer. One practical note: RoleMap engagements are sized by the number of named roles mapped, not by staff headcount or budget. A church with three people on payroll and twenty-two named leaders is a twenty-two-role map. Payroll never enters the calculation.

Counting them is accuracy, not courtesy

I want to be careful here, because this point is easy to sentimentalize. Counting unpaid leaders as real leaders is not a courtesy extended to people who work hard. It is accuracy. If a ministry stops when a person stops, that role is load-bearing, whatever the church does or does not pay for it. Leaving it off the map produces a picture of a church that does not exist.

If you are unsure who belongs on the list, three questions settle most of it.

  • Does the person hold a named position in your governance, such as elder, deacon, or trustee?
  • Does the person lead a ministry area, whether or not the position carries a title?
  • Would a month of that person's absence visibly change how the church runs?

Anyone who draws a yes belongs on the list, whether or not the church has ever written the role down.

Count before you conclude

When I mapped my own church, the engagement covered twenty-three roles. Most of them were unpaid. Had I gone by payroll, I would have concluded there was almost nothing to map, and I would have missed the parts of the structure that most needed looking at.

So before you decide your church is too small for this kind of work, write the list. Not the payroll, the names. Put down everyone your church counts on to lead something, and see what the number turns out to be. Whatever it is, it is the honest place to begin.

The question is not how many leaders your church pays, but how many leaders your church depends on.

Photo by Ion Fet on Unsplash

Share

Keep reading

A dirt path worn through a dry golden field, running past a wooden gate toward distant hills

objections

A Map of Your Roles, Not a Review of Your People

When a pastor proposes RoleMap, someone on the team usually hears performance review. The concern is reasonable and it deserves a straight answer. RoleMap measures roles and the dependencies between them, and no one rates anyone's job performance, character, or fitness.

· 4 min read

A stack of aged, folded handwritten documents resting on a dark green tabletop

bylaws

When the Bylaws Describe a Church You No Longer Are

A church's governing documents describe an organization, and over the years the church quietly becomes a different one. RoleMap compares the structure the documents assume against the dependency network leaders actually report, so a church can amend from evidence instead of guesswork.

· 4 min read

A man in a blue and black jacket and black cap standing outdoors at golden hour

sabbatical

Planning a Pastor's Sabbatical Before You Need One

A sabbatical works far better when a church has mapped what quietly rests on the departing role before that leader steps away. RoleMap shows the single points of failure in advance, so the load can be handed off on purpose instead of discovered mid-absence.

· 4 min read