Why do documented processes drift from reality?
Because the work changes every week and the documentation changes only when someone makes time for it. A new customer, a new system screen, a missing part, a new colleague — each adds a small workaround that is not worth updating the procedure for. Together they turn the document into a description of how the company used to work. Drift is not a discipline problem. It is what happens when documentation has no owner, no triggers for review and no link to the daily work.
A short story
A food producer wrote its line-cleaning procedure for a certification audit. Over the following years the team switched cleaning agents, the line layout changed and a new shift pattern was introduced. Each time, the team lead adapted the real sequence in practice. The document stayed as it was, and it passed every audit.
Then the team lead was absent for several months. The stand-in followed the procedure to the letter — with the old cleaning agent's contact times and a step for equipment that had moved. Nobody had done anything wrong. The document had simply stopped describing the work. (An illustrative example, not a client case.)
How does drift happen?
- Day one: the procedure matches the work, because it was written from it
- The first months: small workarounds appear — for a new customer, a missing part, a changed screen
- The first year: the workarounds become the normal way. New colleagues learn from colleagues, not from the document
- After that: the document is opened for audits only, and updated to look right rather than to be right
Why doesn't a yearly update fix it?
A yearly review catches the changes someone remembers. It misses the silent ones: the step people skip because the system does it now, the check that moved to another team, the exception that became the rule.
Two things work better. Review on change, not only on the calendar: a new system, a new customer agreement, an incident, a new person in the process. And review against a real case — follow last week's work through the document and note every difference.
Which signs show your documentation has drifted?
- new colleagues hear “forget the procedure, this is how we do it”;
- two versions of the same instruction are in use;
- documents are updated in the weeks before an audit, and not otherwise;
- the steps no longer match the screens of your systems;
- people ask the same colleague instead of looking it up.
Can drift be prevented completely?
No, and it does not need to be. Work should adapt when customers, systems and people change. The goal is to notice the change quickly and decide whether it becomes the new standard, instead of discovering years later that the document and the work parted ways.
That is why ownership matters more than format. A simple instruction with an owner and review triggers stays closer to reality than a detailed manual that belongs to nobody.
How MentX helps
MentX captures how your company really works: the knowledge of your key people and the processes they run. We offer both a hands-on service approach — mapping your processes and capturing the knowledge behind them, from meetings, workshops and a guided intake — and our own personality-aware knowledge base, with full source attribution, in your own Knowledge Space. We build on the tools you already use and add best-practice solutions where they fit.
We map processes from real cases, not from existing procedures, and give every process an owner and review triggers. In the MentX knowledge base every statement keeps its source and its date, and newer knowledge replaces the old without erasing it — so you can see what changed, when, and on whose word.
What to do this quarter
- Pick one critical procedure and hold it against last week's real case.
- Note every difference, and ask the people involved why.
- Update the document from the real case, with the date and who confirmed it.
- Name an owner and agree the triggers that force a review.
- Link the document from the place where the work happens.
