Define triggers for mode transitions in both directions…

Define transition triggers for each operating mode that specify when to shift from full to reduced, reduced to minimal, and—critically—from degraded back to full operation.

When This Fires

When designing any multi-mode process (Design three operating modes for every important process) — define all transition triggers before deployment
When a process has been in degraded mode for longer than the disruption justified
When designing recovery protocols (Document five recovery components for every important…) — include mode upgrade triggers
When a process seems permanently stuck at lower capacity despite conditions improving

Common Failure Mode

Defining only downgrade triggers: "When stressed, switch to minimal. When traveling, switch to reduced." But when does minimal switch back to reduced? When does reduced return to full? Without these triggers, every degradation is a one-way ratchet toward lower and lower performance levels. The system degrades naturally but doesn't upgrade without explicit direction.

The Protocol

(1) For each operating mode (Design three operating modes for every important process), define transition triggers in both directions: Downgrade triggers: "When [specific condition] → switch from [current mode] to [lower mode]." Upgrade triggers: "When [specific recovery condition] → begin transitioning from [current mode] to [higher mode]." (2) Make triggers observable (Apply the camera test to triggers — if a camera can't…): "three consecutive full-energy days" not "when I feel better." (3) Include a transition timeline for upgrades: don't jump from minimal to full. Transition minimal → reduced (1 week) → full (1 week). (4) Default rule: if you've been in degraded mode for 2x the duration of the disruption and no upgrade trigger has fired, force a reassessment. The absence of an upgrade trigger might mean the system needs redesign rather than continued degradation.