Idea 005
When Exceptions Become the System
The point at which a workaround stops being an exception and becomes the operating procedure, without anyone having decided that it should.
- First appeared
- Last updated
- Domains
- Controls, Evidence, Maintenance
Why it matters
Exceptions are tolerated because they are understood to be temporary. They become permanent through use: a procedure is written, a rota absorbs it, a spares position adapts to it, and a small group of people come to understand how it behaves.
The concept matters because nothing in the reporting marks the transition. The exception continues to be counted as an exception long after it has become the way the work is done, which means the organization is measuring a condition it no longer has.
The idea appears in
Essays
- Your Opex Problem May Have Started Ten Years Ago
Some operating expenses belong to the ordinary cost of running a system. Others are the recurring price of decisions made years earlier.
8 min read
Field Notes
- A Control Isn’t a Control Because Someone Clicked Approve
Approval records that an action happened. It does not record whether anyone looked.
3 min read
- The Spare That Was Never Ordered
A part that is always borrowed is a part the system has decided not to own.
2 min read
Case Studies
- Clearing a Temporary Repair Backlog
A backlog of temporary repairs awaiting permanent remediation fell from roughly 600 items to roughly 80 in about ten weeks, under dedicated capacity and senior escalation.
Case Study 001
Related ideas
How the idea has evolved
Posed as a question: when does an exception stop being an exception?
Connected to evidence. A control that produces a record of participation rather than of scrutiny has already made the transition.