Every company has two org charts. The first is the official one, the one on paper: boxes and lines showing who reports to whom, who is in charge of what. The second is invisible and far more important: the map of how work actually flows, who talks to whom, who people turn to when they have a problem, where information really passes. These two maps rarely coincide — and it is in the second, the informal one, that most of what happens in an organization is decided. Organizational network analysis, or ONA, is the technique that makes that invisible map visible, using data to reveal how the company works beneath the official structure.
The idea behind ONA is simple and powerful: instead of looking at the formal hierarchy, you look at the real connections between people. Who collaborates with whom, who seeks advice from whom, where knowledge circulates. These connections form a network, and that network tells a story about the organization the official org chart hides. It is an often surprising story, revealing anonymous heroes, hidden bottlenecks and isolated islands nobody knew existed.
This article is about what ONA reveals, why that matters for management, and about the essential care of using it to support people rather than to surveil them.
The official org chart lies (by omission)
The formal org chart describes authority, but not reality. It says who has the power to decide, but not who has the actual influence; it shows the reporting lines, but not the channels through which information and help really flow. In a real company, much of the work happens through relationships that appear in no box: the person in one department everyone informally consults, the collaboration between two teams that officially have nothing to do with each other, the veteran the new hires turn to instead of following the official channel.
This divergence is not a defect; it is the natural way organizations work. The problem is that, when management only sees the official org chart, it makes decisions blind to half of reality. It reorganizes teams without knowing it is cutting a critical collaboration link; it promotes by hierarchy without seeing who is really influential; it looks for the problem in the wrong place because the map it consults does not show where work really jams. ONA exists to correct this blindness.
What ONA reveals
By mapping the real connections, ONA makes visible patterns that would otherwise remain hidden, and some of them are of enormous value for managing the organization. Each pattern tells something management would need to know and usually does not.
- The hidden connectors: people who, despite not having a top job, link many parts of the organization and are crucial for the flow of information — losing them would be far more serious than the org chart suggests.
- The bottlenecks: points everything has to pass through, that slow the organization and overload some people while creating dangerous dependence.
- The isolated islands: teams or people disconnected from the rest, who neither receive nor share knowledge, and whose contribution is lost for lack of connection.
- The cross-silo collaboration: whether the different areas really communicate or live in separate worlds, despite the org chart placing them side by side.
The data behind the network
ONA builds the network map from data about interactions. These can come from surveys — asking people who they collaborate with and who they turn to for different things — which is the most direct and transparent way. Or they can come, with much more care, from metadata of work systems: patterns of who communicates with whom, without looking at the content of the communications. From this data, the network of connections is drawn and its properties analyzed, revealing the informal structure that was hidden in plain sight.
It is important to stress that the value of ONA is in the aggregate patterns, not in spying on individuals. The goal is to understand how the organization as a whole is connected — where the bottlenecks, the islands, the connectors are — not to surveil what each person does. This distinction is not only ethical; it is also what makes ONA useful, because the value is in the overall picture, not in individual policing.
The essential care: support, not surveil
No data technique about people demands more responsibility than ONA, because none touches so closely on privacy and trust. Mapping who each person talks to can easily feel like surveillance, and the moment employees feel network analysis serves to control them, the very trust the organization depends on is destroyed — and people adjust their behavior, making the data useless as well as toxic. Poorly used ONA does not just fail; it does active harm.
That is why responsible ONA rests on non-negotiable principles: transparency about what is being analyzed and why; a focus on aggregate patterns, not individuals; anonymization whenever possible; and a clear purpose of supporting people — relieving those who are overloaded, connecting those who are isolated, valuing the connectors the hierarchy ignores. Used this way, ONA is a tool in the service of people; used as surveillance, it is a betrayal that costs dearly.
A concrete case
A company noticed that one of its departments seemed strangely slow to execute projects, despite having competent people and enough resources. By the org chart, everything looked well structured, and management could not figure out where the problem was. They decided to do an organizational network analysis, with full transparency to employees about the purpose — to understand and improve the flow of work, not to evaluate people. The map that emerged was revealing. They found that almost all the information and all the decisions of that department passed through a single person — not the formal boss, but a veteran everyone, informally, turned to for everything. That person was an extraordinary and valuable connector, but had become, without anyone noticing, a bottleneck: nothing moved without passing through them, and they were overloaded far beyond what their job suggested. The org chart would never show this, because the person was not at the top of the hierarchy. With this clarity, the company acted: they distributed part of the knowledge and decisions concentrated in that person, recognized and valued their connector role, and relieved their load. The department visibly sped up, not because resources were added, but because a bottleneck only ONA had managed to reveal was undone. The difference came from finally seeing how work really flowed.
Managing the real organization, not the paper one
The greatest value of ONA is reminding us of a truth traditional management forgets: organizations are networks of people, not boxes in a diagram. Decisions that ignore this network — reorganizations that cut vital links, promotions that ignore the real influencers, change efforts that do not go through the right connectors — fail by managing an organization that only exists on paper. ONA gives management back the ability to see and work with the real organization, the one that actually produces the work.
This does not mean throwing away the formal org chart, which still has its function. It means complementing it with the view of the informal, and recognizing that many of the most powerful levers for improving an organization lie precisely in that invisible layer ONA illuminates.
In practice
If you feel your organization has flow problems — slow decisions, information that does not circulate, silos that do not communicate, people overloaded for no apparent reason — the cause may be in the informal network the org chart does not show. An organizational network analysis, done with transparency and in the service of people, can reveal the connectors, the bottlenecks and the islands shaping performance without anyone seeing them. Do you know your company's real org chart — the one of how work actually flows — or only the official one, the one on paper?
