Core idea · Institutional Drift
How Systems Drift
Reasonable local decisions can accumulate into a process no one would design as a whole.
The first check was added after a real failure. The second came from legal. The third came with a vendor. By the fifth, nobody could remove a step because nobody owned the whole route.
Bad systems are not always designed in one bad meeting. A safety check gets added after an error. A vendor brings a second portal. Legal adds a notice. Another team tracks a local target. Each piece can make sense while the whole route becomes something no one owns. Following the timeline is slower than assigning motive, but it usually explains more—and it leaves room for repairs that actually worked.
Recognize it in ordinary life
The bend rarely announces itself.
Blaming one villain can hide the repairable mechanism. A timeline of rules, incentives, handoffs, and ownership changes often explains more than a confident theory about motive.
Watch for this: Find where the original purpose lost its owner, and check whether later repairs changed the end-to-end burden.
Three places it can show up
- Five departments add separate checks after five different incidents.
- A new vendor portal duplicates information already held by the original system.
- Every team meets its local performance target while the person moving between teams waits longer.
These are recognition examples, not findings about every company, program, or transaction. The record still has to establish the specific case.
01
Recover purpose and sequence
State the system’s published purpose and build a dated record of material additions, exceptions, ownership changes, vendors, metrics, and temporary rules that remained.
02
Follow incentives and handoffs
Ask what each participant is rewarded for avoiding, completing, reporting, or shifting. A process can degrade without a single actor intending the final result.
03
Keep motive on a short leash
Distinguish tradeoff, risk control, neglect, path dependence, vendor constraint, metric gaming, incompetence, and deception. Similar burdens can arise from very different mechanisms.
A question to carry
Think of the last time this happened to you.
Think of a process where every employee seemed responsible for one step and nobody could fix the whole path. Where did ownership disappear?
If you want to keep looking, choose a familiar procedure with at least three handoffs. Build the shortest timeline you can support. Circle any step whose owner, purpose, or removal authority is unclear.
When you want to go deeper
Questions that keep the story honest
- What was the original mandate?
- When was each step added?
- Who owns the end-to-end outcome?
- Which claim describes effect, and which claim assigns intent?
Try to disprove yourself
The strongest honest countercase
Complexity is not proof of conspiracy or incompetence. Some systems are complex because the underlying work is complex.