The Durable Performance Brief · Edition 29 · October 7, 2026
Most organizations have two sets of policies.
The first is written down.
The second is learned through experience.
The written policy may say that approvals belong at a certain level, deadlines have a defined meaning, performance standards apply consistently, or a particular process must be followed.
Then something unusual happens.
A customer situation requires flexibility. A valuable employee needs latitude. A deadline forces compromise. A leader makes a reasonable judgment call and grants an exception.
Nothing about that is necessarily a problem.
The problem begins when the exception survives the circumstances that justified it.
Someone remembers it.
Someone references it.
A similar case appears.
And eventually the organization stops asking whether the exception should exist.
It starts asking who qualifies for it.
That is the moment an exception begins becoming policy.
Policy Can Change Without Being Rewritten
Organizations often think of policy change as a formal event.
Someone proposes a revision. Leaders discuss it. Legal or HR reviews it. Documentation changes. The new standard is communicated.
But operating policy can change without any of that happening.
Behavior only needs a precedent strong enough to compete with the written rule.
Consider a manager who is allowed to bypass a normal approval because an important customer is at risk.
The decision may be correct.
Three months later, another manager faces a similar situation and points to the earlier exception. Denying the second request now requires leadership to explain why the cases are different.
So the second exception is granted.
Then a third.
Eventually, the conversation changes.
The organization is no longer debating the original standard. It is managing the boundaries of an alternative operating rule.
The formal policy still exists.
The precedent governs behavior.
That is a classic mechanism of organizational drift. Structure changes through repeated operating decisions long before anyone announces that the structure has changed.
Precedent Creates Its Own Logic
Once an exception exists, it becomes a comparison point.
That creates pressure for consistency.
If one person received flexibility, why should another similar case not receive it?
If one team was allowed to bypass the process, why should another team bear the full burden?
If one high performer was protected from a consequence, what distinguishes the next high performer?
This is where an isolated judgment decision starts becoming structural.
Leadership may still believe it is evaluating every situation independently. The people inside the system are doing something different: they are mapping the precedents.
They are learning where the boundaries actually sit.
Over time, people become skilled at framing their circumstances so they resemble previously approved exceptions.
The question is no longer:
What does the standard require?
It becomes:
How do we qualify for the exception?
Once that happens, the exception is influencing behavior more strongly than the rule.
The Hidden Shift in Accountability
This creates a particularly difficult problem for accountability design.
Accountability depends on people being able to predict the relationship among standards, ownership, correction, and consequence.
Exception-driven systems make that relationship increasingly conditional.
A manager enforcing the written standard can suddenly look unreasonable because another manager received flexibility.
An employee being corrected can point to someone who was not.
A leader trying to restore discipline can appear inconsistent because the organization has already adapted to the exception.
The irony is important.
The original exception may have been granted in the name of fairness.
Repeated exceptions eventually make fairness harder to establish.
Now every decision requires context.
Every standard needs interpretation.
Every correction invites comparison.
The organization becomes increasingly dependent on explanation because the operating rule is no longer obvious.
Why Leaders Add Process
At this point, organizations often try to solve the problem by formalizing the exceptions.
They add approval criteria.
They create review committees.
They define special circumstances.
They add documentation requirements so managers can distinguish legitimate exceptions from illegitimate ones.
That can feel like discipline.
But sometimes the organization is simply building bureaucracy around a standard it no longer consistently enforces.
The original rule remains.
The exceptions remain.
Now there is also a process for deciding who gets to bypass the rule.
This is how organizational entropy accumulates through reasonable additions.
Nothing is necessarily removed.
The organization keeps the standard, keeps the exception, and adds machinery to manage the tension between them.
What began as flexibility becomes structural load.
The Difference Between an Exception and a Policy
The distinction is not whether something is written down.
It is whether the organization expects it to happen again.
A real exception is bounded.
It has a reason.
It has an owner.
It has conditions.
Most importantly, it has an end.
An informal policy is different.
People expect it.
They reference precedent.
Managers know how to request it.
Similar situations receive similar treatment.
Removing it would now feel like changing the rules.
That final condition is particularly revealing.
If ending an “exception” would require a change-management effort, it probably stopped being an exception some time ago.
One Practical Diagnostic
List the significant exceptions your organization has granted during the last six months.
Then ask one question about each:
If we denied this same exception tomorrow, would people believe we had changed the rules?
If the answer is yes, investigate further:
- Has the exception occurred more than once?
- Do employees or managers reference earlier cases when requesting it?
- Is there now an informal process for obtaining it?
- Does leadership spend time deciding who qualifies?
- Would removing it create accusations of inconsistency or unfairness?
- Does the original standard still describe how work actually happens?
Those are signs that precedent may already have become operating policy.
If You Change One Thing This Week
Create an exception register.
Do not make it elaborate.
For every material exception, record:
The standard being suspended
Why the exception is necessary
Who owns the exception
Who or what it applies to
The expiration or review date
Then add one more question:
Does this exception reveal that the underlying standard itself should change?
That matters.
Not every exception is evidence of weak discipline. Sometimes repeated exceptions reveal a badly designed rule.
A disciplined organization should be willing to change a standard deliberately when reality shows that the standard no longer serves its purpose.
What it should avoid is allowing the standard to change accidentally through accumulated precedent.
That is the role of leadership systems: making sure temporary accommodations expire, structural decisions remain deliberate, and operating reality does not quietly outrun formal expectations.
Go Deeper
Why Organizations Drift examines how reasonable exceptions become precedent, why precedent becomes increasingly difficult to reverse, and how organizations gradually replace clear standards with context-dependent operating rules.
The issue is not whether leaders should ever make exceptions.
They should.
The issue is whether the organization can distinguish a deliberate exception from an accidental redesign.
Closing Thought
Organizations rarely announce that a standard no longer applies.
They simply behave around it long enough that enforcing it begins to feel unusual.
That is how an exception becomes policy.
Not through a vote.
Not through a memo.
Not through a deliberate redesign.
Through precedent.
The policy on paper survives.
The operating policy moves somewhere else.
Question for readers: Which “temporary” exception in your organization would now feel like a policy change if you removed it?
Next Wednesday: The slow erosion of judgment.
Part of The Durable Performance System™
Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
Published every Wednesday morning.
Curtisstoaks.com – YouTube – @curtisstoaksauthor
