Middle Management as Bridge Nodes: The Layer Where Innovation Flow Actually Breaks

• The Layer Most Often Mischaracterised
• Bridge Nodes: A Structural Definition
• How Bridge Work Surfaces in the Interviews
• Three Bridge Functions: Connector, Translator, Buffer
• The Nordic Dimension
• Five Diagnostic Questions for the Bridge Layer
• Structural Responses: Investing in the Bridge Architecture
• From Layer to Architecture

Why the layer most often blamed for organisational inertia is structurally the layer holding innovation flow together — and what the Bridgium research with 28 innovation leaders reveals about the bridge function, the conditions that sustain it, and the conditions that break it.

The Layer Most Often Mischaracterised

Gallup’s State of the Global Workplace research attributes 70 percent of the variance in team engagement to the manager (Gallup, 2024). McKinsey research on flatter organisational designs documents an average 12 percent reduction in middle management roles across large enterprises between 2022 and 2024 (McKinsey, 2023). The conventional reading places these two findings in tension: managers explain most of the variance in team performance, yet organisations are systematically thinning the layer that contains them.

The tension dissolves when the function of middle management is read structurally rather than hierarchically. The Bridgium research with 28 innovation leaders across Nordic and European enterprises (September to December 2025) consistently identifies middle managers not as a delivery layer but as a bridge layer: the structural position where innovation flow either travels across organisational boundaries or stops travelling. Ronald Burt’s framework on Structural Holes (1992) provides the most precise vocabulary for what is happening at this layer. The middle manager who matters for innovation flow is not the manager who delivers fastest. It is the manager who bridges between groups that would otherwise not communicate.

This reading does not romanticise middle management. The Bridgium interviews are equally clear on where the bridge function fails, why it is structurally invisible to performance systems, and what happens when it does break. The diagnostic question this article addresses is structural: what bridge functions does middle management perform in the innovation flow, what conditions make them possible, and what conditions cause them to disappear.

“People are very good at their own roles, but innovation usually sits between functions — and that space is not owned by anyone.”
— People & Business Developer · Financial Services · Finland

The Bridgium framework names that ownerless space the Ownership Void. The middle layer is the structural place where the Ownership Void is either bridged or widened. Which one happens depends less on the talent of individual managers than on the architecture in which they operate.

Bridge Nodes: A Structural Definition

In Burt’s network theory (1992), a structural hole exists wherever two parts of an organisation have something to learn from each other but lack the relational ties to do so. Bridge nodes are the people who span those holes. The economic value of a bridge node is not in the work they personally produce. It is in the information, sensemaking, and trust that travels through them — and would not travel otherwise.

Granovetter’s prior work on the strength of weak ties (1973) established that the most useful information in organisations travels through acquaintances rather than close colleagues, because close colleagues already share the same information. Middle managers are structurally positioned to hold the largest portfolio of weak ties in the organisation: by virtue of role tenure they know the people above and below, and by virtue of cross-functional exposure they know the peers laterally.

Floyd and Wooldridge (1996), in their foundational work on strategic middle management, made a related argument: middle managers perform four distinct strategic functions — championing initiatives, synthesising information, facilitating adaptability, and implementing deliberate strategy. The Bridgium research finds that all four of these functions, in innovation contexts specifically, depend on the bridge architecture: they only happen if the middle manager is structurally connected across functions, not only vertically inside one.

The Bridgium framework maps this onto the three stages of innovation flow. Each stage requires bridge work, and each requires a different kind.

The bridge function is not concentrated at any single stage. It is the cross-cutting infrastructure on which all three stages depend. This is why the middle layer is not a delivery layer in the innovation context. It is the connective tissue.

How Bridge Work Surfaces in the Interviews

Across the 28 Bridgium interviews, descriptions of bridge work were the most frequently recurring pattern in the data — more frequent than any single stage-specific theme. Innovation leaders described the moment an innovation flow worked as the moment a specific person carried it across a functional boundary. They also described stalls and disappearances as the moment a specific bridge person moved roles, left, or ran out of attention.

“The biggest struggle is not the idea itself, but knowing who needs to be convinced.”
— Innovation & Sales Leader · Technology & Enterprise Services · Finland

This observation describes the Connector function precisely. The information cost of an innovation initiative is not concentrated in formulating the idea. It is concentrated in mapping the relational topology of the organisation: who needs to hear it, in what order, with what framing, with which prior context. That mapping work is performed by specific people, in specific bridge positions, and it is rarely visible in the formal description of their role.

Three Bridge Functions: Connector, Translator, Buffer

The 28 interviews surfaced three distinguishable bridge functions. A single middle manager may perform one, two, or all three at different times. Distinguishing them matters because each rests on different conditions and breaks under different pressures.

1. Connector. Maintains relational ties across organisational silos. Carries weak-tie information, brokers introductions, holds the map of who works on what. The Connector function depends directly on the Connectivity condition: it requires sustained low-cost informal contact across functions. Microsoft’s Work Trend Index (2023) documented that hybrid workers report 24 percent fewer meaningful cross-team interactions per week than office-based equivalents. The Connector function is structurally vulnerable to this contraction because most of the relational maintenance it performs is invisible and unscheduled.
2. Translator. Converts between functional languages and incentive systems. An R&D pilot result must be translated into business unit language before a business unit leader can absorb it. A frontline observation must be translated into formal pipeline language before it can become a funded initiative. The Translator function depends on dual fluency: the manager must understand both the source and destination logic. Kerr’s classic finding (1975) — that organisations reliably reward A while hoping for B — is operationally addressed at this layer. The Translator is the person who notices that the KPI architecture rewards a behaviour incompatible with the innovation flow, and negotiates a translation. This work rarely appears on a performance review.
3. Buffer. Absorbs ambiguity from above so that teams below can keep delivering. When upper-level reorganisations, strategy changes, or budget pressures arrive, the Buffer middle manager translates these into a stable set of priorities for their team. Hochschild’s work on emotional labour (1983) provides the closest theoretical anchor: the work consists in managing the emotional and informational environment of others, not in producing visible output. The Buffer function is structurally vulnerable to burnout because its work product is, by definition, the absence of disruption — and absences are not visible in performance systems.

Why the Bridge Function Is Invisible to Performance Systems

Mintzberg’s foundational study of managerial work (1973) established that managers spend the majority of their working hours on activities that produce no formal output: brief conversations, informal information exchange, network maintenance, and interpersonal sensemaking. Five decades later, the underlying performance architecture in most enterprises still measures the activities that produce formal output — projects, decisions, deliverables — and treats the surrounding 70 to 80 percent of managerial time as administrative overhead.

This produces a systematic measurement gap. The bridge functions described above account for most of what makes innovation flow possible across boundaries. They also account for almost nothing in standard performance reporting. The Bridgium framework identifies this as a structural form of Invisible Work: not work that is hidden by intention, but work that the measurement architecture cannot register.

The cognitive cost of bridge work is also systematically underestimated. Mark’s research at the University of California, Irvine (2023) found that knowledge workers experience an average 23-minute recovery period after each cognitive interruption. Leroy’s work on attention residue (2009) showed that the quality of subsequent work is impaired even when individuals believe they have transitioned. Bridge managers operate in continuously interrupted attention — Microsoft’s Work Trend Index (2023) recorded an average of 77 daily message and email checks among knowledge workers, with knowledge work fragmented into intervals averaging three minutes between context switches. The cumulative cognitive cost of bridge work, performed in this interrupted environment, is substantial and unrecognised.

“Innovation without recognition becomes invisible work.”
— CEO · IT Services · Finland

The Ownership Void at the Stage 2 to Stage 3 handover is the most consequential consequence of this invisibility. When the bridge work that would carry a pilot into business unit adoption is unowned in the formal architecture, it gets done — or fails to get done — depending on whether a specific middle manager has the relational and cognitive capacity to do it. When that specific person moves, leaves, or runs out of attention, the pilot quietly stops travelling. The Bridgium interviews repeatedly describe this pattern in the same words: the pilot did not fail, it simply disappeared.

The Nordic Dimension

Nordic enterprises operate with structurally flatter hierarchies than most global comparators. Finnish luottamus (trust as institutional precondition), Swedish samförstånd (consensus through dialogue), and Norwegian-Danish dugnad (collective contribution) all support a working culture in which middle managers have less unilateral authority and more relational influence. In Burt’s terms, the Nordic middle manager operates with weaker formal hierarchy and proportionally stronger reliance on bridge function.

This is a strength for innovation flow. Bridge work is easier in cultural environments that already treat peer-to-peer translation as the default mode of work. The Nordic middle manager is, on average, more practised at the Connector and Translator functions than counterparts in more hierarchical systems.

It is also a particular vulnerability. Janteloven and equivalent norms across the Nordics make it culturally awkward to recognise individual bridge contribution publicly. Bridge work is performed; bridge work is not celebrated. This compounds the structural invisibility problem: not only do performance systems fail to register bridge contribution, the cultural environment further discourages making it visible. The Bridgium interviews recorded multiple instances of senior leaders describing critical bridge people whose contribution became apparent only when they moved roles and the pilot they had been carrying stopped moving.

“Then it goes back to the business units… and that’s usually where things slow down.”
— Innovation Partnerships Lead · Energy · Finland

The phrase “it goes back” identifies the structural moment of bridge dependency. Whether the innovation continues to travel at this point depends on whether a specific middle manager in the business unit performs the bridge work. In Nordic enterprises, the cultural strength makes this more likely to happen quietly. The structural fragility makes it equally likely to stop quietly when one person moves.

Five Diagnostic Questions for the Bridge Layer

The Bridgium framework approaches the middle management layer not as a population to thin or expand, but as an architecture to make visible. The questions below test the visibility of bridge function in current operating systems.

Three or more warning signals in this diagnostic predicts a Connectivity-condition deficit in the innovation flow architecture. The deficit is rarely visible in standard organisational health surveys, because survey instruments measure individual sentiment rather than network density. It is visible in flow metrics: declining articulation rates, increasing fragmentation tax, and rising adoption gap.

Structural Responses: Investing in the Bridge Architecture

The Bridgium framework treats the middle management layer as architectural infrastructure for innovation flow. The structural responses below are organised by bridge function and frame the work as architecture investment rather than as personal development.

The common pattern across all three responses is recognition architecture. Bridge work that is invisible to the performance system will, over time, be performed less, performed by exhausted people, or performed by people who leave because their contribution is unrecognised. The Bridgium framework treats recognition not as a motivational lever but as a structural signal: the act of measuring bridge work is itself what makes it sustainable. This is the operational meaning of the Legitimacy condition at the middle layer.

MIT Sloan research (Reeves et al., 2023) found that organisations that sequenced transformations with explicit middle-layer sensemaking phases achieved 2.4 times higher sustained adoption rates than those that compressed those phases. Deloitte’s 2024 Human Capital Trends report similarly identified that 76 percent of organisations believe they have significant untapped workforce potential, while only 14 percent have structural mechanisms for surfacing it. The middle layer is the structural mechanism in question. Making its bridge work visible is the prerequisite condition for everything that follows.

From Layer to Architecture

The conventional debate over middle management asks whether the layer should be larger or smaller. The Bridgium research suggests this is the wrong question. The right question is what bridge architecture the organisation requires for innovation to flow, what conditions sustain that architecture, and how it can be made visible to the systems that currently overlook it.

The Connector, Translator, and Buffer functions are not personality traits. They are structural positions that someone occupies, with greater or lesser support from the surrounding architecture. The middle managers who perform these functions well are not exceptional individuals. They are people operating in conditions that make the functions possible: protected time, dual-fluency development, recognition for relational and translation work, distributed ambiguity load.

Organisations that thin the middle layer without first mapping the bridge architecture remove the connective tissue of their own innovation flow. Organisations that map the architecture first, identify where bridge work concentrates, and invest in the conditions that sustain it, find that the layer they thought was overhead was the structural mechanism for everything else they were trying to achieve.

This reframe — from layer to architecture — is the most consequential adjustment available to enterprises trying to make their innovation flow visible. It costs little to make. It costs substantially more to discover after the fact, when the bridge nodes have already moved on.

Continue with the Bridgium Framework

→ Full Bridgium Report (28 interviews, complete framework):
bridgium-research.eu/innovation-report-2026/
→ Self-evaluation checklist mapping current innovation flow architecture:
bridgium-research.eu/innovation-checklist-2026/
→ The Innovation Flow newsletter, bi-weekly:
https://www.linkedin.com/newsletters/the-innovation-flow-7292805307267743744/

References

1. Berger, P. L., & Luckmann, T. (1966). The Social Construction of Reality: A Treatise in the Sociology of Knowledge. Penguin Books.
2. Burt, R. S. (1992). Structural Holes: The Social Structure of Competition. Harvard University Press.
3. Floyd, S. W., & Wooldridge, B. (1996). The Strategic Middle Manager: How to Create and Sustain Competitive Advantage. Jossey-Bass.
4. Granovetter, M. S. (1973). The Strength of Weak Ties. American Journal of Sociology, 78(6), 1360–1380.

Hochschild, A. R. (1983). The Managed Heart: Commercialization of Human Feeling. University of California Press.

5. Kanter, R. M. (1983). The Change Masters: Innovation and Entrepreneurship in the American Corporation. Simon & Schuster.
6. Kerr, S. (1975). On the folly of rewarding A, while hoping for B. Academy of Management Journal, 18(4), 769–783.
7. Leroy, S. (2009). Why is it so hard to do my work? The challenge of attention residue when switching between work tasks. Organizational Behavior and Human Decision Processes, 109(2), 168–181.
8. Mark, G. (2023). Attention Span: A Groundbreaking Way to Restore Balance, Happiness and Productivity. Hanover Square Press.
9. Mintzberg, H. (1973). The Nature of Managerial Work. Harper & Row.
10. Gallup (2024). State of the Global Workplace Report — Manager Variance in Team Engagement. Gallup Inc.
11. McKinsey & Company (2023). The State of Organizations 2023: Ten Shifts Transforming Organizations. McKinsey Global Institute.
12. Microsoft (2023). Will AI Fix Work? — 2023 Work Trend Index Annual Report. Microsoft.
13. MIT Sloan Management Review (Reeves, M., Whitaker, K., & Job, A., 2023). Sequenced Transformation: Why Order Matters in Enterprise Change Programmes. MIT Sloan.