Use case
Organizational network analysis
Organizational network analysis (ONA) maps how work actually flows between people, as opposed to the reporting lines on an org chart. It shows the informal experts everyone goes to, the bottlenecks everything waits on, and the teams that never talk to each other.
Updated · Netgraf
What ONA finds
| Pattern | What it looks like | Measure |
|---|---|---|
| Hidden expert | Many people go to them for advice | Degree on advice ties |
| Bottleneck | One person links two teams | Betweenness, cut points |
| Silo | Teams with dense ties inside and few across | Communities |
| Overloaded hub | The network runs through one manager | Centralization |
| Peripheral newcomer | Few ties, all within one team | Degree, closeness |
How to run a small ONA
- Pick one question per network: "Whom do you go to for advice on X?" or "Whom do you work with weekly?"
- Survey everyone in scope, allowing up to five names each.
- Build an edge list (person, named person) and import it.
- Add each person's team as the subtitle so the groups are readable.
- Colour the map by group in Insights and compare the groups found with the teams on the org chart. Where they differ is the finding.
Krackhardt's classic study of a small firm found that the person with the most advice ties was not the person with the most power; the kite is a textbook reduction of exactly that problem.