Radical simplification to 1-2 priorities is an emergency protocol, not a lifestyle — scale back to 3-5 once capacity recovers

Why This Is a Rule

Radical simplification — dropping to 1-2 active priorities — is the behavioral equivalent of triage: sacrificing everything non-critical to save what's most important. Like medical triage, it's the right protocol under emergency conditions (overwhelm, crisis, capacity collapse) and the wrong protocol under normal conditions (where 3-5 priorities is the productive operating range — Work exclusively on the top-of-stack item until it completes or blocks — 3-5 items max, serial execution, not parallel distribution).

The "not a permanent lifestyle" qualifier prevents two failure modes. First, permanent under-commitment: staying at 1-2 priorities indefinitely because it feels comfortable, leaving significant capacity unused and important priorities permanently deferred. Second, simplification as avoidance: using "I'm simplifying" as a cover for avoiding important but uncomfortable work by declaring it non-essential.

The recovery trigger is explicit: when capacity returns (crisis resolves, health improves, cognitive load normalizes), the stack expands back to 3-5. This matches Design three operating modes for every important process: full, reduced, and minimal — degrade fidelity but never lose continuity's three operating modes (full/reduced/minimal) and Define triggers for mode transitions in both directions — especially the return path from degraded back to full's explicit mode transition triggers: you need pre-defined criteria for when to return from emergency mode to normal operation.

When This Fires

• During overwhelm when Priority overload triage: if you could only advance two this week, which two create the most downstream relief?'s triage has reduced priorities to 1-2
• When you've been operating at 1-2 priorities for weeks and capacity has recovered
• When "simplification" starts feeling like permanent avoidance rather than temporary protection
• Complements Design three operating modes for every important process: full, reduced, and minimal — degrade fidelity but never lose continuity (three operating modes) with the priority-specific emergency/recovery cycle

Common Failure Mode

Permanent emergency mode: the crisis that triggered simplification ended two months ago, but you're still running 1-2 priorities because the reduced load feels good. Meanwhile, 3-4 deferred priorities accumulate priority debt (Quarterly priority debt audit: date each deferred Q2 item, estimate cost growth, and schedule the highest-interest-rate debts first). Emergency mode was designed for the crisis; continuing it post-crisis wastes recovered capacity.

The Protocol

(1) When activating emergency simplification (Priority overload triage: if you could only advance two this week, which two create the most downstream relief?), simultaneously define the recovery trigger: "I will return to 3-5 priorities when [specific condition]" — not "when things calm down" but "when I've had three consecutive weeks of full-capacity days." (2) During emergency mode: execute 1-2 priorities with full focus. All others in explicit disposition (Every deferred priority gets one of three dispositions: defer to a named date, delegate to a named person, or declare pause with stakeholder notice). (3) When the recovery trigger fires → begin reintroducing priorities: one per week (or per month for habit-stacked priorities — One new stacked commitment per month maximum — overloading anchor chains converts working infrastructure into brittle sequences) until the 3-5 steady state is reached. (4) If capacity proves insufficient for the reintroduced priority → the original simplification may have been revealing genuine over-commitment rather than temporary overload. Reassess the full stack.