Occasionally run processes in degraded mode…
Practice running processes in degraded mode occasionally even when not required to rehearse partial failure, making the transition familiar rather than frightening when real constraints force it.
When This Fires
- Monthly or every 4th cycle of any process with designed degraded modes
- Before anticipated disruption periods as a rehearsal
- When you notice resistance to mode-switching during actual constraints
- Extends Test degraded modes during calm periods — if they don't… (test during abundance) from initial testing to ongoing rehearsal
Common Failure Mode
Only running full mode and treating degradation as shameful: "A real professional never does the minimal version." This perfectionism makes degraded mode feel like failure, which makes switching to it psychologically difficult, which means you skip the process entirely when full mode isn't possible. The result: binary execution (full or nothing) instead of continuous operation across modes.
The Protocol
(1) For each process with designed degraded modes (Design three operating modes for every important process), schedule occasional practice runs. (2) Once per month (or every 4th cycle), deliberately run the reduced or minimal mode even though you could run full mode. (3) During practice: notice how the degraded mode feels. Is it smooth? Awkward? Does it preserve the core function you designed it to preserve? (4) After practice: note any adjustments needed. The reduced mode might need a small modification, or the transition might need a different cue. (5) The goal is familiarization: when real constraints force mode-switching, the degraded version should feel practiced and comfortable — a legitimate operating mode, not a desperate fallback.