Governance maturity may be assessed function by function: does finance have adequate controls, does technology have adequate oversight, does each business unit have clear reporting lines. That assessment can return favorable answers across individual functions while enterprise-level governability remains weaker at their interfaces. Material conditions can cross functional boundaries even when control structures are designed function by function.

The mechanism. Control frameworks, reporting structures, and escalation paths are typically designed within organizational units, because that is how governance responsibility is assigned and how audits are typically scoped. Interfaces between units — where one function’s output becomes another’s input, where a subsidiary reports up to a parent, where a joint venture straddles two governance structures — are structurally under-owned. No single function has full accountability for the interface itself, because the interface belongs to both sides and, in practice, is often fully owned by neither.

Why this is dangerous specifically at scale. As organizations grow more complex — more business lines, more entities, more interconnected systems — the number of interfaces grows faster than the number of functions. A modest increase in organizational complexity produces a much larger increase in the number of seams where control may be thin, even while each individual function continues to report strong internal governance.

Documented pattern. This is not a hypothetical concern. Financial sector post-crisis reviews identified a consistent finding: individual business lines often had reasonable internal risk practices, while the organization as a whole could not reliably aggregate exposure or identify concentration across those lines, because no governance structure was positioned to see across the seams rather than within each function separately. The failure was not that any one function was poorly governed — it was that the space between functions was invisible to governance by design.

Governance consequence. A board reviewing function-by-function governance reports can reasonably conclude the organization is well governed, because each report is, individually, accurate. The blind spot exists precisely because no single report is responsible for covering the interfaces, and the board’s review process, built to receive function-level reports, has no natural mechanism for asking the cross-boundary question directly.

What this requires. Governability at the enterprise level requires an explicit answer to a question that function-level governance does not naturally produce: who is accountable for the condition of each significant interface between functions, entities, or systems — not the functions on either side of it, but the interface itself.

Evidence boundary. The general pattern — functional governance maturity coexisting with weak cross-boundary control — is well documented in financial-sector post-crisis analysis and broader organizational research on silos and coordination failure. The specific framework proposed here, of assigning explicit accountability to interfaces rather than only to functions, is Obraval’s synthesis.

The executive question. For any two functions or entities that depend on each other, ask who is accountable for the space between them — not for either side, but for the seam itself.