The Durable Performance Brief · Edition 28 · September 30, 2026
Most organizational standards do not disappear because leadership formally abandons them.
They disappear because leadership makes exceptions to them.
A deadline slips for understandable reasons. A high performer behaves in a way that would normally require correction. A manager avoids a difficult conversation because the timing is bad. A process is bypassed because the customer situation is unusual. A commitment is missed, but the explanation seems reasonable.
None of these decisions necessarily looks irresponsible.
That is what makes tolerance difficult to see as a structural force.
The individual decision may be reasonable. The accumulated lesson can still be destructive.
Tolerance Does More Than Avoid Conflict
Leaders often experience tolerance as discretion.
They know the circumstances surrounding the decision. They understand why an exception was warranted. They remember the pressure, the tradeoff, the relationship, or the unusual conditions that made enforcement seem unnecessarily rigid.
The organization experiences something different.
It sees what happened.
A standard existed. The standard was crossed. No meaningful correction followed.
That becomes information.
The next time a similar situation appears, people do not evaluate the standard only by what the policy says. They also evaluate what happened the last time it was tested.
This is one of the central mechanisms of organizational drift: the operating system changes through precedent long before anyone formally changes the rules.
Tolerance is therefore not passive.
It teaches.
The Cost Compounds
The first accommodation may have almost no visible organizational cost.
The tenth is different.
Repeated tolerance changes what people believe is actually required. It creates a growing gap between the stated standard and the experienced standard.
That gap changes behavior.
High performers often absorb the difference first. They compensate for missed commitments, resolve problems informally, protect customers, correct weak work, and carry additional load because they still feel responsible for the outcome.
For a while, their compensation makes tolerance look inexpensive.
Results remain acceptable.
The problem appears contained.
But the organization is now receiving a false signal: leadership can tolerate the behavior because someone else is absorbing its consequences.
Eventually, other people adapt too.
They learn how precise they really need to be. They learn which commitments are firm and which are negotiable. They learn whose misses receive correction and whose receive explanation. They learn when a standard matters enough to enforce and when circumstances are likely to override it.
This is where tolerance begins interacting with incentive architecture.
People are not simply responding to formal rewards. They are responding to what the system protects, excuses, recognizes, corrects, and allows to continue.
The stated standard may not have changed.
The behavioral incentive has.
The System Remembers What Leaders Treat as Isolated
This is why leaders frequently underestimate the accumulation.
They remember context.
The organization remembers precedent.
To the leader, there may have been ten different decisions:
One involved a critical customer.
One involved a strong employee having a difficult quarter.
One involved an unusual deadline.
One involved a politically sensitive situation.
One involved a manager who deserved additional latitude.
Each decision had its own rationale.
But systems do not preserve those distinctions cleanly.
People observe patterns.
They see that deadlines can move.
They see that standards depend on who is involved.
They see that accountability can become contextual.
They see that enough explanation can sometimes substitute for correction.
Eventually, what leadership still thinks of as exceptions begins functioning as the operating rule.
This is where accountability design starts to weaken.
Accountability becomes less predictable because the relationship among ownership, standards, correction, and consequence is no longer clear.
The question changes from:
What is expected?
to:
What will actually happen if the expectation is missed?
That is a much more consequential question.
Why the Organization Can Still Look Healthy
Tolerance is particularly difficult to diagnose because its early effects can make an organization feel easier to manage.
There are fewer confrontations.
Less immediate disruption.
Relationships remain intact.
Work keeps moving.
Leaders preserve flexibility.
The organization can even feel calmer.
But reduced friction is not always evidence of stronger alignment.
Sometimes people have simply learned what is no longer worth challenging.
High performers compensate instead of escalating. Managers solve around weak standards. Employees calibrate their effort to what actually receives consequence. Leaders explain deviations they once would have corrected.
The system becomes increasingly practiced at carrying the distortion.
That is why organizational entropy often accumulates without a dramatic failure event.
Nothing has to break today.
The organization only has to become slightly less disciplined tomorrow than it was yesterday.
One Practical Diagnostic
Review the last ten situations in which an important standard, commitment, deadline, or expectation was missed.
Do not begin by asking whether each decision was justified.
Ask:
What did the organization learn from our response?
Then examine the pattern.
- Which misses received correction?
- Which received explanation?
- Which exceptions were explicitly temporary?
- Which were never revisited?
- Did the same people repeatedly receive latitude?
- Who absorbed the work created by the accommodation?
- Would another employee reasonably expect the same treatment now?
The purpose is not to eliminate discretion.
It is to discover whether discretion has quietly created precedent.
If you cannot explain why two similar situations produced different consequences, the organization probably cannot either.
If You Change One Thing This Week
Put an expiration rule on exceptions.
When leadership decides that a legitimate circumstance requires temporarily relaxing a standard, record three things:
What exception are we granting?
Why does it exist?
When does it expire or require review?
This preserves judgment without allowing accommodation to become invisible policy.
The goal is not rigid enforcement.
Healthy organizations need discretion. Circumstances differ. Standards themselves can be poorly designed and sometimes should change.
But there is a major difference between deliberately changing a standard and allowing repeated exceptions to change it for you.
One is design.
The other is drift.
Go Deeper
Why Organizations Drift examines how reasonable accommodations accumulate into precedent, how exceptions begin functioning like policy, and why enforcement becomes increasingly difficult after people have adapted to inconsistency.
The deeper problem is not that leaders occasionally tolerate something.
It is that repeated tolerance teaches the system what leadership may never have intended to teach.
Closing Thought
Every organization has written standards.
It also has experienced standards.
The experienced standard is the one people actually learn.
It is created each time leadership decides what deserves correction, what receives accommodation, what gets explained, and what is allowed to continue.
That is why tolerance cannot be evaluated one decision at a time.
One exception may be judgment.
Repeated exceptions become precedent.
Precedent changes expectations.
And expectations eventually become the operating system.
Question for readers: What behavior has your organization tolerated often enough that people may now reasonably believe it is permitted?
Next Wednesday: When exceptions become policy.
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