The org chart is a legal and administrative document. It describes reporting relationships for HR purposes: who approves time off, who writes performance reviews, who has hiring authority. It does not describe how work actually gets done, how decisions are actually made, or how information actually flows.
This distinction is not academic. For PE firms conducting due diligence, for boards evaluating organizational health, and for CEOs trying to understand why execution is slowing, the gap between the formal org chart and the real organizational network is the single richest source of operational insight available.
The Org Chart's Assumptions (and Why They Are Wrong)
The formal org chart makes three assumptions that behavioral data consistently disproves.
- Assumption 1: Information flows through reporting lines — The org chart assumes that a directive from the CEO reaches the front line by cascading through VPs, directors, managers, and team leads. In reality, information flows through the paths of least resistance. A Slack message from the CEO reaches the entire organization in minutes, bypassing every reporting layer. A critical technical decision flows from one senior engineer to another across departments, never touching a manager. The reporting line is the official path. The communication network is the actual path.
- Assumption 2: Decision authority maps to hierarchy — The org chart implies that a VP has more decision authority than a director, who has more than a manager. In practice, decision authority concentrates around individuals with information, expertise, and trust — which may or may not correlate with title. A senior product manager with deep customer knowledge and the CEO's trust may have more effective decision authority than the VP of Product whose direct reports go around them for decisions.
- Assumption 3: Teams are the primary unit of collaboration — The org chart groups people into teams within departments. In reality, the primary unit of collaboration is often the informal working group: the three people from different departments who always end up solving cross-functional problems together. These working groups are invisible on the org chart but drive a disproportionate share of the organization's output.
What the Real Organization Looks Like
Mapping communication patterns across an organization reveals a structure that is both more complex and more informative than the org chart.
The Communication Network
When you visualize every communication relationship in an organization — who messages whom, how frequently, across what channels — you see the real organizational structure. It typically reveals several patterns:
- Informal hubs — Individuals who are not in management roles but sit at the center of communication networks. They are the people others go to for answers, context, and problem-solving. They may be a senior engineer who understands every system, an operations coordinator who knows every process, or a project manager who bridges every department. These informal hubs are often the most valuable and most vulnerable people in the organization.
- Shadow hierarchies — Communication paths that bypass the formal hierarchy. The CEO communicates directly with a team lead three levels down because that is where the critical information lives. A VP of Sales communicates more with the VP of Engineering than with their own direct reports because cross-functional coordination is their primary value-add. The shadow hierarchy describes who actually influences decisions, and it frequently diverges from the official hierarchy.
- Structural holes — Gaps in the communication network where two groups that should be connected are not. Engineering and customer success operate independently. Sales and product do not communicate directly. Finance and operations coordinate only through the CEO. These structural holes create information latency, duplicated effort, and misaligned priorities.
- Clusters and boundaries — Natural groupings of intense collaboration that may or may not align with department boundaries. Sometimes the most cohesive cluster is not a team but a cross-functional group working on a specific initiative. Sometimes a single team on the org chart is actually two sub-clusters with minimal internal communication.
Why This Matters for Due Diligence
The gap between the org chart and the real organization contains critical information for deal teams.
- Key person risk is hidden in the network — The org chart says the VP of Engineering is the technical leader. The communication network may reveal that a senior engineer three levels below the VP is the actual technical hub — the person everyone goes to for architecture decisions, code reviews, and troubleshooting. If that person leaves post-acquisition, the technical capability degrades regardless of whether the VP stays.
- Management effectiveness is visible — A manager who appears on the org chart as leading a team of 12 may, in the communication data, show minimal interaction with half their team. Their "span of control" on paper is 12. Their effective span is 6. The other 6 people are operating without meaningful management, which shows up as execution inconsistency and engagement divergence.
- Integration compatibility is assessable — When two companies are merging, comparing their organizational networks (not their org charts) reveals compatibility or conflict. Two companies that are both hierarchically organized will integrate differently than two companies with distributed network structures. A hierarchical company acquiring a flat one creates specific, predictable friction points that the org chart comparison would never surface.
- Organizational resilience is quantifiable — A company whose communication network is distributed and redundant (multiple paths between any two groups) is more resilient than one with a star topology (everything routes through one person). The org chart cannot distinguish between these structures. The communication network makes the distinction obvious.
Case in Point: What We Typically Find
Across hundreds of organizational analyses, several patterns appear with striking consistency.
- The org chart leader vs. the network leader — In roughly 60% of companies, the person with the highest communication centrality (the most connected, most active node in the network) is not the CEO or any C-suite member. It is a middle manager, a senior IC, or an operations role that the org chart does not flag as critical.
- The phantom department — At least one department on the org chart functions as two or more separate units in practice. The most common example: a "product" department where the product managers for different product lines have virtually no communication with each other. The org chart says "product team." The network says "three independent product groups that share nothing but a VP."
- The missing bridge — At least one critical cross-functional connection is missing or dangerously thin. The most common gap: engineering and customer success. Product and sales. Finance and operations. These are functions that need to coordinate closely but whose communication network shows minimal direct interaction.
- The overloaded node — At least one individual is carrying an unsustainable communication load — handling 3-5x the cross-functional communication volume of their peers. This person is typically not a formal leader. They are an organizational glue human who fills structural gaps the org chart creates. They are also the person most likely to burn out and leave, which would create an outsized disruption.
How to Map Your Real Organization
Building an accurate picture of the real organization requires behavioral data, not surveys.
- Communication analysis — Map all communication relationships (email, messaging, collaborative documents) by frequency, reciprocity, and cross-functional breadth. This produces the organizational network graph.
- Decision flow tracing — Track how decisions move through the organization: who initiates, who is consulted, who approves, who executes. This reveals the actual authority structure.
- Collaboration clustering — Identify natural working groups by analyzing which individuals consistently collaborate on shared projects, documents, and workflows. This reveals the real team structure.
- Centrality scoring — Calculate the communication centrality of every individual in the organization. The resulting ranking identifies the informal hubs, the overloaded nodes, and the structural vulnerabilities.
The output is not a replacement for the org chart — the org chart serves administrative purposes that the network analysis does not. The output is a companion diagnostic that reveals the operating reality behind the organizational fiction.
For PE deal teams, this means understanding what they are actually buying — not the structure on the management presentation slide, but the living system that produces the financial results. For CEOs, it means seeing their organization as it actually functions — which is the prerequisite for changing it deliberately rather than accidentally.
