---
name: hr-organization-network-analysis
description: Help org design and workforce analytics teams analyze informal collaboration networks to surface hidden influencers, bottlenecks, and silos beyond the formal org chart. Use when asked to "run an organizational network analysis", "identify hidden influencers", "find collaboration bottlenecks", "map informal networks", or "analyze who really drives collaboration in this team".
metadata:
  author: Tuan Duc Tran
  version: "1.0.0"
---

# Organizational network analysis

Analyze informal collaboration patterns — communication flows, cross-team connections, and influence networks — to surface dynamics the formal org chart doesn't show, from hidden influencers to silent bottlenecks and silos.

## Supported tasks

- Designing an organizational network analysis (ONA) study and data approach
- Identifying informal influencers and connectors not reflected in the org chart
- Detecting collaboration bottlenecks where too much flow depends on one person
- Mapping silos and weak cross-team connections that limit collaboration
- Analyzing network health before and after a reorganization
- Identifying flight risk based on network centrality and disengagement signals
- Assessing onboarding network integration for new hires
- Designing interventions to strengthen weak but strategically important connections
- Using ONA to inform succession planning beyond formal hierarchy
- Communicating ONA findings sensitively, respecting privacy and trust
- Comparing network structure across teams, functions, or locations
- Tracking network changes over time to measure the effect of interventions

## Key prompts

### Study design

1. "Design an organizational network analysis study for [team/function], including data sources and privacy safeguards."
2. "What data sources (survey, calendar, communication metadata) are appropriate and proportionate for an ONA in [context]?"
3. "Draft a consent and privacy framework for running an ONA that respects employee trust."
4. "How do we communicate the purpose of an ONA to employees so it doesn't feel like covert surveillance?"

### Identifying patterns

1. "Analyze this network data to identify informal influencers or connectors who aren't reflected in the formal org chart."
2. "Where are the collaboration bottlenecks in [team] — points where too much flow depends on one person?"
3. "Identify silos or weak connections between [team A] and [team B] that could be limiting collaboration."
4. "Which roles show signs of being overloaded network hubs at risk of burnout or single-point-of-failure attrition?"

### Applying findings

1. "How might network centrality data inform succession planning for [role], beyond what the formal hierarchy suggests?"
2. "Design an onboarding approach that helps new hires build network connections faster in their first 90 days."
3. "Recommend interventions to strengthen a strategically important but currently weak connection between [team A] and [team B]."
4. "How should network analysis findings be shared with leaders without exposing individual employees to unwanted attention?"

### Measuring change

1. "Compare network structure for [team] before and after [reorganization/intervention] and summarize what changed."
2. "Design a way to track network health over time without turning it into a surveillance exercise."
3. "What is a reasonable cadence for re-running an ONA so it captures real change without becoming intrusive routine monitoring?"
4. "How do we present a before/after network comparison in a way non-technical leaders can act on?"

## Tips

- Be transparent about what data is collected and why — ONA can feel invasive if employees don't understand or consent to the analysis.
- Focus on patterns and roles, not individual surveillance; findings should inform structural decisions, not target specific people.
- Validate network findings with qualitative context — a high-centrality node isn't always a good thing; it can also signal an overloaded bottleneck.
- Use ONA to complement, not replace, formal org design and succession planning — informal network data adds a dimension the org chart misses, it doesn't override it.
- Re-run analysis after major interventions (reorgs, team changes) to check whether the intended structural changes actually happened in practice.