Organizational Network Analysis (ONA)

Theory & origin

ONA descends from sociometry (Moreno, 1930s) and graph theory, and was brought into management practice by researchers like David Krackhardt and Rob Cross, whose The Hidden Power of Social Networks made the case that collaboration patterns are measurable and manageable. The method is simple to state: gather tie data, either by survey ("who do you go to for advice, decisions, energy") or from passive metadata like email and calendar traffic, build the graph, and compute the standard measures: centrality, betweenness, density. The value is in the patterns those numbers surface. A central connector carrying half the information flow. A broker who is the only bridge between two departments. A bottleneck where every approval queues. A cluster with no outside ties. New hires floating unconnected at the periphery. Two cautions define responsible use. Passive-data ONA is employee monitoring and needs every one of its four gates, and network position must never feed performance ratings, because the moment it does, people game their ties and the map stops being true.

Key components

The parts at a glance. Click any term for the full definition, a field example, and the common failure, in the model below.

How a consultant runs it

1. 01 Choose the question before the tool: retention risk, silo integration, change adoption, or post-merger wiring. A network map without a question is wall art.
2. 02 Pick the data source with the monitoring gates in mind. Surveys are consented and rich but small. Passive metadata scales, and needs the full privacy treatment.
3. 03 Compute the boring numbers, then read for the five patterns worth money: connectors, brokers, bottlenecks, peripheries, and silos.
4. 04 Protect the connectors before you celebrate them. Their burnout is the most expensive attrition event you have not priced.
5. 05 Rewire deliberately: delegate the bottleneck's authority, give every peripheral hire named connections, and build real ties across silos before issuing collaboration mandates.

Worked example

A multifinance risk division of 140 people keeps missing its credit-approval SLA despite two process redesigns. The ONA survey maps 1,240 working ties and finds the real process: 68% of approval paths run through one senior analyst who was never given authority, only trust. Two silo clusters, including the acquired portfolio team with three external ties, and 22% of recent hires sitting peripheral complete the picture. The fix is wiring, not another process: the analyst gets formal delegation and a deputy, the portfolio silo gets two rotation embeds, and every new hire gets three named connections in month one. The SLA recovers within a quarter, and the analyst, who turns out to have been two months from quitting under invisible overload, stays.

Common pitfalls

1. 01 Mapping without a question, which produces a beautiful poster and no decision
2. 02 Skipping the privacy gates on passive data, which converts a diagnostic into a scandal
3. 03 Letting network position leak into ratings, which teaches everyone to perform their ties
4. 04 Treating one snapshot as permanent. Networks drift, and last year's map is last year's organization.
5. 05 Celebrating connectors with more work instead of protecting them from it

Sample deliverable

One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.