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

Somewhere in the first conversation about RoleMap, a leader on the team usually goes quiet. Then the question comes. Is this a performance review? Underneath it sits a sharper question people are often too polite to ask out loud. Is the pastor building a case to cut somebody?

I take that seriously, because it is a reasonable thing to wonder. Churches have watched instruments get used as ammunition before. A survey goes out, the results are read selectively, and a few months later a faithful volunteer is quietly moved aside with the data cited as the reason. If that is what a leader fears, his hesitation is not obstruction. It is loyalty to the people he serves, and it deserves a straight answer rather than reassurance.

Here is the straight answer. RoleMap maps roles and the dependencies between them. It does not evaluate persons.

Nobody rates anybody

Every leader answers the same seven questions about every other role in the church. Not one of those questions asks how well anyone does his job. They ask how often two roles are in touch, how often decisions have to be made together, how much work flows in each direction, how much one role's work hinges on the other, and how much accountability the two share.

Read that list again and notice what is missing. There is no competence rating. No character judgment. No question about effort, attitude, fitness, or whether someone should still be in the seat. The unit under the microscope is always the connection between two roles, never a person's worth. A respondent is describing his own working reality. He is not grading a colleague, and he has nothing to defend.

Findings about shape, not about people

The signals a RoleMap produces are structural by design.

• Centrality shows where the church's load concentrates.
• Asymmetry shows where two people describe the same shared relationship differently.
• Consolidation shows where two roles have quietly merged in practice.
• The bylaws comparison shows where the written structure has drifted from lived practice.

Consider what a centrality finding actually says. Suppose a report notes that one role carries critical dependency from nine others. That is a sentence about the church's shape. It is not a verdict on the person in that seat. In my experience the most central role tends to be held by one of the most faithful people in the building, someone who has said yes for years without complaint. The map is often the first thing that has ever made that load visible to anyone else.

The honest part

I do not want to oversell the safety of this, because that would be its own kind of dishonesty. A map can surface uncomfortable truths. It can show that a role is carrying far less than everyone assumed. It can show that a line of accountability everyone believed was working has gone silent from one side. Leaders should not pretend otherwise before they begin.

The discipline is in what a leadership team does next. Structural findings get structural remedies. Redistribute weight. Clarify a reporting line. Merge two roles that have already merged in practice, or split one that is quietly doing the work of two. Staff a gap the church has been asking a volunteer to cover on goodwill. Each of those responses changes the structure, and each one honors the person standing inside it.

And if a leadership team is determined to use an instrument as ammunition against a person, no instrument will prevent it. That is a problem in the room, not a problem in the map. The honest work then is to deal with the room, not to add a tool to it.

Why I built it

I built RoleMap to care for leaders, not to sort them. The people I had in mind while designing it were the quiet ones who carry more than anyone realizes and would never say so. If a church runs this well, the person most likely to feel relief is the one everybody depends on.

If someone on your team raises this objection, take it seriously. Show them the seven questions and let the instrument answer for itself.