Organizational Network Analysis

What is Organizational Network Analysis?

Organizational network analysis (ONA) is a method for mapping and measuring the informal relationships and information flows between people and teams, revealing how work actually gets done beyond the formal org chart.

Updated November 2026 · 5 min read


The org chart shows who reports to whom, but it says little about how work actually happens. In practice, people go to trusted colleagues for advice, rely on a few connectors to get things done across departments and avoid certain teams because working with them is slow. These informal networks often matter more to performance than the formal structure. Organizational network analysis makes them visible. By mapping who communicates with whom, who people go to for information and where collaboration breaks down, it shows leaders the real shape of their organization.

Network analysis has roots in sociology, including Jacob Moreno's sociograms in the 1930s, and was brought into management practice by researchers such as Rob Cross, whose work showed how a small number of people often carry a disproportionate share of collaboration. Organizational network analysis now uses surveys and, increasingly, passive data from email, calendars and collaboration tools to map relationships at scale. For organization designers, HR and people analytics teams, change leaders and executives, it provides a view of the organization that no reporting line can show.

Definition of Organizational Network Analysis

Organizational network analysis is a structured method for collecting data on relationships, such as communication, collaboration, advice and trust, among people or groups, then using network mapping and metrics to identify patterns, key individuals, bottlenecks, silos and opportunities to improve how the organization works.

It complements the formal view in an org chart, is a common technique in people analytics and informs organizational design decisions.

Data Collection Methods

Active ONA uses surveys asking people whom they go to for information, advice, decisions or support.

Passive ONA analyzes metadata from email, calendars, chat and collaboration tools to see communication patterns, usually without reading content.

Many organizations combine both, using passive data for scale and surveys for the quality and purpose of relationships.

Privacy safeguards, such as aggregation, consent and limits on individual reporting, are essential with either method.

Key Network Roles and Metrics

Central connectors are people many others rely on, often essential to getting work done and at risk of overload.

Brokers connect otherwise separate groups, carrying information across boundaries.

Peripheral people have few connections, which may signal new joiners, isolated experts or disengagement. New joiners who stay peripheral after several months are at higher risk of leaving, which makes onboarding a common use of network data.

Network metrics include centrality, density within groups and the strength of connections between groups. Patterns over time matter too, since a team whose external connections are shrinking may be becoming isolated.

Importance of Organizational Network Analysis in Workforce and Operations

ONA reveals how work really flows. It shows where collaboration happens and where it is missing, which helps target improvements.

It identifies critical people. Central connectors and brokers often hold knowledge and relationships that the organization would struggle to replace.

It also supports change and integration. Mapping networks helps leaders spot influencers who can spread change and gaps that need bridging after a merger or reorganization. Research by Rob Cross and colleagues found that a small share of employees often accounts for a large share of valuable collaboration, which makes those people both critical and at risk of burnout.

Organizational Network Analysis and Financial Management

Identifying collaboration overload helps reduce time lost to excessive meetings and requests, which carries a real cost in productivity.

Knowing which people are central to key processes helps target retention spending where losing someone would be most costly.

Network data can inform where to place shared resources and how to size teams, avoiding duplicated effort.

Measuring collaboration before and after a reorganization shows whether the change delivered the intended benefits.

Common Challenges

Employees may see passive data collection as surveillance, damaging trust if it is not handled transparently.

Network maps can be misread, for example by treating highly connected people as high performers when they may simply be overloaded.

Survey-based ONA depends on high response rates, since missing responses leave gaps in the network.

Insights can be hard to act on without clear ownership and follow-up. Networks also change quickly, so a single snapshot may not reflect how the organization works a year later.

How to Conduct Organizational Network Analysis

Conducting organizational network analysis involves defining the business question, choosing data sources, collecting data with privacy safeguards, analyzing the network and acting on the findings.

ONA is most useful when it addresses a specific question, such as improving collaboration between two units, rather than mapping everything.

Planning and Collecting

Define the question, such as how well product and sales teams collaborate or who will be most critical in an upcoming change.

Choose active, passive or combined data collection, and agree privacy rules with legal, HR and employee representatives.

Communicate the purpose and safeguards to employees before collecting data.

Collect data for the relevant population and time period, aiming for high participation in surveys. Keep surveys short, with a few questions about the relationships that matter most for the question being asked.

Analyzing and Acting

Map the network and calculate key metrics, looking for connectors, brokers, silos and overloaded individuals. Compare the network map with the formal structure to see where informal connections compensate for gaps in the organizational structure.

Validate findings with leaders and employees, since context often explains patterns in the data. A person who looks isolated may be a specialist whose work is meant to be focused, while a dense cluster may reflect a team that works well together.

Act on the insights, for example by redistributing work from overloaded people, creating forums between disconnected teams or involving key influencers in change efforts. Repeat the analysis after six to twelve months to see whether the changes had the intended effect.

Examples of Organizational Network Analysis in Practice

The examples below show organizational network analysis in practice.

Both use illustrative figures. The first reduces overload, and the second supports a merger.

In each, the network revealed what the org chart could not.

Reducing Overload

An engineering organization's survey-based ONA finds that 5% of engineers receive more than a third of all requests for help.

Several of these engineers report burnout, and two have recently left.

The organization documents common answers, creates an internal help forum and rotates support duties, and requests to the most central engineers fall by about 40%. Their contributions are also recognized formally in performance reviews, which they had previously felt were overlooked.

Supporting a Merger

Two merged consulting firms map collaboration networks six months after the deal and find almost no connections between their industry practices.

Leaders create joint client teams and cross-firm communities of practice led by people identified as brokers. They also pair partners from each firm on major accounts, giving client teams a reason to work together.

A year later, cross-firm connections have grown sharply, and joint client proposals are increasing.

Conclusion

Organizational network analysis maps the informal relationships and information flows between people and teams, showing how work actually gets done. It uses surveys, collaboration data or both, and identifies connectors, brokers, silos and overload.

In workforce and operations, ONA reveals how work flows, identifies critical people and supports change. Starting with a clear question, protecting privacy, validating findings with the people involved and acting on the insights help organizations use network analysis well.