Every organization operates two systems at once: the one it wrote down and the one it runs. The distance between them is called drift, and most leadership teams are governing the wrong one.
Walk into most organizations and the operating model looks impeccable. Clean process maps. Named owners. Approval gates in the right places. Then watch the same organization on an ordinary Tuesday, and you will see something else running. I have spent more than four decades inside operations, and the beautiful document is the thing I have learned to distrust first. The document is not the system. It is a photograph of the system on the day it was born.
This is not a story about weak teams or careless documentation. It is a story about a gap that opens inside healthy, well-run organizations, stays invisible, and costs real money long before anyone gives it a name. The name is drift, and learning to see it is the difference between leading the organization you have and managing a memory of the one you designed.
Two Systems, One Name
On the day you finish designing a process, you have two systems that are identical. The documented system is what you wrote down. The running system is what people do. At launch they match. That is the last moment they will.
From there, the running system changes and the document does not. A vendor asks for an exception and someone grants it because the deadline is real. A control that adds three days gets worked around because a customer is waiting. A handoff that once routed through a single manager now routes through whoever answers first. None of these are failures. Each is a capable person solving a real problem in the moment.
Drift is the residue of good judgment that no one wrote down, and that no system was built to reconcile. Multiply one small, sensible adjustment by a thousand across a year, and the system you run stops resembling the system you documented. The map still says one thing. The territory does another.
The Number Most Leaders Misread
The Project Management Institute has put the waste at ninety-seven million dollars for every billion invested in projects. Leaders read that figure and reach for the usual explanations: scope creep, weak estimates, poor execution. Those are real. They are also not the largest driver. In the programs I have run, the single biggest source of waste is quieter than any of them. It is the widening distance between the system a company designed and the system it now runs, compounding unwatched until it surfaces as an incident with a price tag attached.
Why You Cannot See It
If drift were loud, it would be easy. It is silent, for three structural reasons.
It is local. Each adjustment happens inside one team, one workflow, one relationship. The person making it sees their piece. No one stands where all the pieces meet, so no one sees the sum.
There is no baseline in view. The documented system lives in a repository nobody opens after go-live. Without the original in front of you, the drifted version looks normal. It becomes the water everyone swims in.
It resolves problems early. Drift usually makes today easier. The workaround clears the queue. The exception keeps the vendor moving. Because the near-term result is relief, the adjustment reads as a win rather than a warning.
So the organization keeps running, the reports keep clearing, and the distance keeps growing. Nothing signals a problem, because from any single seat there is no problem.
What a Green Dashboard Is Telling You
Here is the part that unsettles executives. Your dashboard can be entirely green while your running system has drifted well off its documented design. A status dashboard reports against the plan. It measures the documented system. When milestones land and metrics sit inside tolerance, the board shows green. But the dashboard has no way to see the difference between the process you designed and the process your people execute, because it was never built to look there. Green is not evidence that the system is sound. Green is evidence that the reported version of the system is on plan.
That distinction is the whole game. Leaders make confident decisions on green dashboards every week. When the reported system and the running system have separated, those decisions are being made against a picture that is out of date, and no one in the room knows it.
The Two Fixes That Make It Worse
When leaders finally sense the gap, the market offers two answers, and both deepen it. The first is to buy a better dashboard. More telemetry, more real-time reporting, a single pane of glass. But a better dashboard measures the documented system faster. It still has no way to know whether the process it charts is the process your people run. You have not closed the gap. You have grown more confident about the wrong system.
The second answer is to commission a fresh design, often from a large consulting firm. A team arrives, studies the operation, and delivers a pristine new target operating model. The engagement ends. The binder goes on the shelf. And the new document begins to drift the day the consultants leave, because nothing in the deliverable was built to reconcile it against reality. You have paid for a cleaner photograph of a system that will not hold still.
The Alternative Is a Discipline, Not an Artifact
The answer to drift is not a better document or a brighter dashboard. It is a habit of reading the running system against its design, on purpose, before the gap becomes an event. That habit is what the AGE Framework™, our Adaptive Governance Engine, is built to give you. Adaptive, because a living system is supposed to change and you want to govern the change rather than pretend it away. Governance, because someone has to hold the standard. Execution, because the only version that matters is the one your people run.
There is a companion idea worth naming. Drift is velocity outrunning governance. When the pace of change in the running system moves faster than your ability to see and steer it, the gap widens. That is the tension the Velocity Governance Framework™ exists to hold, and it is why speed you cannot govern is not an advantage. It is exposure.
What This Looks Like in Practice
Consider a vendor onboarding process at a mid-market services firm. Well designed. Nine steps, two approval gates, one owner. Over nine months the team hit a run of urgent onboardings, and each time they trimmed a step to move faster. Skip the secondary review this once. Batch the compliance check to Fridays. Let the account lead approve in place of the gate owner when the gate owner is out.
Every decision was defensible. None were written down. By month nine the running process had five steps and no consistent approver, while the documented process still had nine. The dashboard stayed green the whole time, because the metric it tracked was onboarding cycle time, and cycle time had never looked better. The drift stayed invisible until a vendor cleared onboarding without the compliance check, and that vendor became a problem large enough to reach the executive team. The step they had trimmed as a convenience was the one designed to catch exactly that. By the time anyone connected it, the drift was an incident. It did not have to be.
The Point
The system you run is not the system you documented, and the distance between them is not a sign that something is broken. It is a sign that your organization is alive and adapting. The failure is not the drift. The failure is not being able to see it, and then governing with confidence from a document that stopped being true months ago.
This is the threat the rest of this series takes apart. Where drift hides. Why it has no owner by default. And what it takes to close the distance on purpose instead of discovering it by accident.
See where your own system stands
The Executive Dashboard Template shows you how to build a view that reports on the system you run, not only the plan you drew. In about fifteen minutes it surfaces the one gap your current reporting cannot show you: where the running system has moved away from the system you designed. Download it from the TransformXperience Insights hub, and take the short self-assessment while you are there to gauge how far the two have separated.
