Every deferred priority gets one of three dispositions

For each priority you defer during simplification, assign one of three explicit dispositions: defer to a named date, delegate to a named person, or declare pause with stakeholder notification.

When This Fires

After any triage reduction (Priority overload triage) when priorities are being simplified
When overwhelm requires temporary scope reduction
When any priority needs to come off the active stack (Work exclusively on the top-of-stack item until…)
Complements Did you choose to defer or fail to negotiate? Strategic… (strategic vs silent deferral) by ensuring all deferrals are explicit

Common Failure Mode

Undispositioned deferral: "I'll get back to that." When? To whom? Who knows? The priority sits in cognitive limbo — not active enough to receive attention, not resolved enough to stop consuming background bandwidth. Each of the three dispositions closes the loop by answering the specific question (when, who, or what stakeholders were told).

The Protocol

(1) For each priority being deferred, assign exactly one disposition: Defer: "This resumes on [specific date]." Put it on the calendar. Delegate: "This goes to [specific person] who will own it through [period]." Communicate the handoff (Three-component handoff spec). Pause: "This is paused. I will notify [specific stakeholders] that it's on hold." Send the notification now. (2) Write the disposition next to the deferred priority. The written record closes the Zeigarnik loop. (3) No fourth option: "I'll figure it out later" is not a disposition. It's the undispositioned state this rule exists to prevent.