What a Church in Decline Taught Me About How Churches Work.

I did not set out to build a product. I set out to turn a church around.

Some years into pastoral ministry I found myself leading a congregation that was, by most honest measures, in decline. The kind of situation where the org chart still looked orderly on paper while the reality underneath it was quietly coming apart. I loved that church. I did not want to preside over its decline. And I could feel that something in how the whole thing was put together was wrong, but I could not point at it.

This is the trap of a church in decline. You can feel the dysfunction. You cannot locate it. Everyone is working hard. Everyone means well. And it is still not adding up, and you do not have language for why.

The problem was never the people

For a long time I did what most leaders do. I looked at people. Who was carrying their weight, who was not, who needed encouragement, who needed a harder conversation. That framing got me almost nowhere, because the people were mostly fine. Faithful, willing, tired.

The thing I slowly realized is that the problem was not living inside any one person. It was living between them. It was in the connections. Two roles that overlapped so that work kept falling through the seam. One seat that had quietly become the hinge the whole church swung on, so that person was exhausted while nobody could say exactly why. A handful of decisions that never got made because it was genuinely unclear whose call they were.

None of that shows up when you look at individuals. It only shows up when you look at how the roles interact. And I did not have a tool that looked at that, so I started building one for myself.

Forty-six roles, and one person holding fourteen

I sat down and did something I had never done before. I stopped counting people and started counting roles. Not heads. Jobs. Every distinct responsibility the church actually needed covered in order to function week to week. Preaching and teaching, yes, but also the finances, the facilities, the hospitality, the communications, the pastoral care, the setup and teardown, the dozens of quiet functions that only get noticed when they stop happening.

I ended up with forty-six roles. Forty-six distinct jobs that had to be carried for the church to run.

Now, this was a small congregation. Nowhere near forty-six people running things. That was the whole shock of the number. Forty-six roles did not mean forty-six leaders. It meant forty-six jobs piled onto a handful of people, and when I looked at how those jobs were actually distributed, one person was holding fourteen of them. Fourteen roles on a single set of shoulders.

That one seat became the picture of the whole problem for me. Not a lazy church. Not unwilling people. A tiny group of faithful people quietly carrying far more roles than any human being was built to hold, with one person carrying the weight of fourteen.

Then I did the harder part. Instead of asking what each person was like, I mapped how each role connected to every other role. How often two responsibilities touched. How much work flowed between them and in which direction. How high the stakes were when they did connect. And crucially, whether both sides of a connection experienced it the same way, because it turns out they very often do not. One role feels like it is carrying a relationship the other role barely registers.

Forty-six roles produces a lot of connections. Hundreds of them. But when I laid the whole thing out as a map, for the first time I could actually see the church. Not the church I intended. The church that was really running.

What the map showed

The map showed me exactly the things I had been feeling but could not name. It showed me the seats that were overloaded, and it showed me that the overload was structural, not a failure of the people in them. It showed me where roles overlapped and no one owned the seam. It showed me where our written structure and our actual practice had drifted apart, sometimes by years. And it showed me something I had half suspected but never proven. A good part of those forty-six roles did not need to exist as forty-six separate things. They had multiplied over the years. Splintered. The same underlying work had been chopped into more and more little pieces until nobody could hold a coherent picture of it.

So I did the work the map made possible. I consolidated. I took those forty-six fragmented roles and rationalized them down to twenty-three coherent ones. Not by cutting the work. The work still had to get done. By combining responsibilities that belonged together, ending the ones that were duplicating each other, and drawing clean lines so each seat was a real job a real person could actually hold. Forty-six splintered roles became twenty-three sustainable ones.

The map did not tell me to do that. That part was still mine. I know my church, and no map decides for a pastor. But for the first time I was deciding with my eyes open instead of guessing in the fog. And decisions I had been circling for a long time suddenly had a clear place to land.

That is the whole conviction behind RoleMap. A church is not a stack of individuals. It is a network of roles, and the health of the church lives in how those roles interact. If you can see the network honestly, most of the fog burns off.

Why I turned it into something other churches can use

I kept the method after that season, because I kept needing it. And the more I talked with other pastors, the more I heard the exact fog I had been stuck in. "I have ten people on my staff and I cannot tell you, on a sheet of paper, who is actually carrying this church." I knew that sentence from the inside. I had lived it.

So I built the survival tool into something a church can actually run. The leaders answer a short, honest survey about how they work with each of their teammates. The analysis turns those answers into one clear map of how the whole network operates. And I review every single one personally before it goes out, because I have sat in the seat where a wrong read on the map could cost real people real things, and I am not willing to hand a church a report I have not looked at with my own eyes.

The takeaway

I learned how churches work by watching one in decline, and by finally building a way to see it clearly. What I learned is that the people were never the real problem. The wiring was. Too many fragmented roles piled onto too few people, with one person holding fourteen jobs because the structure had quietly handed them over one at a time. The people were faithful. The wiring was broken. And wiring is something you can actually understand and change.

RoleMap is that tool, made shareable. It is the map behind your org chart, built by someone who needed it before he ever sold it.

If any of this sounds like the church you are leading right now, email me directly at anton@rolemap.co. Tell me what you are seeing, or just ask to see what a RoleMap actually looks like. No pressure and no pitch. I have been where you are, and I am always glad to talk it through with someone who is trying to see their church clearly.