Design a degraded-mode version of every recurring system before it breaks — preserve core function at reduced scope

Why This Is a Rule

Systems engineering uses the concept of "graceful degradation" — when a system is stressed beyond capacity, it sheds non-essential functions while preserving core operations. A nuclear plant under stress doesn't go from full operation to complete shutdown; it steps down through predefined operational levels. Your personal systems need the same design.

Without a pre-designed degraded mode, disruptions (illness, travel, crisis, life events) produce binary outcomes: either the system runs at full capacity or it collapses entirely. Your morning routine either executes all 7 steps or you "skip it today." The exercise habit either hits its full 45-minute target or doesn't happen. The knowledge management practice either follows the complete protocol or goes dormant for weeks. Binary systems are brittle — they survive only as long as conditions stay within their design parameters.

A degraded-mode version preserves the core function — the part that produces the most value — at reduced scope. The morning routine becomes "one minute of journaling and one glass of water." The exercise becomes "a 10-minute walk." The knowledge management becomes "capture one thought." These maintain the habit chain, prevent routine death, and provide a path back to full capacity when conditions improve.

When This Fires

• When designing any new recurring system, workflow, or habit
• When an existing system has died due to disruption and you're rebuilding it — add a degraded mode this time
• When travel, illness, or life changes are approaching and you want to protect existing systems
• Complements When an agent fires below 80% after 30 days, simplify before sophisticating — unreliable agents need reduction, not enhancement (simplify underperforming agents) with proactive degraded-mode design

Common Failure Mode

Designing only the full-capacity version: "My morning routine is meditation (20 min) → journal (15 min) → exercise (30 min) → cold shower → review goals." This works on good days. On bad days (sick, traveling, 4 hours of sleep), none of it happens because you can't do the full version and there's no intermediate option. A 60-second degraded mode (one breath, one sentence, one stretch) would have preserved the chain.

The Protocol

(1) For every recurring system, design three operational modes: Full mode: the ideal version with all components at full scope. Degraded mode: the minimum viable version that preserves core function in 2-5 minutes. Strip to the single most valuable component at its minimum viable size (Start every new agent at under two minutes with zero preparation — automaticity requires low activation energy first). Maintenance mode: the absolute minimum that preserves the trigger-response chain. Even 30 seconds of the behavior prevents habit death. (2) Define the conditions that trigger each mode: full mode = normal conditions, degraded mode = stressed/sick/traveling, maintenance mode = crisis. (3) Write down all three modes — when disruption hits, you won't have the cognitive resources to design a fallback in real-time. (4) The degraded mode should be pre-tested: run it once during normal conditions to verify it's actually executable under stress.