RoleMap

What RoleMap measures

Every church has an organizational chart. The chart shows authority, reporting relationships, and the formal structure of governance. What it cannot show is how those roles actually work together — the dependencies that have grown up over time, the communication channels that have gone quiet, the role-holders who have become structurally central even though their formal position doesn't reflect it, the committees the bylaws describe as independent that the rest of the church treats as one.

RoleMap measures the relational pattern that lives below the level of formal awareness. It asks each role-holder, one careful question at a time, how they actually experience their working relationships with every other role in the church. Then it turns those answers into a heat map and a written analysis your leadership team can read together and act on.

The analysis surfaces four things that formal structure rarely makes visible: the roles your church most depends on, the perception gaps between role-holders who see their working relationship differently, the roles that have collapsed into one another in practice even if the bylaws keep them separate, and the gap between what your governance documents intend and what is actually happening day to day.

The questionnaire

Each role-holder receives an invitation by email with a magic link. The questionnaire takes about fifteen minutes and is mobile-friendly — most respondents complete it on their phone during a quiet moment. There is no account to create and no password to remember.

For every other role in the church, the respondent answers three questions:

Direction of relationship. Do you provide them with information or items they need? Do they provide you with information or items you need? Or do you both provide each other? This captures whether the dependency runs one way or both.

Frequency of communication. Daily, more often than weekly, weekly, less than weekly, monthly or less, or never? This captures the cadence of contact.

Level of influence. How much does this role's work affect your ability to do yours — critically, somewhat, or little? This captures the structural weight of the relationship.

After the three structured questions, the respondent has the option to add a free-text comment about that specific role-pair. Many respondents take this option. Comments are part of what makes the report grounded: when the analysis identifies a finding, it can draw on real respondent voices to explain what the pattern means in practice. Comments are quoted in the report with the respondent's name redacted.

The questionnaire is identical in structure for everyone, regardless of role. A senior pastor and a hospitality committee member each rate every other role on the same three dimensions. This consistency is what makes the analysis comparable across roles.

The four analytical layers

Once all responses are in (or once the leadership team chooses to proceed with partial data), four analytical layers run.

Centrality

This identifies the church's structural backbone — the roles others most depend on. A role with high centrality is one that, if it transitioned, would create the largest blast radius in operational continuity. Centrality is not the same as authority; the most central role in a church is often not the senior pastor but the office manager, who handles scheduling, communication, facility coordination, and routine information flow that everyone else relies on. The centrality ranking gives the leadership team a clear-eyed picture of where structural risk concentrates and where succession planning, sabbatical coverage, and role-clarity documentation deserve special attention.

Perception asymmetry

This identifies pairs of role-holders who experience their working relationship at substantially different intensity. A trustees chair who rates her interaction with the elder team at the floor of the scale, paired with an elder team that rates its interaction with the trustees chair near the ceiling, is a perception asymmetry. These gaps are sometimes the result of one role passing information toward another without expecting return communication, sometimes a role taking on responsibilities the other party does not perceive, and sometimes an interaction that has gone quiet from one direction. The pattern is not a verdict but an invitation — these are the conversations the leadership team should be having, approached with curiosity rather than blame.

Consolidation candidates

This identifies pairs of roles that the church treats as functionally interchangeable, even when the formal structure says they are distinct. Two roles whose patterns of relationship with everyone else look nearly identical are filling the same relational slot regardless of what the bylaws say. Sometimes these are designed pairs — a treasurer and assistant treasurer, by design, share the same relational fingerprint with everyone else, because the bylaws structure them as deputies. Sometimes the pattern reveals genuine redundancy, where two formally-separate roles have collapsed into one body and could be consolidated, simplified, or restructured.

Bylaws-vs-actual

When the church provides its bylaws and organizational chart during engagement setup, a fourth layer becomes possible — the comparison between the church's intended governance structure and the actual relational pattern revealed by the heat map. Where they align, the church's structural design is functioning as written. Where they diverge, the gap names exactly where governance reform, role clarification, or bylaw amendment may be needed. This is typically the most actionable section of the report, because it translates observed patterns into specific governance proposals grounded in the church's own documents.

The AI-assisted analytical engine

RoleMap uses Claude, a large language model from Anthropic, to convert the matrix of role-pair scores, the four analytical layers, the respondent comments, and the supporting documents into structured narrative analysis. The AI handles the analytical writing — the heavy lifting of synthesizing many data points into coherent prose, identifying the patterns worth highlighting, and drafting recommendations grounded in the data.

Anton Brown personally reviews and refines every report before it reaches the church. This is not a perfunctory check; it is a deliberate part of how RoleMap works. The review ensures pastoral sensitivity in framing, factual accuracy in bylaws citations, appropriate weighting of findings, and the kind of contextual judgment an AI alone cannot reliably produce. Anton edits sections that need a more nuanced touch, softens language where the analysis lands too pointedly, removes findings that the data does not support strongly enough, and adds connections across sections that an AI sometimes misses.

The combination of AI-assisted analysis and human curation is how RoleMap delivers in-depth narrative reports at accessible pricing while preserving the kind of attention each engagement deserves. We disclose this combination openly, because we think it is part of what makes the product trustworthy rather than something to hide.

Data submitted through the Claude API is not used to train Anthropic's models. This is part of Anthropic's published data-handling commitment for API usage and is the reason we use the API path rather than other Claude offerings.

What you receive

The deliverable is a written narrative report with eight to nine sections, depending on whether your engagement includes follow-up comparison data. The report opens with an executive summary, explains how to read the heat map, develops the four analytical findings in detail, identifies where structure has drifted from intent (when bylaws are provided), proposes prioritized recommendations, and closes with a methodology and confidence note. Reports typically run twelve to eighteen pages, in Word and PDF formats.

A heat map visualization accompanies the report — a colored matrix showing the strength of every role-pair relationship in your church. The map uses qualitative tier language (peripheral, low, moderate, high, critical) rather than algorithmic numerical values, and the tiers are explained in a brief reading guide at the start of the report.

For Tier 2 (Full Consultation) engagements, the deliverable also includes a discovery call at the start, a 90-minute leadership presentation of findings (virtual by default, in-person available with travel costs billed separately), and a 30-day follow-up call to discuss implementation.

What RoleMap is not

A few clarifications about what kind of analysis RoleMap is, since church leaders sometimes encounter similar-sounding tools.

RoleMap is not a spiritual-gifts assessment. It does not evaluate individuals' calling, fit, or proper place to serve. Frameworks like Bruce Bugbee's Network and similar spiritual-gifts inventories address where individuals are most fruitful in service. They are complementary to RoleMap but address a different question. RoleMap describes the relational pattern of the structure that already exists; gift-based frameworks describe the proper placement of individuals within whatever structure exists.

RoleMap is not professional management consulting. It does not provide legal advice, financial advice, or organizational psychology services. Consulting engagements from national firms typically begin around six thousand dollars and address vision, budget, facilities, staffing, and strategy comprehensively. RoleMap is a focused, specialized tool that addresses one critical question — how do your roles actually interact — at a fraction of the cost. Churches navigating major transitions often benefit from both, in sequence.

RoleMap is not a 360-degree review of individuals. The unit of analysis is the role, not the person. Findings name structural patterns and roles; they do not evaluate or rank individuals.

RoleMap is not a public-facing assessment. Reports are intended for confidential leadership-team review. Findings are conversation starters, not verdicts. They are best approached with curiosity rather than concern; most of what RoleMap surfaces is the kind of structural insight that lives below the level of formal awareness, and naming it is half the work of acting on it.

Methodological lineage

For readers who want to know where the analytical concepts come from, a brief note. The centrality measure is grounded in the network-science literature established by Linton Freeman in the late 1970s and developed extensively in the decades since. Perception asymmetry as a structural signal draws on work in organizational network analysis and team dynamics. Column-correlation analysis for identifying functionally interchangeable roles is a standard technique in cluster analysis. The framework for comparing intended structure against observed practice — the bylaws-versus-actual layer — draws on the broader church-administration literature, including Aubrey Malphurs's work on strategic planning and structural reform.

What is unique to RoleMap is the integration: a questionnaire designed for ministry contexts, an analytical pipeline that combines the four layers into a coherent picture, a narrative report that translates structural findings into pastoral language, and a human review step that ensures the result is something a leadership team can actually use.

If you have any question about the methodology — whether for a church considering an engagement, a consultant familiar with related frameworks, or simply a curious reader — write to hello@rolemap.co. We respond personally.