Organizational Network Analysis¶
Method — instantiates Informal Structure Mapping
Builds a graph of advice, trust, information, and collaboration ties from relationship data, then analyzes its structure to expose brokers, isolates, and structural holes.
Organizational Network Analysis (ONA) treats the organization as a graph and reasons about its shape. From relationship data — surveys, rosters, or communication traces — it constructs the ties along which advice, trust, information, and collaboration actually flow, then runs structural analysis over the whole graph: who sits at the center, who bridges otherwise-disconnected clusters, who is isolated, and where the structural holes are that a needed conversation falls into. Its defining move is aggregate and quantitative: it does not tell you who any one person is or what they mean to the organization; it tells you how the topology is built and which positions in it carry structural load. Because relationship data is inherently sensitive, protecting it is part of the method, not an afterthought.
Example¶
Two engineering companies merge and, on paper, become one 900-person organization with unified teams. Leadership wants to know whether the two halves are actually integrating or just co-located. ONA sends a bounded roster survey to everyone: from this list, who do you go to for technical advice? who do you share information with weekly? The responses build a combined advice graph. Its structure is stark: the two legacy organizations form two dense clusters that touch at only three edges — three people carry nearly all cross-org advice. Meanwhile a cluster of twenty acquired-side specialists shows up as near-isolates, connected to the merged whole by a single thread.
The analysis names the structural features without naming the humans in public: three overloaded brokers holding the merger together, a structural hole between the specialists and everyone else, and a fragility no reorganization chart would reveal. The results circulate as anonymized, team-level aggregates; the raw who-named-whom data never leaves a protected diagnostic view. That structural picture is what tells leadership the integration is one bus-accident away from splitting back in two.
How it works¶
What distinguishes ONA is that it computes structure over the graph rather than reading any single relationship:
- Define the tie types precisely — advice, trust, information, collaboration are different networks and must not be collapsed into one "connection."
- Collect relationship data through a bounded roster survey (or, carefully, from communication traces), so ties are reported rather than inferred from titles.
- Compute structural metrics — centrality, betweenness, cluster detection — to surface brokers, isolates, and structural holes as positions in the graph.
- Aggregate and anonymize before sharing, so the output is a map of the network's shape, not a leaderboard of individuals.
Tuning parameters¶
- Tie definition — which relationship the survey asks about. Advice networks, trust networks, and information networks have different shapes; asking a vague question yields a meaningless blend.
- Roster boundary — who is in the survey frame. Too narrow and the key external broker vanishes; too wide and response rates collapse.
- Centrality metric — degree, betweenness, or eigenvector; each foregrounds a different kind of structural importance and can crown a different node.
- Response-rate threshold — how complete the survey must be before the graph is trusted, since missing respondents create phantom holes.
- Aggregation / anonymization level — individual, team, or department reporting. Coarser aggregation protects people but can hide the single critical broker.
When it helps, and when it misleads¶
Its strength is that it quantifies structure the eye cannot see across hundreds of people, and its most valuable finding is usually a structural hole — a gap between two clusters that ought to be talking and aren't[1] — or the overloaded broker bridging it. It turns "the two teams don't seem integrated" into a measured, locatable claim.
Its central caution is that a tie is a proxy: reported advice-frequency is not the same as trust, authority, or value, and an absent edge is ambiguous — healthy independence or a missing necessary link, the graph alone cannot say. The classic misuse is turning a network map into an instrument for ranking or surveilling individuals, or running it backwards to justify a reorganization already chosen. The discipline that guards against this is the confidentiality safeguard the method builds in — aggregate and anonymize before anyone reads it — and treating every structural finding as a hypothesis to confirm with the people in it, never as a verdict about them.
How it implements the components¶
ONA fills the graph-structural slice of the archetype:
informal_network_map— its primary output: the graph of advice, trust, information, and collaboration ties, built from relationship data rather than reporting lines.broker_or_bottleneck_node— structural metrics surface the brokers bridging clusters and the isolates cut off from them, as positions in the graph.confidentiality_safeguard— anonymized, aggregated reporting is part of the method because raw who-named-whom data is sensitive by nature.
It reasons about topology, not people or practice: it does not profile any single informal_leader_profile or trace an individual's influence_path — that person-level work is Informal Leader Mapping — and it never watches work happen, so it produces neither the actual_practice_trace nor the formal_informal_gap_diagnosis of Workflow Ethnography.
Related¶
- Instantiates: Informal Structure Mapping — supplies the structural map of the informal network the intervention reasons over.
- Sibling mechanisms: Actual-vs-Documented Process Map · Informal Leader Mapping · Process Mining Review · Shadow Process Audit · Workaround Review · Workflow Ethnography · Communication Pattern Review
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Organizational Network Analysis operates as an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution because it builds a graph of advice, trust, information, and collaboration ties from relationship data, then analyzes its structure to expose brokers, isolates, and structural holes.
Independent corroboration: The frozen evidence defines Organizational Network Analysis as 'Builds a graph of advice, trust, information, and collaboration ties from relationship data, then analyzes its structure to expose brokers, isolates, and structural holes', so its operative form is Analysis, Modeling & Optimization.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Sociology & Anthropology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Organizational Network Analysis is most directly rooted in sociology and anthropology's study of institutions, social structure, culture, and situated collective life. The lineage fits its defining practice: Builds a graph of advice, trust, information, and collaboration ties from relationship data, then analyzes its structure to expose brokers, isolates, and structural holes.
Related originating lineages:
- Data Science & Analytics — Organizational Network Analysis also draws materially on data science and analytics' computational practice of modeling, monitoring, validation, and pattern extraction, which shaped this mechanism rather than merely adopting it as an application.
- Organizational & Management Science — Organizational Network Analysis also draws materially on organizational and management science's practice of coordinating people, authority, strategy, knowledge, and work, which shaped this mechanism rather than merely adopting it as an application.
Review resolution: Both independent reviews agree on primary origin sociology_anthropology; reconciliation resolves alternate_origin_disagreement, domain_reach_disagreement. Formative alternate lineages retained: data_science, organizational_management. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis records how the formative lineages relate. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=false preserves the reviewers' boundary judgment.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
ONA finds the structural broker — the graph position bridging two clusters. Whether that position is held by a trusted, competent person or an accidental gatekeeper is a question the graph cannot answer; that is why its output is best handed to Informal Leader Mapping, which profiles the human occupying the node.
References¶
[1] Burt, R. S. Structural Holes: The Social Structure of Competition (1992). Harvard University Press. Defines a structural hole as the absence of a connection between actors with complementary resources or information. registry ↩