A method that maps and measures how information, collaboration, and influence flow through an organization by analyzing communication patterns, meeting data, and relationship networks to reveal the informal structures that actually drive how work gets done, often uncovering dynamics invisible on the org chart.
Key Takeaways
Your org chart says one thing. Reality says another. The org chart shows clean reporting lines and tidy department boundaries. But the actual work happens through informal networks: the engineer who everyone asks for help, the project manager who connects three teams that never formally interact, the senior leader whose calendar is so packed with cross-functional meetings that they've become a bottleneck for every decision. ONA makes these invisible patterns visible. It takes metadata from communication tools (not message content, just who communicated with whom and how often) and builds a network map of the organization. The result looks like a web of connected dots, where clusters, bridges, and isolated nodes reveal dynamics that surveys and manager reports miss entirely. This matters because organizational decisions, especially restructuring, leadership development, and change management, are often made based on the formal hierarchy. But if you restructure without understanding the informal network, you might accidentally sever critical collaboration pathways, overload key connectors, or isolate teams that depend on informal bridges to function.
ONA uses specific network science terms to describe organizational dynamics. These are the ones HR leaders need to understand.
| Metric | What It Measures | Why It Matters for HR |
|---|---|---|
| Degree centrality | Number of connections a person has | Identifies highly connected individuals who may be overloaded or are informal hubs |
| Betweenness centrality | How often a person sits on the shortest path between two others | Reveals brokers and bottlenecks: people who control information flow between groups |
| Closeness centrality | How quickly a person can reach everyone else in the network | Flags potential change champions who can spread information efficiently |
| Network density | Ratio of actual connections to possible connections within a group | Indicates team cohesion. Too low means silos. Too high may mean groupthink |
| Bridging ties | Connections that link otherwise disconnected groups | Critical for cross-functional innovation and knowledge transfer |
| Isolation score | How disconnected a person or team is from the broader network | Identifies onboarding failures, disengaged employees, or siloed teams |
ONA can be conducted using active methods (surveys) or passive methods (communication metadata). Most modern implementations combine both.
Passive ONA analyzes metadata from communication platforms: email (who sent to whom, when, how often), calendar (meeting attendees, frequency, duration), Slack or Teams (channel membership, direct messages, @mentions), and collaboration tools (shared documents, co-editing patterns). The key point: passive ONA analyzes metadata, not content. It doesn't read your emails. It maps who you communicate with and how often. This is an important distinction for privacy and employee trust.
Active ONA uses short surveys asking employees questions like: "Who do you go to for technical advice?" "Who energizes you at work?" "Who do you depend on to get your work done?" The advantage of active ONA is richer context. You can ask about specific relationship types (advice, trust, energy, decision-making) that metadata can't distinguish. The disadvantage is response bias and survey fatigue. Active ONA works best as a periodic deep dive (annually or semi-annually) supplemented by continuous passive ONA.
The strongest ONA programs use passive data for continuous monitoring and active surveys for periodic deep analysis. Passive data tells you that Maria and Raj communicate frequently. Active data tells you whether that communication is about technical advice, project coordination, or emotional support. The combination gives you both the "what" and the "why" of organizational relationships.
ONA has specific, high-impact applications across several HR and business challenges.
When two companies merge, the formal integration plan connects org charts. ONA reveals which informal networks need to be bridged, which key connectors from each company should be retained, and where collaboration barriers exist between the legacy organizations. Companies that use ONA during M&A integration report 25% to 30% faster cultural blending.
Before restructuring, map the current collaboration network. Identify which cross-team connections are critical for current workflows. Then test proposed reorg structures against the network to predict which connections would break and which new ones need to be built. Reorgs that ignore informal networks often destroy productive collaboration patterns without realizing it.
ONA frequently reveals employees with outsized influence who aren't in formal leadership roles. These central connectors are often the people who train newcomers, resolve conflicts, and bridge knowledge gaps between teams. They're high-value employees who rarely show up in succession planning because they don't have impressive titles. ONA makes them visible.
Employees with extremely high betweenness centrality (everyone's workflow passes through them) are at elevated burnout risk. They can't take vacation without creating bottlenecks. They attend too many meetings. Their role in the informal network is unsustainable. ONA flags these individuals so managers can redistribute workload before burnout occurs.
ONA involves analyzing employee communication patterns, which raises legitimate privacy concerns. Getting this right is essential for trust and legal compliance.
ONA should only use metadata: sender, recipient, timestamp, and platform. It should never analyze message content, subject lines, or attachments. The goal is to understand communication patterns, not to surveil what people say. Any ONA vendor or internal team that accesses message content has crossed an ethical line.
Employees should know that communication metadata is being analyzed, what the purpose is, and what decisions it informs. In GDPR jurisdictions, ONA typically requires a Data Protection Impact Assessment and often explicit consent or a strong legitimate interest justification. Even in jurisdictions without strict consent requirements, transparency builds trust. Secret surveillance destroys it.
Results should be presented at the team or network level, not the individual level, except in cases where specific action is needed (like identifying burnout risk in a key connector). Dashboards accessible to managers should show team-level network health metrics, not individual communication logs. When individual-level insights are used, they should inform support and development conversations, never punitive actions.
The market for ONA tools has grown significantly as remote work made understanding collaboration patterns more critical.
Data on how organizations are using network analysis to inform talent and organizational decisions.