The relationship mapping tools guide helps you choose a format for the map. For the people around one project, use the stakeholder mapping guide instead.
Organizational mapping is the practice of drawing how an organization actually works: who decides, who influences whom, how information travels, and where work passes between teams. An org chart shows one of those things, the formal reporting lines. An organizational map shows the rest.
The boxes and lines on an org chart say who reports to whom on paper. They do not say whose buy-in a decision needs, which team quietly holds up another, or who everyone asks before they act. That structure lives in the relationships between people, and you have to map it yourself.
What Is Organizational Mapping?
An organizational map puts people, teams, and processes on one canvas and connects them with labeled relationships. It answers questions an org chart cannot:
- Who has the final say on a given kind of decision?
- Whose opinion do the decision-makers trust?
- How does information reach the people who need it, and where does it stop?
- Which teams depend on each other to get work done?
Org Chart vs Organizational Map vs Stakeholder Map
| Map | Shows | Scope |
|---|---|---|
| Org chart | Formal reporting lines | The whole organization, on paper |
| Organizational map | Formal lines plus influence, information flow, and work dependencies | The whole organization, or one part of it, as it works |
| Stakeholder map | Who affects or is affected by one initiative, and their stance | One project or decision |
The maps build on each other. An organizational map of a division is a good starting point for the stakeholder map of any project inside it.
What an Org Chart Leaves Out
- Shadow decision-makers. The person with the final say often isn't the one with the title. An executive assistant, a trusted adviser, or a long-tenured specialist may carry more influence than their position suggests.
- Cross-functional dependencies. Critical work happens between the boxes, in the handoffs, collaborations, and informal agreements that org charts can't capture.
- History. A leader who seems supportive may have championed a similar initiative that failed. Past relationships shape present ones.
- Information flows. Who talks to whom? Where do ideas start, and how do they travel? The official channels rarely tell the whole story.
The Four Layers of an Organizational Map
Build the map in layers. Each layer uses its own set of relationship labels, so you can read one layer at a time.
1. Formal Structure
Start with the org chart: "reports to," "manages," "sits on committee with." This layer is the easiest to confirm, and it gives every later observation somewhere to attach.
2. Informal Influence
Record who listens to whom: "trusted by," "mentored by," "defers to," "rivals with." These relationships come from meetings, interviews, and who gets copied on what.
3. Information Flow
Record how news and requests move: "briefs," "consults," "escalates to." Look for the people who pass information between groups, and for the groups nobody briefs.
4. Work Dependencies
Add the processes and handoffs between teams: "approves," "depends on," "hands off to." Use Process cards for workflows such as budget approval or month-end close, and connect the teams that feed them.
How to Map an Organization
Step 1: Lay Down the Formal Structure
- Add cards for the people and teams in scope
- Draw the formal reporting relationships
- Mark these strings Confirmed and set their source to the org chart
Step 2: Add What You Observe
- Add new people as you meet them
- Note who introduced you to whom. Referral chains show trust networks
- Track who defers to whom in meetings
- Record informal relationships that people mention, with the source and date
Step 3: Rate How Sure You Are
Mark each connection Confirmed (documentary evidence or direct observation), Suspected (a single source or a reasonable inference), or Uncertain (speculation or an unverified claim). This keeps assumptions visibly separate from facts.
Step 4: Analyze the Map
Step back and look for these patterns:
- Hubs - Cards with many strings. These people are often busier and more influential than their title suggests.
- Brokers - People who connect two groups that otherwise do not talk. If one leaves, the groups lose touch.
- Bottlenecks - A person or process that many workflows pass through.
- Silos - Clusters with few strings to the rest of the map.
- Gaps - Teams you have not talked to yet, and relationships you still need to confirm.
Step 5: Keep It Current
Organizations change with every hire, departure, and reorganization. Update the map after each meeting while the detail is fresh, and note when a relationship changes rather than deleting the old one.
This observation-based method suits one person or a small team. Organizational network analysis (ONA) is a formal version that builds the map from surveys or communication data across a whole organization.
Who Uses Organizational Mapping?
Consultants
A new engagement starts with an organization you do not know. Mapping each meeting onto a board shows, within the first weeks, who holds the decisions and which relationships a recommendation has to travel through.
New Leaders
A manager who joins or moves into a new division inherits relationships nobody writes down. A map of the first round of conversations shows who to talk to next and whose support matters.
Transformation and Integration Teams
Mergers, reorganizations, and system changes cut across teams. A map of the current dependencies shows which handoffs a change will break before it breaks them.
Analysts and Researchers
Anyone studying how an organization makes decisions, from a journalist to an academic researcher, needs the same map of formal lines, influence, and sources.
Example: Mapping an Integration at Meridian Financial
Here is a made-up engagement to show how a board fills in over a first week. The company and the people are invented.
Say a bank we will call Meridian Financial hires you to help integrate a recently acquired wealth management firm. The official project sponsor is the Chief Integration Officer, but after a week of meetings the board shows a more complex picture:
The People
- Sandra Chen (Chief Integration Officer) - Your formal sponsor. Hired 18 months ago specifically for acquisitions. Hasn't led an integration this size before. Eager for the project to succeed.
- Marcus Webb (CFO) - Controls the integration budget. Sandra nominally reports to the CEO, but Marcus approved the budget and attends all steering meetings. Note: "Sandra defers to Marcus on resource decisions."
- Diana Torres (Head of Wealth Management) - Runs the acquiring division. Her team will absorb the acquisition. She's been with Meridian for 22 years and knows the history behind every decision.
- James Okonkwo (CEO of acquired firm) - Staying on for 12 months as "Strategic Advisor." Your read: he's skeptical the acquisition will preserve his firm's culture. Influential with his former team.
- Rachel Park (Diana's Chief of Staff) - Not on the org chart, but everyone copies her on emails and she's in every meeting. She appears to be Diana's gatekeeper and trusted adviser.
The Connections That Matter
- Marcus → Sandra: "controls budget" - Confirmed. You've seen it in meetings.
- Diana → Rachel: "trusts, consults" - Suspected. Rachel speaks and Diana listens, but you haven't confirmed their history.
- James → acquired team: "loyalty, informal authority" - Confirmed. His former employees still treat him as the leader.
- Diana ↔ James: "respectful but wary" - Suspected. They're polite in meetings, but neither has visited the other's office.
What the Map Shows
The integration depends on the Diana and James relationship, and your sponsor Sandra has no direct connection to either of them. Rachel is a broker: the likely route into Diana's inner circle. None of this is on the org chart, and it sets the approach for the rest of the engagement. From here, a stakeholder map of the integration itself would rank these people by power and interest.
Keep Organizational Maps Private
An organizational map records informal power, who trusts whom, and observations that could do damage if they leaked. Cloud-based tools put that data on servers you do not control.
Local files keep organizational maps on your machine, with no account or cloud sync. Optional AI analysis sends the board and your Gemini key to Google, so leave it off for sensitive work.
AI Analysis of an Organizational Map
Once the board has some depth, Redstrings Pro can send it to Google Gemini with your own API key and ask questions about it. Built-in prompts include Analyze Structure, Find Gaps, Key Players and Key Insights. You can also write your own: which people form a tight group, who is connected to the project on paper but to nobody on the board, or what a one-page summary of a given person would say. Answers can be saved as reports inside the board.
The board content and the key go straight to Google. No Redstrings server sits in between, and nothing is sent unless you run an analysis.
Organizational Mapping in Redstrings
Redstrings supports each layer of the map:
- Built-in card types - Person, Team, and Process cards for people, groups, and workflows; Artifact cards for the documents behind a decision
- Labeled strings - "reports to," "trusted by," "briefs," "depends on"
- Confidence levels - Set each string to Confirmed, Suspected, or Uncertain
- Source tracking - Record where each piece of information came from
- Local files - Boards live on your machine. Optional AI analysis sends the board to Google with your own Gemini key.
- Case files and boards - Use a separate case file for each organization and separate boards for divisions or layers
- Export to Markdown - Generate a report of every card and relationship
Download Redstrings free and map the organization behind the org chart.