Dismantling structural holes: cross-functional bridging and innovation

A structural hole is a gap between groups that have little contact with each other; research by Ronald Burt found that people who bridge such gaps are more likely to have ideas others rate as good, so organizations that build bridges across functions improve the flow of ideas.

Functions, sites and teams naturally become dense clusters: people talk most with those they work beside. The gaps between clusters are where information stops. This guide explains the research and how to act on it without turning a few brokers into bottlenecks.

A team leans over printed charts and graphs on a meeting table
Photo: Yan Krukau on Pexels

What structural holes are

Burt's theory of structural holes describes networks as clusters joined by a few links. Within a cluster, people share the same information. Across clusters, information differs. A person with ties into several clusters, a broker, sees more varied information and can combine it. In "Structural Holes and Good Ideas" (2004), Burt reported that managers whose networks spanned structural holes were more likely to have their ideas judged valuable.

This builds on Granovetter's earlier finding about the strength of weak ties: casual acquaintances often carry new information that close contacts do not.

Why gaps between functions matter

  • Slow problem-solving. Problems that cross functions wait for escalation through managers.
  • Duplicated work. Teams solve the same problem separately.
  • Missed ideas. Knowledge in one group never meets the need in another.
  • Fragile bridges. When one broker leaves, two groups lose contact.

Finding the holes

A consent-based network survey asking whom people go to for information or advice shows which groups are connected and which are not. Simple measures, such as the share of each team's ties that go outside the team, are usually enough. The output should be a map of groups and the links between them, not a ranking of people. See mapping the informal network.

Ways to build bridges

  1. Cross-functional forums with a real shared problem, not just networking time.
  2. Rotations and secondments that create lasting ties between groups.
  3. Shared roles such as product or program owners who sit between functions.
  4. Spread brokerage. If one person carries every bridge, add more so the link survives turnover and the person is not overloaded.
  5. Structure changes. Where two teams need constant contact, consider the reporting lines and layers; a span and layers check is a starting point.

Cautions

Brokers often carry an invisible load. Recognize it, and make bridging part of roles rather than an unpaid extra. And treat network findings as information about the system: they should never be used to judge individuals. BlissPoint's Workshops and Training can help teams design bridging practices.

Organization Viewer maps the formal structure: the org chart, reporting lines, spans and layers and succession readiness. It does not read email, chat or calendar data and does not run network analysis. Its manager and 360 surveys show peer and direct-report results only for groups of five or more.

Signals of holes without a survey

Before any survey, some signs suggest gaps between groups: the same problem solved twice in different departments, handoffs that routinely stall, escalations that go up one chain and down another to reach a peer team, or new hires who cannot find who knows what. These are prompts to ask the question properly, not evidence on their own.

Checking whether bridges work

Repeat a short network survey after bridging efforts, or track practical outcomes such as time to resolve cross-team issues. Report results at team level. If the same few people still carry every bridge, spread the load further.

Key takeaways

  • Structural holes are gaps between groups where information stops flowing.
  • Burt's research links brokerage across such gaps to better ideas; Granovetter showed weak ties carry new information.
  • Find holes with a consent-based survey analyzed by team, then build several bridges rather than relying on one broker.
  • Recognize bridging work in roles and workloads, and never use network position to judge individuals.

Questions

What is a structural hole?

A gap between two groups in a network that have few or no direct ties, so information does not flow between them.

Who coined the term?

Sociologist Ronald Burt developed the theory of structural holes, including the 2004 study "Structural Holes and Good Ideas."

Is it bad to have one person bridging two teams?

It works but is fragile. If that person leaves or is overloaded, the link breaks. Building several bridges is more resilient.

How do I measure cross-functional ties?

A short voluntary survey asking whom people go to for information, analyzed by team, shows how many ties cross team boundaries.

Do structural holes always need closing?

No. Some separation lets teams focus. The aim is enough bridges for information and ideas to move where the work needs them.

Can structure alone close a hole?

Sometimes. Moving teams under a shared leader or creating a joint role can help, but shared problems and regular contact are what build lasting ties.

Sources

← All relational science and network analysis