Material Here, Immaterial There
The same condition can be treated as material in one part of the organization and immaterial in another — and both determinations can be internally defensible.
In organizations where materiality is assessed across functions, entities, or reporting contexts, the same condition may be evaluated against different scales, thresholds, or qualitative considerations. The result is that a condition can be assessed as immaterial in the unit where it originates while, viewed at enterprise scale or in combination with similar conditions elsewhere, it could warrant a different enterprise-level interpretation.
The mechanism. A materiality threshold set relative to a business unit’s own budget, revenue, or risk appetite is internally coherent — a condition genuinely may be immaterial to that unit. But enterprise-level governance is concerned with materiality to the organization as a whole, which is a different denominator entirely. A condition immaterial against a single unit’s scale can be highly material against enterprise scale, particularly if similar conditions exist, unrecognized as related, across several units simultaneously.
Why this is not simply an ESG reporting concern. Materiality fragmentation is frequently discussed in the context of sustainability and financial disclosure, but the underlying governance problem is broader: any organization that determines materiality locally, without a mechanism for recognizing when locally immaterial conditions are actually instances of an enterprise-material pattern, is vulnerable to this fragmentation regardless of what kind of condition is being assessed — operational, technological, reputational, or financial.
Governance consequence. A board reviewing materiality determinations function by function can receive uniformly reasonable-sounding conclusions — “not material to this unit,” repeated across several units — without any of those conclusions being wrong on their own terms, while the enterprise-level picture, which no single function was positioned to assemble, would tell a materially different story.
What consistency requires. This does not mean materiality thresholds must be identical across every part of the organization — that would ignore genuine differences in scale and context. It means the organization needs an explicit mechanism for periodically asking whether locally immaterial determinations, viewed together, describe a pattern that is material at enterprise scale — a question that, by construction, no single function’s materiality process is positioned to ask on its own.
Evidence boundary. Fragmented and context-dependent materiality assessment is documented in financial, disclosure, and sustainability governance contexts. Obraval extends the underlying structural issue to enterprise governance more broadly; that broader application is interpretive rather than a universal empirical finding. The specific recommendation for periodic cross-unit pattern review is Obraval’s synthesis rather than an established standard practice.
The executive question. Has any single point in this organization ever asked whether conditions judged immaterial in several different units, taken together, describe something material at the enterprise level?