Archive note:
Originally published on LinkedIn on July 21, 2025. This article is preserved here as part of the evolution of our thinking on Organizational Network Analysis, organizational behavior, and the layered relationship between formal structure, trust, influence, and the networks through which organizations actually function.

Every organization tells itself a story.

There’s the org chart: boxes, lines, hierarchies. There are the values painted on walls and repeated in onboarding sessions. There are goals, KPIs, roles, and rituals.

But beneath the visible surface lies the lived reality of how people actually behave, relate, and decide. That reality isn’t flat - it’s layered. And navigating those layers without the right lens is like trying to map ocean currents with a magnifying glass.

This is where Organizational Network Analysis (ONA) enters - not as another HR fad, but as a structural microscope. ONA doesn’t measure what people say they value; it reveals how those values live - or vanish - through relationships.

Let’s peel back the layers.

Layer One: The Formal Layer – Structure, but Not Substance

Most leadership teams manage what they can see: the formal design of their organization. Who reports to whom. What each department does. Job descriptions and policies. It’s the most visible and most comforting layer - because it looks like control.

Mintzberg (1979) called this the "structural configuration" - necessary, but insufficient. Formal structures give clarity but rarely explain performance.

In practice, teams with flawless organizational charts often collapse under pressure - not because the structure is wrong, but because it ignores the second layer.

Layer Two: The Cognitive Layer – Mental Maps and Invisible Rules

Every employee builds a mental map of the organization: who has power, who can be trusted, who gets things done. These perceptions shape behavior more than any policy manual.

Karl Weick (1995) argued that organizations are sense-making systems. And that sense-making is relational - built through ongoing interaction, not static charts.

ONA captures this by asking: Who do you go to for advice? Whose opinion do you trust when making a difficult call? These are indicators of perceived influence and cognitive centrality. When these patterns contradict formal leadership, dysfunction brews.

Layer Three: The Emotional Layer – Trust, Safety, and Psychological Load

Trust isn’t a soft metric - it’s infrastructure. Without it, collaboration falters, innovation dies, and people retreat into silence.

Amy Edmondson (1999) introduced psychological safety as the belief that one can take interpersonal risks without fear. High-performing teams don’t just tolerate questions - they amplify them.

ONA tracks this layer by mapping who people turn to in moments of stress, conflict, or confusion. When critical roles - like emotional anchors or silent brokers - go unsupported, burnout spreads quietly. And voice shuts down.

Milliken et al. (2003) found that 85% of employees withhold input not out of laziness, but fear. ONA makes that fear visible - so it can be addressed.

Layer Four: The Network Layer – Where It All Comes Together

Here lies the real terrain.

The network layer isn’t just a metaphor - it’s the structural DNA of how organizations live or stagnate. It’s where cognition, emotion, and formal intention collide.

ONA doesn’t just visualize relationships. It quantifies them:

  • Betweenness centrality reveals bottlenecks.

  • Degree centrality shows visibility.

  • Clustering highlights silos.

  • Effective size maps innovative potential.

Rob Cross & Parker (2004) showed that 20–35% of value-added collaboration in most companies comes from just 3–5% of employees. Lose them, and you lose leverage.

ONA is the only method that empirically shows who holds the network together - and what happens when they’re gone.

What Happens When You Ignore the Layers

Here’s what I’ve seen in real organizations:

  • Teams with great KPIs - but zero trust - implode after minor conflict.

  • Managers shocked by sudden resignations - never realizing that their “star” was an emotional sponge for the whole team.

  • New structures rolled out with enthusiasm - but failing because old informal networks reasserted themselves like gravity.

In each case, the organization managed the surface - but missed the layers underneath.

ONA would have told a different story. A deeper one.

Designing for Depth: What Leaders Can Do Now

Building organizational resilience isn’t about adding more process - it’s about revealing and reinforcing the relationships that sustain performance under pressure. Leaders who design with depth don’t chase visibility. They cultivate connection.

  1. Map influence, not just roles. Titles don’t build trust - people do. Go beyond the org chart and identify those who carry the real weight of decision-making, advice, and mentorship. These are the “invisible load-bearers.” If you don’t know who they are, you’re already vulnerable.

  2. Detect silos before they calcify. Don’t wait for a reorg to learn that your marketing team doesn’t talk to product team. ONA reveals which units operate in isolation - and which individuals could become bridges with the right support. Silos are never just structural; they’re relational fractures.

  3. Reinforce emotional infrastructure. Organizations celebrate high performers but rarely invest in the emotional stabilizers: the colleague everyone vents to, the one who remembers birthdays, the one people turn to during uncertainty. These “relational shock absorbers” quietly prevent collapse. Recognize them. Protect them.

  4. Pair data with design. Use what the network reveals to shape real interventions-mentoring programs, onboarding pairings, knowledge transfer plans, even crisis communication maps. ONA doesn’t just diagnose problems. It guides how to (re)design systems that can bend without breaking.

This isn’t about surveillance. It’s about stewardship. If the goal is to build organizations that adapt and endure, then leaders must stop designing for appearance - and start designing for connection.

From Topography to Topology

Most organizations manage their topography: the landscape they can see.

But true insight comes from topology: the shape of relationships that flex, strain, and reshape the system every day.

ONA is the lens that brings that shape into view.

And in a world where trust breaks faster, change moves quicker, and silence spreads deeper -organizations can’t afford to manage just what’s visible.

They need to navigate the layers.

References

Edmondson, A. (1999). Psychological safety and learning behavior in work teams.

Weick, K. (1995). Sensemaking in organizations.

Mintzberg, H. (1979). The structuring of organizations.

Milliken, F., Morrison, E., & Hewlin, P. (2003). An exploratory study of employee silence.

Cross, R., & Parker, A. (2004). The hidden power of social networks.

Kahn, R. L., Wolfe, D. M., Quinn, R. P., Snoek, J. D., & Rosenthal, R. A. (1964). Organizational stress: Studies in role conflict and ambiguity.

Burt, R. S. (1992). Structural holes: The social structure of competition.