Pick any company of a thousand people or more and pull the official organizational chart. Now ask the top fifty people inside that company a different question: when something urgent breaks, who do you actually call. Map the answers. You will produce a second diagram that bears only a loose relationship to the first. The boxes are in different places. Some of the lines are missing. Other lines run sideways across boundaries that the org chart treats as sealed. A handful of people are central to the second diagram who are junior or invisible on the first.
This is not a sign of dysfunction. It is how every large organization actually operates. The formal structure describes accountability. The informal network describes where work gets done. Both exist. Most executives spend their careers managing the first and ignoring the second, which is why the second tends to quietly determine most of what matters.
The research on this is older than most operators realize. Rob Cross and colleagues have been mapping organizational networks since the late 1990s. The pattern is consistent across companies, industries, and geographies: a small number of people (typically three to five percent of headcount) account for a disproportionate share of information flow, cross-functional connection, and informal decision facilitation.
- In a study of 23 large organizations, the top 3 to 5 percent of employees were responsible for 25 to 35 percent of value-added collaboration (Cross, Rebele, Grant, Harvard Business Review).
- Only half of these high-connectivity individuals held titles that would have predicted their role in the network.
- Companies in the top quartile for informal network health showed 6 to 8 percent higher revenue growth than peers with similar formal structures, per McKinsey Organizational Health Index data.
The person in the center of the right-hand diagram is the one the company cannot function without. They are probably not on the executive team. They are probably not in line for a promotion in the next twelve months. And when they leave (and they do leave, because companies that run on informal networks exhaust the people at the center of those networks), the first symptom is not a vacancy. It is a slow degradation of cross-functional execution that nobody connects to their departure.
Why accurate org charts are a bad sign
The received wisdom is that a well-designed organization is one where the formal structure matches the actual work. This is wrong in a specific and important way. The formal structure is an approximation. Reality does not sit still long enough to be fully captured by a diagram that is refreshed twice a year. An organization where the formal chart and the informal network are identical is an organization where nothing cross-functional is happening.
Put differently: when the org chart is accurate, the organization is inert. Real companies produce work that cuts across functions, geographies, and levels. That cross-cutting work is what the informal network is for. If the org chart describes all of it, the company is either very small, very mechanical, or not actually doing much.
What you want is not alignment between the two diagrams. What you want is awareness of the gap between them, and a set of management practices that make the gap productive rather than destructive.
The gap between the two quartiles is larger than most structural interventions will ever produce. It is larger than the typical return on a reorganization, larger than the productivity gain from most technology deployments, larger than the lift from the kind of cultural initiatives that executives usually spend money on.
An organization where the formal chart and the informal network are identical is an organization where nothing cross-functional is happening.
The management implication
Once you accept that the real business runs on a network that is not documented, the management question changes. It is no longer "how do we design the right structure." It becomes "how do we see the structure we actually have, and how do we manage it without destroying it."
A few things follow. The first is that periodic network mapping stops being an HR curiosity and becomes a basic diagnostic, of the same order as a financial close. If you cannot name the ten people in your company whose departure would measurably disrupt execution, you are flying blind. The second is that retention strategy needs to be informed by network position, not just by level or performance rating. Losing a senior VP is painful but visible. Losing a mid-level program manager who sits at the center of three product lines is catastrophic and invisible. The third is that reorganizations (which are the default executive response to almost any structural problem) are more dangerous than they appear. A reorg does not just move boxes. It severs edges in the informal network, and those edges take years to rebuild.
The best operators treat the informal network as a first-class asset. They know who sits at its center. They invest in those people deliberately. They route information flow through them rather than around them. And when they make structural decisions, they make them with the network map in front of them, not just the org chart.
The org chart is a document. The network is the business. Managing one while ignoring the other is not a strategy. It is a misunderstanding about where the company actually is.