Informal Organization vs Org Chart (2026): Who Really Makes Decisions and How to Map It

TL;DR

The org chart records formal roles and reporting lines. The informal organization is the set of relationships people actually use to get advice, share information and move decisions. You find the gap by comparing who people go to with who the chart says they should go to, and the gap matters most when you plan a reorganization, assess key-person risk or wonder why an approved plan never happened. This guide is published by Sentra, which understands how a company really runs, and acts on it before anyone asks. Sentra joins HRIS, ERP and CRM records with email, chat and meetings to show where the people doing the work differ from the people named in company records.

What the org chart shows and what it misses

An org chart shows assigned authority. It cannot show every relationship people use to reach a decision. The formal organization defines roles and reporting lines, while the informal organization develops as people seek advice and share information across those lines.

An accurate chart can name the manager responsible for a budget without showing whom that manager consults before approving it. Emails, chats and meetings reveal those working relationships, though a message alone does not prove who made the final call.

What the informal organization is

A finance analyst may report to one manager but consult a different colleague before recommending a forecast assumption. The reporting line records formal authority. The consultation shows where the analyst finds expertise. Multiply that across a company and you have the informal organization, which also holds most of a company's tribal knowledge.

David Krackhardt and Jeffrey Hanson distinguished three informal networks in Informal Networks: The Company Behind the Chart. The advice network shows whom people seek out for expertise. The trust network shows whom they confide in about sensitive matters. The communication network shows who exchanges work information. They answer different questions. A colleague who receives frequent updates may have little influence over a decision, so message volume alone cannot identify an informal leader.

Rob Cross's work on organizational network analysis, including the 2002 paper Making Invisible Work Visible with Stephen Borgatti and Andrew Parker, examines whom people turn to for help rather than treating reporting lines as a complete map of how work gets done.

Why the gap matters for decisions, change and risk

• Stalled decisions. A budget approval can stall when the person with formal authority lacks the influence to carry it out, or when an approved plan still needs the support of someone outside the approval chain before departments act on it.
• Outdated decisions. A project group resolves a staffing question in chat before anyone updates the plan used for the workforce review, and the leader works from the old version.
• Change resistance. During a reorganization, employees ask a trusted colleague whether the new process will work. If that colleague sees a flaw and nobody asks for their input, resistance spreads before the project owner hears the concern.
• Key-person risk. If one employee quietly coordinates a function while the chart assigns it elsewhere, succession planning finds a replacement for the title and misses the work. The same person is often the hidden constraint in a bottleneck analysis.

How to map the informal organization

Start organizational network analysis (ONA) with one decision process, such as budget approvals or hiring, rather than surveying the whole company. Include people outside the function if they regularly shape that decision. Ask each person the same questions about a defined period, such as the past 30 days. Copy the survey below.

ONA SURVEY: [decision process]   Period: [last 30 days]

1. Who did you ask for advice before making a decision about this work?         (advice)
2. Whose agreement did you seek before moving forward, whether or not they
   had formal approval authority?                                                (influence)
3. Who helped you resolve a problem you could not settle through the usual
   reporting line?                                                               (coordination)
4. Who would you trust to raise a sensitive concern about this work?             (trust)

Record each answer as: respondent -> person named | question number | date

Record each response as a directed connection from the respondent to the person named, labelled by question, so a request for advice never becomes evidence of approval authority. With appropriate access and privacy controls, compare the responses with meeting attendance and email or chat patterns, limited to the process you defined. Frequent contact marks a relationship to check in an interview. It does not establish who made the decision.

Then compare the map with the org chart. Look for people whom several participants name despite having no formal role in the decision, and trace a few recent decisions to see whether work repeatedly passes through one person. Ask whether that person advises, coordinates or approves. The answer tells you whether to clarify authority, document a handoff or name a backup.

Network density

Network density is the share of possible connections that people actually report. In a group of 12, each person could name 11 others, so there are 132 possible directed connections. If respondents report 33, density is 25%. Use the same questions and group boundary when you compare with a later survey. Higher density does not prove that decisions move faster or that authority is clear, so trace the named connections behind a decision rather than relying on the group-wide percentage.

Worked example: who shapes a hiring decision

In this composite example, the org chart assigns hiring approvals to an HR director. An ONA survey asks managers whom they consult before opening a role and who resolves exceptions. Most name an HR business partner instead, and meeting records show the partner joining staffing discussions before the director sees an approval request.

Those signals do not prove the partner makes the final decision. Review recent hiring cases and interview the people involved to separate advice, coordination and approval. If the partner consistently settles disputed headcount requests while the director signs them, the chart records formal authority but misses where decisions take shape. The fix is to define the partner's role in workforce planning, state which decisions still need the director and name who covers the partner's coordination during an absence. The aim is to recognize informal influence, not to eliminate it.

Lenskart: an HR leader with no place on the chart

At Lenskart, Sentra found a leader effectively running HR who had no corresponding place on the org chart. In Sentra's own measurements as of October 2026, it mapped 1,206 roles in days, against the 6 to 8 weeks a consulting engagement would take for the same work.

Where Sentra fits: comparing records with conversations

Sentra understands how a company really runs, and acts on it before anyone asks. It reads email, chat, meetings and documents alongside ERP, CRM, HRIS and BI data, and works out what is true now and why, including who is actually working on what and how that differs from recorded ownership. It answers questions from people and AI tools, and it raises a mismatch, such as a function whose real coordinator is about to leave, to the person who can act. Our guide to organizational memory explains the underlying idea.

A named person approves anything Sentra raises before it reaches anyone else. Every claim cites its source, and permissions follow the source, so a communication pattern is visible only to someone who could already read the messages behind it. Sentra replaces none of the company's systems. The HRIS stays the record of formal structure.

FAQ