INSIGHTS / THE MERIDIAN SERIES
15 / 16
Enterprise Divergence Makes Drift Governable
Meridian makes enterprise drift visible by establishing the material difference between the condition leadership intended and the condition the business is carrying. That difference is Enterprise Divergence. When it persists without correction, reconsideration, or appropriate authority, it becomes Enterprise Drift.

The distinction matters because enterprises rarely move out of alignment through one obvious event. The condition of the business changes through ordinary operation. A service expands. A dependency changes. A treatment loses funding. A control no longer supports the activity around it. Each change may appear reasonable when viewed on its own while their combined effect moves the enterprise away from the condition leadership approved.
Intended State Provides the Reference
Intended Enterprise State is the operating condition leadership has chosen through strategy, investment, authority, risk appetite, capacity, and operating limits. It expresses more than an objective. It establishes the condition leadership is prepared to fund, operate, and carry while pursuing that objective.
That intended condition may include a service leadership has approved, the limits placed on its use, the dependencies supporting it, the exposure the enterprise is prepared to carry, and the work required to reach a more durable condition. Those elements are connected because the decision depends on their combined effect.
A decision to continue operating may be reasonable while certain controls remain in force. A treatment may be approved because the enterprise has the people and capital required to complete it. A dependency may be acceptable under the obligations that applied when the decision was made. If those supporting conditions change, the original decision does not automatically describe the enterprise that follows.
Intended Enterprise State provides the reference needed to determine whether it still does.
Current State Establishes What the Enterprise Is Carrying
Current Enterprise State is the decision-relevant condition actually in force. It reflects the material facts that determine what the enterprise can do, what it depends on, what constraints apply, and what exposure exists now.
The current condition is not established by the most recent approval, project status, or risk record alone. Those records may each describe part of the enterprise. The operating condition emerges from their combined effect.
A treatment can remain marked as funded after the people required to deliver it have been reassigned. A provider can remain approved after its obligations change. A control can remain documented while the activity around it expands beyond the condition it was intended to support. None of those facts necessarily invalidates the original decision by itself. Together, they may create a materially different enterprise.
Meridian keeps those facts connected to the business condition they produce. That makes it possible to compare the enterprise leadership intended with the enterprise now in operation.
Divergence Is the Material Difference Between Them
Enterprise Divergence is the material distance between Intended and Current Enterprise State. It identifies where the operating condition has changed in a way that matters to the enterprise.
Not every difference is material. Businesses change constantly, and many changes remain compatible with approved direction. A service may add capacity without altering its exposure. A provider may update an administrative term without changing the obligation leadership relies on. A treatment may move within its delivery plan while remaining feasible.

Divergence becomes material when the changed condition affects the basis on which the enterprise was authorized to operate. The change may alter exposure, remove a required dependency, weaken a constraint, exceed delegated authority, or make an approved transition no longer achievable under the conditions leadership expected.
Consider a business capability that is permitted to operate while a control improvement is completed. Leadership accepts the current exposure because the service remains within a defined scope and the treatment is funded to reach the intended condition. The service later expands, while the treatment loses delivery capacity. The business is now carrying more exposure through a path that has become less capable of reaching the condition leadership approved.
The service expansion and capacity change may exist in separate systems. Enterprise Divergence expresses their combined significance. The problem is no longer that two records changed. The enterprise has moved away from the operating condition leadership intended.
Drift Is Divergence That Persists
Enterprise Drift is the business condition created when material divergence persists. It develops when the enterprise continues operating outside the condition leadership intended without restoring alignment or establishing a new authorized condition.
That persistence is important. A temporary difference may be understood, governed, and corrected through ordinary operation. Drift develops when the changed condition becomes embedded in the business. Teams begin planning around it. Dependencies form around it. Exposure accumulates within it. The enterprise gradually treats the condition as normal even though leadership never evaluated or approved it as the new operating basis.
This is why drift can be difficult to see through conventional reporting. The underlying records may remain individually accurate. The service is correctly recorded as active. The provider agreement is current. The treatment plan reflects its revised schedule. The risk acceptance remains on file. The unresolved issue is whether those records still describe one compatible enterprise condition.
Meridian makes that relationship visible. It allows the enterprise to determine whether the authority and risk appetite in force still apply to the condition being carried.
Divergence Can Begin Within One Domain
Enterprise Divergence does not require an enterprise-wide implementation before it becomes useful. It can be established within cyber risk, third-party risk management, operational risk, compliance, or another material domain.
A cyber deployment can compare the intended security condition with the controls, access, dependencies, and exposure currently in force. A third-party risk deployment can compare the dependency leadership approved with the provider obligations and business reliance that exist now. The same governing relationship applies because each domain produces a condition the business must carry.
As additional domains are connected, Meridian can show where a change originating in one area affects another. A provider change may alter a compliance obligation. A technology decision may change operational exposure. A delayed treatment may affect the authority under which a business capability continues.
The enterprise view expands through those relationships. It does not depend on forcing every domain into one implementation at the beginning.
Economic Context Establishes Materiality
Divergence becomes more useful when leadership can understand its consequence in business and economic terms.
A changed condition may increase expected loss, reduce the value of an approved treatment, extend the period during which exposure must be carried, or require additional capital to restore alignment. Expressing exposure in dollars gives leadership a common basis for comparing those consequences with investment, expected reduction, and the value of the objective being pursued.
Financial normalization does not decide whether a divergence is acceptable. It helps establish what the divergence means to the enterprise. Leadership can determine whether the changed exposure remains within appetite, whether the authority in force is sufficient, and whether the investment required to correct it remains justified.
This turns divergence into a governing question rather than another exception appearing on a report.
Drift Requires an Enterprise Response
Once material divergence is visible, the enterprise has to determine what condition it is prepared to carry.
Leadership may restore the original operating condition. It may establish the controls, capacity, or obligations required to make the current activity permissible. It may authorize a different condition after evaluating the exposure and business value. The appropriate response depends on the facts in force and the authority required to act on them.
The important point is that drift cannot be resolved by updating a record to match what happened. The enterprise must either return to the condition it intended or deliberately establish a different condition it is prepared to carry.
Meridian provides the current view needed to make that determination. Intended Enterprise State establishes the reference. Current Enterprise State establishes the condition in force. Enterprise Divergence makes the material difference visible. Enterprise Drift identifies when that difference has become part of how the business operates.
The next requirement is convergence: establishing the permissible path from the condition the enterprise is carrying to one leadership is prepared to authorize.