Test backup paths during normal operations — untested…
When validating redundancy in human systems, test backup paths during normal operations rather than waiting for primary failure, as untested redundancy often fails precisely when needed due to skill atrophy or outdated procedures.
When This Fires
- After establishing any backup plan, backup person, or fallback procedure
- During quarterly resilience reviews
- When you realize a backup path hasn't been tested since it was created
- Before any high-risk period where primary failure would be especially costly
Common Failure Mode
Assuming the backup works because it was designed correctly: "We have a backup plan." Having a plan and having a working, validated plan are different things. Plans atrophy like skills. The only way to know a backup works is to test it — under conditions similar to when it would actually be needed.
The Protocol
For each backup path in your system: (1) Schedule a test during normal operations — not during a crisis. (2) Temporarily activate the backup while the primary is available as safety net. (3) Verify: does the backup actually work? Are procedures current? Does the backup person have the needed skills? Are the tools functional? (4) Fix any gaps discovered during testing. (5) Repeat at regular intervals (quarterly minimum) — untested redundancy degrades continuously, so validation must be periodic.