Process drift describes the gradual state in which a company’s documented workflows increasingly diverge from lived reality — without anyone actively noticing or correcting the difference. It isn’t the exception but the norm: write processes down once without systematically keeping them current, and before long the documentation barely matches day-to-day operations.
We have processes — but for months now something quite different has been happening. The only person who knows is the one doing it.
That sentence captures a problem that exists daily in many companies but is rarely named. Not because nobody minds, but because nobody has a channel for making it visible.
What process drift is — and why it happens
Processes change. Constantly. New software gets introduced, a supplier changes, someone finds a faster route, a client request creates an exception step that quietly becomes permanent. None of these changes is problematic in itself. The problem arises when the process documentation doesn’t follow.
Conventional process documentation systems — PDFs on a shared drive, Word files in SharePoint, printed process maps on a wall — share a structural weakness: they’re static. Someone has to actively decide to open, edit and save them. In practice, that rarely happens.
Drift starts small. A step disappears because it turned out to be redundant. Another gets added because a source of errors had to be eliminated. After a few months, the process in an experienced employee’s head looks different from what sits in the folder. Eventually the documentation becomes a historical record.
The crucial point: nobody made a mistake. Every individual change was sensible. Drift is a systemic effect, not an individual failing — which is exactly why it isn’t solved by reminders, but by a different mechanism.
The three cost drivers of process drift
Flawed onboarding on an outdated basis
When new hires are trained on outdated documentation, they don’t learn how the company works today — they learn how it worked a year ago. The resulting errors then get attributed to the new person rather than to the drift.
Audit risk through shadow processes
For companies with quality management systems, drift isn’t an operational annoyance but an audit risk. An external auditor compares the documented process with what people actually do. Where the two diverge, that’s a finding — regardless of whether the lived version is the better one. Accredited laboratories under ISO/IEC 17025 face additional requirements, which we cover on a dedicated page.
Knowledge loss when people leave
When the person who last performed the process as it really works leaves, the practical delta knowledge goes with them. What remains is outdated documentation. Whoever takes over works from a basis that no longer holds and fills the gaps by asking around and trial and error. Our article on absence cover covers what that means in practice.
Static vs. living process documentation
| Static documentation | Living process documentation | |
|---|---|---|
| Updating | Manual, when someone remembers | Continuously maintainable, with visible change history |
| Divergence visible? | No — drift goes unnoticed | Versioning and change records show the delta |
| Traceability | None | Who changed what and when — fully logged |
| Audit readiness | Questionable as soon as reality diverges | The documented current state is the auditable state |
| Onboarding basis | A historical snapshot | The real, current process |
Three questions that expose drift immediately
The core problem isn’t technical, it’s a visibility problem. Drift stays invisible as long as nobody has a mechanism for capturing divergence. You can ask these three questions tomorrow:
When was a process last actively updated?
If the answer is more than six months ago while things have changed operationally, either the answer is wrong or the documentation is drifting.
Can three different employees describe the same process identically?
If the answers differ substantially, each person is describing what they personally do — not what was agreed.
Would an auditor find a divergence during an unannounced visit today?
The question sounds harsh, but it’s the most precise drift test there is.
In the Fraunhofer ProWis project, which studied process-oriented knowledge management in manufacturing SMEs, “knowledge as a critical success factor” ranked among the participating companies’ largest challenges — with rapid onboarding of new employees identified as the area with the greatest room for improvement. What rarely exists is any method for measuring the degree of divergence at all.
Getting out of the drift cycle
The way out isn’t a one-off rewrite of all your process documentation. That consumes capacity and leads straight into the next drift cycle if the new documents are treated as statically as the old ones.
The way out is structural continuity: changing a process has to cost less effort than keeping the delta in your head. As long as updating is more work than remembering, documentation will never keep pace. That’s a question of friction, not discipline.
This is precisely where digital colleagues come in. Lars, one of Kollegia’s Digital Colleagues, reduces that friction at both ends. When capturing, it turns a few bullet points into a complete step description, so nobody faces a blank page. Afterwards it keeps watch: identifying processes untouched for a conspicuously long time, flagging steps whose responsible role has changed, and pointing out workflows with no cover assigned.
Three principles
- Permission intersection — a digital colleague never sees more than the person it works for.
- Fail-closed — when in doubt, nothing happens. If it’s unclear whether a change is correct, it’s submitted for review rather than applied automatically.
- Audit trail — every change is logged: when, by whom, on what basis. That makes it demonstrable which version applied when.
One distinction matters: this isn’t about monitoring employees. It’s about lowering the cost of honest documentation far enough that it actually happens.
FAQ
Source: ISO/IEC 17025:2017 – General requirements for the competence of testing and calibration laboratories, ISO.
Process drift is the divergence between a process as documented and what employees actually do day to day. It builds gradually through workplace changes that never make it into the documentation, and usually only becomes visible when onboarding new staff or during an audit.
For certified companies, drift is a direct compliance risk. Auditors check whether documented and lived processes align; divergences are auditable findings and can lead to non-conformities. Documentation that reflects the actual current state is therefore not optional.
Yes — but through reduced documentation friction, not surveillance. The less effort an update takes, the more often it happens, and the less drift accumulates. A digital colleague turns bullet points into a complete description and flags processes that haven’t been updated in a long time.
Direct costs arise in three places: extended onboarding from an outdated training basis, higher error rates during cover and handovers, and audit risk for certified processes. On top of that comes the hard-to-measure loss of process knowledge when key people leave.
A fixed schedule helps less than a trigger principle: documentation is reviewed whenever something changes — new software, new responsibility, altered workflow. An annual sweep is a useful supplement to catch processes where something shifted unnoticed.
