RoleMap runs on a short survey that every leader answers about every other role in the church. Seven questions, three domains, and a simple score turn a vague sense of how things run into an accurate, shared picture of the whole.
People sometimes assume a tool like RoleMap must run on something elaborate. A long interview, a consultant with a clipboard, weeks of watching how a church operates. It does not. It runs on seven questions, and the honest answers of the people who already do the work.
Here is the part that surprises most leaders. Every person who holds a role in the church answers the same seven questions about every other role. Elders, deacons, ministry leads, paid staff, volunteer leaders. Not about people. About roles. And not about how a role is performing, but about how two roles actually touch each other week to week.
That distinction matters, so let me sit with it before we get to the questions. RoleMap never asks you to rate a colleague's character or effort. It asks how the worship-planning role and the hospitality role coordinate. How the treasurer role and the deacon board role depend on each other. The unit under the microscope is always the connection between two roles, never a person's worth.
Three domains, seven questions
The seven questions fall into three plain groups. Each question is rated from zero to five.
The first domain is Frequency. It measures how often two roles touch at all.
- How often do you communicate with this role?
- How often do your decisions involve coordinating with this role?
- How often do you solve problems together with this role?
The second domain is Flow. It measures which direction the work moves, and it asks the question twice, once each way.
- How much information, work, or output flows from your role to this role?
- How much information, work, or output flows from this role to your role?
The third domain is Stakes. It measures how much rides on the connection.
- How dependent is your work on this role's output, decisions, or availability?
- How much accountability overlap exists between your role and this role?
That is the whole instrument. A leader can work through it in one sitting. There is nothing to study for and nothing to defend, because you are describing your own working reality, not grading anyone.
Why measure flow in both directions
Questions four and five look almost like the same question turned around, and they are, on purpose. One role reports how much it sends to another. The other role reports how much it receives. When those two answers agree, the connection is understood the same way on both ends. When they disagree, you have found something.
A role can say it sends heavy output to another role that reports receiving very little. That gap is not a failure of anyone's memory. It is a real seam in how the church works, and it usually explains a frustration people have felt for months without being able to name it. Because RoleMap asks both sides, it can see the seam that a single interview would miss.
From answers to a picture
The seven scores for any pair of roles combine into one composite, from zero to thirty-five. That single number lets us sort every pairing in the church into five tiers, from Peripheral, where two roles barely touch, up to Peak, where they are heavily intertwined. Lay all the pairs out together and you get a full role-by-role map. Not a diagram of what the bylaws say should happen. A map of what the leaders themselves report actually happens.
This is where the design earns its keep. If one leader described the church, you would get one leader's vantage point, honest but partial. Because everyone answers about everyone, the whole network cross-checks itself. Where many roles independently report leaning hard on a single role, that is not a hunch anymore. It is the church's own testimony, gathered in parallel and laid side by side.
A short survey that tells the truth
None of this asks a church to become more complicated than it is. The genius, if there is any, is in the modesty of the thing. Short questions. The same questions for everyone. Roles instead of personalities. Both directions of flow. A simple score that rolls up into a picture the whole leadership can actually read together.
Most churches carry a vague, shared feeling about how things run, and that feeling is often close to right and occasionally very wrong in the places that matter most. Seven questions, answered by everyone, is what turns that feeling into something you can see. And once a church can see itself clearly, it can lead itself faithfully.
The whole network cross-checks itself, so the map is not one person's opinion but the church's own answer.
