Priority overload triage: if you could only advance two this week, which two create the most downstream relief?

Why This Is a Rule

When active priorities exceed five, the system has failed its capacity constraint (Work exclusively on the top-of-stack item until it completes or blocks — 3-5 items max, serial execution, not parallel distribution). The triage question — "which two create the most downstream relief?" — applies constraint-based thinking (Only optimize the constraint — verify that improving a loop component would increase total system throughput before investing effort) to the priority list itself. "Downstream relief" means: which priorities, once advanced, would reduce pressure on other priorities or unlock blocked work? This produces a leverage-based reduction rather than an urgency-based or arbitrary one.

The reduction to two is an emergency intervention (Radical simplification to 1-2 priorities is an emergency protocol, not a lifestyle — scale back to 3-5 once capacity recovers), not a permanent state. Two priorities is the minimum viable focus: enough to make meaningful progress while preventing the attention fragmentation that 5+ priorities produce. Once capacity recovers, the stack expands back to 3-5.

The "downstream relief" criterion is the key differentiator from simple urgency triage. Urgency triage keeps the most deadline-pressing items. Downstream-relief triage keeps the items whose advancement produces the most cascading benefit — which may or may not be the most urgent ones. A non-urgent infrastructure task that unblocks three other priorities produces more downstream relief than an urgent but isolated deliverable.

When This Fires

• When active priority count exceeds five and cognitive overload is developing
• During crisis periods when capacity is temporarily reduced
• When everything feels equally urgent and you need a principled reduction method
• Complements Work exclusively on the top-of-stack item until it completes or blocks — 3-5 items max, serial execution, not parallel distribution (3-5 item stack) with the emergency reduction protocol

Common Failure Mode

Urgency-based triage: keeping the two most deadline-driven priorities. These might be isolated deliverables that don't unblock anything else. Downstream-relief triage might select a foundation-building task that has no deadline but whose completion would relieve pressure across four other priorities.

The Protocol

(1) When active priorities exceed 5, stop normal execution. (2) Apply the triage question: "If I could only advance two priorities this week, which two would create the most downstream relief — reduce pressure on other work, unblock stuck items, or produce cascading benefit?" (3) Select two. Everything else gets 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): defer, delegate, or pause. (4) Execute the two selected priorities with full attention (Work exclusively on the top-of-stack item until it completes or blocks — 3-5 items max, serial execution, not parallel distribution serial execution). (5) When capacity recovers → reintroduce deferred priorities one at a time (One new stacked commitment per month maximum — overloading anchor chains converts working infrastructure into brittle sequences one per month) until reaching the 3-5 steady state.