Every deferred priority gets one of three dispositions: defer to a named date, delegate to a named person, or declare pause with stakeholder notice

Why This Is a Rule

Unresolved deferred priorities consume cognitive bandwidth through the Zeigarnik effect: uncompleted tasks occupy working memory until explicitly resolved. Priorities that are "deferred" without a specific disposition remain cognitively active — your brain keeps returning to them because their status is ambiguous. Three explicit dispositions close the Zeigarnik loop by converting ambiguous deferral into specific, resolved commitment.

Defer to a named date: "This priority resumes on March 15." The date provides closure — your brain can release the item because it has a scheduled return. Delegate to a named person: "Sarah is handling this through Q2." The named person provides closure — the priority has an owner, just not you. Declare pause with stakeholder notification: "This is paused. I've told the stakeholders." The notification provides closure — the affected parties know, and the social obligation is discharged through communication rather than through continued execution.

Without explicit disposition, deferred priorities linger as "I should get back to that" background noise — consuming cognitive bandwidth without receiving attention, the worst of both worlds.

When This Fires

• After any triage reduction (Priority overload triage: if you could only advance two this week, which two create the most downstream relief?) 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 it completes or blocks — 3-5 items max, serial execution, not parallel distribution)
• Complements Did you choose to defer or fail to negotiate? Strategic deferral preserves sovereignty, silent deferral surrenders it (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: output format, explicit expectations, and return protocol — ambiguous handoffs create bottlenecks). 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.