Useful adaptation
A team changes a process because conditions changed, evaluates the result, updates ownership and documentation, and makes the new method understandable to everyone who depends on it.
When the process people perform no longer reliably matches the process the organization intends or believes it has.
Process Drift is the gradual divergence between a process's intended, documented, or commonly understood form and the way work is actually performed.
A process may begin with one sequence, one source of truth, or one set of decision rules. As exceptions accumulate, tools change, knowledge becomes uneven, and teams compensate for missing inputs, the performed process may develop alternate paths. Eventually, people doing the same work can follow materially different processes while the organization still speaks about a single standard.
Process Drift is not a sixth OEI pillar. It is a pattern that may emerge from interactions among the operating conditions the five pillars examine.
A team changes a process because conditions changed, evaluates the result, updates ownership and documentation, and makes the new method understandable to everyone who depends on it.
A workaround becomes permanent without a clear decision. Different operators inherit different versions, documentation no longer predicts execution, or success depends on knowing an unofficial path.
A workaround can keep work moving and still indicate that the process underneath is unhealthy. Its existence is evidence of adaptation; whether it represents resilience, necessary variation, or concealed drift requires investigation.
Several operating conditions can produce the same visible variation. These links lead back to the diagnostic locations OEI would examine.
Knowledge may not travel: teams may reconstruct a process from incomplete documentation, memory, or local convention.
Work may be forced around constraints: missing access, approvals, context, or poorly fitted tools may create unofficial routes.
Transfers may change the process: each handoff can lose criteria, context, or ownership and leave the receiver to improvise.
Leadership may become the exception handler: the founder or a senior operator may personally reconcile versions that the system itself cannot keep aligned.
None of these signals proves Process Drift by itself. OEI would compare the documented process with observed work, interview the people who perform and receive it, review operational artifacts, and test whether different paths are intentional and reliable.
Employees often preserve outcomes by remembering undocumented context, manually correcting inputs, chasing approvals, or working around a tool. The process appears to function because a person absorbs the inconsistency.
This is one expression of The Mitigation Trap: temporary compensation is mistaken for system health. When the compensating person is absent, demand increases, or a handoff changes ownership, the underlying divergence may become visible.
OEI would begin with a consequential workflow and map it as performed, not only as documented. The investigation would compare paths across operators, teams, locations, tools, and handoffs; identify where and why variation entered; and test whether it creates delay, rework, uncertainty, or dependence on exceptional effort.
When the problem is already bounded, a Workflow Momentum Analysis can expose where execution diverges or stalls. If the variation is primarily shaped by software or transfer points, an Operational Stack Review or Handoff Failure Analysis may be the more relevant investigation.
Use the engagement assessment to identify the smallest useful next step.
Find your engagement path