Organizational Network Analysis (ONA)

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.

What Is Organizational Network Analysis?

Key Takeaways

  • ONA maps how people actually communicate and collaborate, revealing the informal networks that no org chart captures.
  • It identifies key connectors (people who bridge different teams), bottlenecks (people who are overwhelmed because too many workflows pass through them), and isolated individuals or groups.
  • ONA uses data from email metadata, calendar invitations, messaging platforms, and sometimes surveys to build network graphs of organizational relationships.
  • The method doesn't read message content. It analyzes patterns: who communicates with whom, how frequently, and in which direction.
  • Organizations use ONA for post-merger integration, reorg planning, identifying informal leaders, detecting collaboration overload, and improving knowledge flow.

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.

50%Of collaboration in most organizations happens outside formal reporting lines (Connected Commons, 2024)
3.5xMore likely to identify burnout risk in central network nodes before it shows in surveys (Microsoft, 2024)
35%Of employees flagged as "low performers" by managers are actually critical connectors invisible on the org chart (Deloitte, 2024)
28%Average improvement in post-merger integration speed when ONA guides team restructuring (McKinsey, 2024)

Key ONA Concepts and Metrics

ONA uses specific network science terms to describe organizational dynamics. These are the ones HR leaders need to understand.

MetricWhat It MeasuresWhy It Matters for HR
Degree centralityNumber of connections a person hasIdentifies highly connected individuals who may be overloaded or are informal hubs
Betweenness centralityHow often a person sits on the shortest path between two othersReveals brokers and bottlenecks: people who control information flow between groups
Closeness centralityHow quickly a person can reach everyone else in the networkFlags potential change champions who can spread information efficiently
Network densityRatio of actual connections to possible connections within a groupIndicates team cohesion. Too low means silos. Too high may mean groupthink
Bridging tiesConnections that link otherwise disconnected groupsCritical for cross-functional innovation and knowledge transfer
Isolation scoreHow disconnected a person or team is from the broader networkIdentifies onboarding failures, disengaged employees, or siloed teams

Where ONA Data Comes From

ONA can be conducted using active methods (surveys) or passive methods (communication metadata). Most modern implementations combine both.

Passive ONA (digital exhaust)

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 (survey-based)

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.

Combining approaches

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.

How Organizations Use ONA

ONA has specific, high-impact applications across several HR and business challenges.

Post-merger integration

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.

Reorg planning

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.

Identifying hidden leaders

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.

Detecting burnout risk

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.

Privacy and Ethics in ONA

ONA involves analyzing employee communication patterns, which raises legitimate privacy concerns. Getting this right is essential for trust and legal compliance.

What ONA should and shouldn't access

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.

Transparency and consent

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.

Aggregation and anonymization

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.

ONA Tools and Platforms

The market for ONA tools has grown significantly as remote work made understanding collaboration patterns more critical.

  • Microsoft Viva Insights: Built into Microsoft 365, provides passive ONA using Outlook and Teams metadata. The most accessible option for organizations already in the Microsoft ecosystem. Offers both individual and organizational-level network analytics.
  • Humanyze: A dedicated ONA platform that analyzes email, calendar, and (optionally) proximity sensor data. Strong on workplace design and collaboration optimization research.
  • TrustSphere: Focuses on relationship analytics from email and calendar metadata. Used for M&A integration, org design, and succession planning.
  • Polinode: Combines active (survey-based) and passive (integration-based) ONA in a single platform. Good for organizations that want both approaches.
  • Innovisor: Specializes in active ONA using targeted survey methodology. Strong consulting layer on top of the analytics.

ONA Adoption and Impact Statistics [2026]

Data on how organizations are using network analysis to inform talent and organizational decisions.

39%
Of Fortune 500 companies use some form of ONA in their people analytics practiceInsight222, 2025
3.1x
More accurate identification of flight risk when ONA is combined with traditional attrition modelsDeloitte, 2024
25%
Reduction in post-reorg productivity dips when ONA informs the restructuring designMcKinsey, 2024
47%
Of HR leaders say understanding informal networks is a top priority for 2026Gartner, 2025

Frequently Asked Questions

Does ONA read the content of emails and messages?

No. Properly implemented ONA analyzes metadata only: who communicated with whom, when, and how often. It doesn't read message content, subject lines, or attachments. This distinction is critical for privacy compliance and employee trust. Any ONA implementation that analyzes content has gone beyond network analysis into surveillance, which is a different practice with very different ethical and legal implications.

How accurate is passive ONA?

Passive ONA captures a large portion of digital collaboration but misses face-to-face conversations, phone calls (unless logged), and ad-hoc hallway discussions. In highly remote organizations, passive ONA is quite accurate because most communication is digital. In hybrid and in-person environments, it captures 60% to 80% of collaboration patterns. Supplementing with active surveys fills the gaps.

Can ONA be used for performance management?

It shouldn't be used directly for performance ratings or disciplinary action. Using ONA punitively ("your network is too small, so your rating is lower") destroys trust and can lead to employees gaming the system by sending unnecessary emails. ONA should inform development conversations and organizational decisions, not individual performance scores. The power of ONA is in understanding system-level dynamics, not judging individual behavior.

How often should ONA be conducted?

Passive ONA can run continuously since it's automated. Active (survey-based) ONA is typically done annually or semi-annually to avoid survey fatigue. Event-driven ONA (during a merger, reorg, or major change) should be conducted before and after the event to measure impact. For most organizations, continuous passive monitoring with semi-annual active deep dives is the right cadence.

What's the biggest insight ONA typically reveals?

The most common (and most valuable) finding is the identification of critical connectors who don't appear on the org chart. Nearly every ONA project discovers individuals who are central to how the organization actually functions but have no formal authority or recognition for that role. These people are often mid-level employees who've been with the company for several years and serve as bridges between teams. When they leave, the impact on collaboration is disproportionate to their title.

Is ONA legal under GDPR?

It can be, with proper safeguards. GDPR requires a lawful basis for processing personal data. For ONA, legitimate interest is the most common basis, supported by a Data Protection Impact Assessment (DPIA). Key requirements: use only metadata, be transparent with employees about the analysis, aggregate results wherever possible, limit access to results, and have a clear purpose that benefits the organization and its employees. Consult with legal counsel in your specific jurisdiction before implementing.
Adithyan RKWritten by Adithyan RK
Surya N
Fact-checked by Surya N
Published on: 25 Mar 2026Last updated:
Share: