Principle
Design recovery for the error you cannot prevent
Some resilience belongs after the mistake, not only before it.
Before you use it
- Use when
- The team keeps trying to eliminate every possible human or system error before release.
Keep this limit in mind
- Recovery design does not excuse avoidable unsafe actions; use prevention where it is stronger and cheaper.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
For plausible residual errors, design fast detection, bounded impact and a clear recovery path. Ask how the system notices the wrong state, how far it can spread, and how to restore a known-good state. Prevention and recovery should be reviewed together.
An example
A bulk update has post-write reconciliation, batch limits and a replayable correction file in addition to pre-write validation.
Check your result
A plausible residual error has a defined detection and recovery path instead of requiring perfection.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingDesign recovery for the error you cannot prevent
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaStop the process when the unexpected state invalidates the safety assumptions
More from this collection
Design routine work so ordinary human slips do less damage
Do not discipline away a system defectEvidence and sources
Human-factors engineering includes resilience: detecting and mitigating unexpected events before they worsen rather than assuming every error can be prevented.
Recovery mechanisms complement prevention; they do not justify avoidable unsafe design.
Human Factors Engineering · Resiliency efforts
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.