Test degraded modes during calm periods — if they don't…
Test degraded operating modes during periods of abundant resources to verify they preserve core function, because modes that fail under calm conditions will certainly fail under stress.
When This Fires
- After designing any degraded or minimal operating mode (Design three operating modes for every important process)
- During calm, resourced periods — schedule deliberate tests of your fallback modes
- Before anticipated disruptions (upcoming travel, known busy periods, seasonal challenges)
- When you've never actually run a degraded mode you designed — it's untested infrastructure
Common Failure Mode
Designing degraded modes on paper and never testing them: "If I get sick, I'll do the minimal version." When sickness arrives, the minimal version has never been practiced, the trigger is unfamiliar, and the reduced scope feels wrong because you've only ever done the full version. The degraded mode dies on first contact with actual stress.
The Protocol
(1) After designing a multi-mode process (Design three operating modes for every important process), schedule a test of each degraded mode during a normal week. (2) Run the reduced mode for one full cycle. Does it preserve core function? Does it feel executable? Does the trigger work? (3) Run the minimal mode for one full cycle. Same questions. Can you actually do it in under 5 minutes? Does it maintain the behavioral chain? (4) Note any design problems and fix them now, while you have the cognitive resources to redesign. (5) After testing, you have verified degraded modes that you know work. When disruption arrives, you switch to a mode you've already practiced — not a theoretical design you've never tried.