A composition of translucent flow lines in deep teal, with one central pathway illuminated brighter than the rest — representing the single coordinating function that keeps the system connected but remains invisible to formal dashboards.

The Invisible Work of Innovation: Why the Most Critical Function Has No KPI

Why performance systems cannot see the work that makes innovation flow possible — and what flow metrics reveal instead

The Pattern in Public Discourse

In the first months of 2026, a pattern emerged in the public conversations of senior leaders across Scandinavian enterprises. Professionals in HR, innovation, and transformation roles began describing their own daily work using a specific and consistent vocabulary: invisible, unrecognised, unmeasured.

Analysis of 23 public posts by C-level leaders in the Nordics during a single week identified two dominant themes: Change Fatigue (~11 mentions) and Invisible Work (~10 mentions). The descriptions were specific and structural: minute-by-minute accounts of days spent context-switching between functions, absorbing emotional tension, maintaining coordination across departments, and performing work that appears on no dashboard and in no performance review.

These public descriptions are not complaints about overwork. They are structural observations about a specific type of work that is essential to organisational functioning and systematically invisible to the systems that measure, recognise, and reward performance.

The Bridgium research with 28 Nordic innovation leaders arrived at the same observation from a different direction — and gave it a name.

The Function the Bridgium Research Identified

The Bridgium framework identifies orchestration as the coordinating function that guides ideas across departmental and stage boundaries without owning or executing all innovation itself. It was introduced by one of the 28 respondents:

“For innovation to work in any organisation, a necessary and sufficient condition is having a central innovation team that orchestrates the process. Without central orchestration — clear rules, criteria, and pathways — innovation initiatives don’t work.”
— Enterprise Product & Transformation Leader · IT Services · Netherlands

Orchestration is distinct from three adjacent functions that organisations routinely confuse with it:

Function What It Does Why It Differs from Orchestration Has Formal KPI?
Innovation Leadership Champions innovation as strategy; secures budget; communicates vision Sponsorship role — operates above the flow, not across transitions Usually yes (budget, pipeline targets)
Project Management Coordinates specific initiatives through stages and deliverables Works inside scope; orchestration works across scopes and interfaces Yes (milestones, budget, timeline)
Ownership Accountable for execution and outcomes of specific innovation Orchestration ensures ownership transfers explicitly but does not absorb it Yes (outcome metrics)
Orchestration Coordinates across boundaries; maintains transitions; protects sensemaking space The connective tissue between all three functions above No. In most enterprises, this function has no formal metric.

The Scale of Invisibility: Research Data

The Bridgium research provides specific evidence for the scale of orchestration’s invisibility across the 28 enterprises studied.

Finding Frequency Across 28 Interviews Implication
Orchestration function exists informally but has no formal job title Mentioned in ~22 of 28 interviews (directly or indirectly) Function present in nearly every enterprise; formally recognised in almost none
Innovation contribution not visible in performance metrics Explicitly raised in 18 of 28 interviews KPI Trap: the system literally cannot see innovation work
Critical knowledge about past pilots and decisions lives in individuals, not systems Described in 15 of 28 interviews Innovation Memory dependent on personal retention; structurally fragile
Departure of a single “bridge person” caused measurable innovation slowdown Specific examples in 9 of 28 interviews Bottleneck vulnerability: orchestration capacity concentrated in single nodes
Innovation teams perceived as disconnected from operational reality by business units Described in 12 of 28 interviews Structural Hole between innovation function and receiving environment

These are not marginal findings. The invisibility of orchestration was one of the most consistent patterns across the entire Bridgium dataset — appearing in every industry, every company size, and every national context studied.

Why Performance Systems Cannot See Orchestration

The invisibility of orchestration is not an accident. It is a structural consequence of how organisational performance systems are designed. Four specific mechanisms produce the gap:

  • Mechanism 1: Output-based measurement. Performance systems are designed to capture deliverables: revenue, throughput, project milestones, efficiency ratios. Orchestration produces no direct deliverable. Its product is the conditions under which other people’s deliverables become possible. Kaplan and Norton’s Balanced Scorecard (1996) — the dominant framework for performance measurement in Nordic enterprises — explicitly measures four dimensions (financial, customer, process, learning). None captures the flow function that connects these dimensions across organisational boundaries.
  • Mechanism 2: Boundary-spanning gap. Orchestration operates at the interfaces between departments, between stages, between innovation and operations. Each interface belongs to a different performance system. The work of connecting them belongs to none. Cross & Parker’s research on organisational networks (2004) documented this precisely: the most valuable positions in networks are the ones that bridge disconnected clusters, but these positions are the least visible to hierarchical measurement systems.
  • Mechanism 3: Informal role absorption. In 22 of 28 Bridgium interviews, orchestration was performed by people whose formal job description said something else — innovation directors, transformation leads, senior HR professionals, chief of staff figures. They perform orchestration work on top of their formal responsibilities, which means the invisible work competes with visible work for the same person’s time. In formal evaluation, the visible work always wins.
  • Mechanism 4: Emotional labour multiplier. Arlie Hochschild’s foundational research (1983) defines emotional labour as the work of managing emotions in the service of organisational goals. The leaders describing their work as “invisible” in public posts are naming exactly this: the emotional cost of translating between functions, absorbing tension, and maintaining cross-boundary relationships. Hochschild’s research demonstrated that emotional labour depletes cognitive resources at a rate comparable to complex analytical work — but unlike analytical work, it is not captured by any performance metric.

What Happens When Orchestration Becomes Visible: The Flow Metrics Approach

The Bridgium framework proposes a specific solution to the measurement gap: flow metrics — indicators that capture whether ideas move across transitions, rather than counting outputs at individual points.

Flow Metric What It Tracks What It Makes Visible Orchestration Dimension
Articulation Rate % of observed problems that reach formal discussion channels Stage 1 health; Silence Tax; whether articulation pathways exist Pathway creation
Stabilisation Rate % of discussed ideas that become shared written concepts within 30 days Stage 2 health; Fragmentation Tax; whether sensemaking space is protected Space protection
Handover Rate % of pilots with explicit ownership transfer, resource allocation, and KPI adjustment Stage 2→3 boundary; Ownership Void; whether handover is architecturally complete Handover management
Integration Rate % of adopted innovations that change operational practice within 6–12 months Stage 3 health; Adoption Gap; gap between “formally adopted” and “actually used” Adoption sustainability

Each of these metrics captures a dimension of orchestration’s output — not as a direct deliverable, but as the conditions for movement. When the articulation rate is high, orchestration is creating pathways. When the stabilisation rate is healthy, orchestration is protecting sensemaking space. When the handover rate is strong, orchestration is managing transitions. When the integration rate is sustained, orchestration is maintaining adoption.

Taken together, these four metrics make the invisible function measurable. They do not require sophisticated tracking systems — they can be estimated through structured interviews, periodic assessment, and cross-comparison of existing data. The most important step is not building infrastructure. It is making the distinction between output metrics and flow metrics explicit.

The Cost of Keeping Orchestration Invisible: Research Evidence

The cost of invisible orchestration is not primarily the orchestrator’s burnout, though that is real and significant. The cost is systemic.

Cost Dimension Mechanism Supporting Research
Single point of failure Orchestration concentrated in one person; departure = capability loss Burt (1992): nodes bridging Structural Holes are disproportionately valuable and vulnerable
Innovation Memory loss Knowledge of prior decisions, attempts, and networks leaves with orchestrator Cohen & Levinthal (1990): Absorptive Capacity depends on accumulated prior knowledge
Burnout of bridge nodes Emotional labour + coordination load + zero recognition = predictable exhaustion Hochschild (1983): emotional labour depletes at rate comparable to analytical work
Misdiagnosis of innovation failure When orchestration fails, organisations blame culture or execution instead of the structural gap Kerr (1975): rewarding A while hoping for B; systemic misdirection of attention
Talent attrition Professionals performing invisible work seek environments where contribution is recognised Blau (1964): Social Exchange Theory — rational actors leave unreciprocated relationships

BetterUp research (2023) found that employees who report their work as “invisible” to the organisation are 3.5x more likely to leave within 12 months. For orchestrators — who are typically the most cross-functionally connected people in the enterprise — the departure does not just remove one employee. It removes the connective tissue between functions.

Structural Solutions: Three Architectural Changes

  1. Define the function formally. Orchestration exists in every enterprise where innovation crosses departmental boundaries. Naming it — defining what it includes, who performs it, and what authority it requires — is the first step toward making it measurable. This does not necessarily mean creating a new role. It may mean adding the function to an existing role’s formal scope, with corresponding time allocation and KPI adjustment. Mintzberg’s research on organisational design (1983) documented that functions which are not formally named are systematically under-resourced, regardless of their importance.
  2. Introduce flow metrics alongside output metrics. As long as organisations measure only outputs, the work of enabling flow across transitions will remain invisible. Flow metrics — articulation rate, stabilisation rate, handover rate, integration rate — capture the movement that orchestration produces. They make the function measurable without requiring it to produce direct output. The measurement shift is not from less to more. It is from outputs to transitions.
  3. Protect the function during organisational stress. Orchestration load increases precisely when the organisation is under pressure — during transformations, restructurings, strategic shifts. This is when the function is most valuable and most vulnerable. Protecting it means explicitly acknowledging the increased coordination demand, adjusting workload expectations, and ensuring that the function does not collapse under invisible labour. Deloitte’s Human Capital research (2024) recommends that organisations identify “critical connector roles” and apply differentiated resource protections during change periods.

Conclusion

When senior leaders in Nordic enterprises describe their own work as “invisible,” they are making a structural observation that the Bridgium research confirms with interview data: the most critical function in enterprise innovation — orchestration — has no formal name, no KPI, and no explicit recognition in most performance systems.

This is not a recognition gap that can be closed with appreciation. It is an architectural gap that requires structural changes: naming the function, measuring its output through flow metrics, and protecting it during the periods of organisational stress when it matters most

The leaders who are speaking publicly about invisible work are, in effect, performing Stage 1 of the Innovation Flow — articulating a structural problem that the organisation has not yet recognised. The question is whether the system will hear them.

The Bridgium Innovation Flow Checklist provides a structured diagnostic:
bridgium-research.eu/innovation-checklist-2026/
Full research report: bridgium-research.eu/innovation-report-2026/

 

References

  1. Berger, P.L. & Luckmann, T., The Social Construction of Reality Doubleday (1966)
  2. Hochschild, A.R., The Managed Heart: Commercialization of Human Feeling University of California Press (1983)
  3. Burt, R.S., Structural Holes: The Social Structure of Competition Harvard University Press (1992)
  4. Cohen, W.M. & Levinthal, D.A., “Absorptive Capacity: A New Perspective on Learning and Innovation” Administrative Science Quarterly (1990)
  5. Kerr, S., “On the Folly of Rewarding A, While Hoping for B” Academy of Management Journal (1975)
  6. Kaplan, R.S. & Norton, D.P., The Balanced Scorecard: Translating Strategy into Action Harvard Business School Press (1996)
  7. Cross, R. & Parker, A., The Hidden Power of Social Networks Harvard Business School Press (2004)
  8. Mintzberg, H., Structure in Fives: Designing Effective Organizations Prentice Hall (1983)
  9. Blau, P.M., Exchange and Power in Social Life John Wiley & Sons (1964)
  10. BetterUp, “The Invisible Workforce: How Unrecognised Work Drives Attrition” BetterUp Labs (2023)
  11. Deloitte, “2024 Global Human Capital Trends” Deloitte Insights (2024)

Share this blog post: