Protocol
Review exception debt as a portfolio
Ten small exceptions can create one large operating mode nobody intentionally designed.
When it fits
- A system has accumulated several individually reasonable exceptions, waivers, manual bypasses or temporary controls.
When to avoid it
- A portfolio view is editorial systems reasoning based on temporary-change and normalization principles; it is not a claim that every collection of exceptions is unsafe.
Why it matters
Periodically review active exceptions together, not only one at a time. Look for shared controls that several exceptions weaken, repeated reasons that reveal a structural defect, interactions between exceptions and old items that have outlived their context. Close, redesign or consolidate them. The objective is to prevent local accommodations from composing into an unreviewed system state.
Steps
- List all active consequential exceptions and their owners.
- Group exceptions that weaken the same control or depend on the same manual step.
- Flag expired, repeatedly renewed or ownerless items.
- Look for one underlying design problem creating multiple exceptions.
- Close, redesign, or formally approve the resulting operating state.
An example
Three teams each have a temporary manual approval bypass for different reasons. Viewed together, all three remove the same independent review layer and deserve one system-level decision.
Check your result
The review can describe the combined control state created by the active exceptions, not merely justify each exception in isolation.
Keep this limit in mind
- A portfolio view is editorial systems reasoning based on temporary-change and normalization principles; it is not a claim that every collection of exceptions is unsafe.
Evidence and sources
NASA describes normalization of deviance as a gradual shift in which unacceptable practices or standards become accepted after repetition without catastrophic results.
The concept explains one organizational failure pattern; it does not prove that every local deviation is unsafe.
Best Practices for Organizational Resilience in the International Space Station (ISS) Program · Abstract and Appendix B theme 6
OSHA process-safety guidance recommends identifying and reviewing changes before implementation and specifically says temporary changes need a monitored time limit because uncontrolled temporary changes can become permanent.
The guidance is written for hazardous industrial processes; the general exception-control pattern is transferred here by analogy.
Compliance Guidelines and Recommendations for Process Safety Management · Managing Change