Notification Blackout¶
Attention-protection protocol — instantiates Active Goal Shielding
Cuts off the inbound interruption channel for the goal's duration, letting nothing reach you except a short, pre-authorized allow-list.
A Notification Blackout silences the channels through which competing goals reach you — pushes, pings, calls, email badges, chat mentions, the shoulder-tap — for the length of a protected goal window, admitting only an explicit allow-list of true exceptions. Its distinguishing move is that it works on the inbound side: it does not ask you to resist a temptation, it prevents the rival goal from ever announcing itself in the first place, so the interruption never gets the chance to hijack attention. Where a friction mechanism raises the cost of you reaching toward a distraction, a blackout raises a wall against distractions reaching you — binary, time-boxed, and lifted the moment the window ends.
Example¶
A hospital medical-surgical unit keeps making medication errors, and every post-incident review lands on the same cause: nurses are interrupted several times during a single drug pass — a page, a family question, a colleague's request — and each interruption is a chance to miscount or mis-scan. The unit adopts a Notification Blackout for the pass itself. During med rounds the nurse wears a bright "do not interrupt" vest, their pager routes to the charge nurse, and staff are trained to hold non-urgent questions until the vest comes off. The blackout is not total: a rapid-response call or a coding patient still breaks straight through — that is the allow-list.
The outcome is that the nurse crosses the whole pass without a single non-emergency interruption. The competing pulls that used to fragment the task simply never arrive, while the handful that genuinely must arrive still do. Nothing was resisted; the distractions were prevented from ever reaching the point of a decision.
How it works¶
- It targets the channel, not the willpower: identify every route a competing goal uses to signal you — notifications, calls, walk-ups, unread badges — and close each for the window's duration.
- It defines an allow-list up front — the narrow set of interruptions worth breaking focus for (a named person, a system-down alert, a safety event) — so "block everything" never means "block the one thing that actually mattered."
- It routes the blocked traffic somewhere safe — voicemail, a covering colleague, a queue — so nothing is lost, only deferred; that is what makes a hard block tolerable to the people on the other side.
- It ends cleanly with the window: suppression lifts, the queue is drained, and the channels reopen.
Tuning parameters¶
- Blackout scope — how many channels you cut (just phone notifications, versus calls, email, physical access, status-set-to-away). Wider scope protects more but strands more; match it to how interruption-sensitive the task is.
- Allow-list width — how many exceptions may bypass the block. A narrow list protects hardest but risks missing something genuinely urgent; too wide and the blackout leaks until it is decorative.
- Duration — minutes to a full day. Longer blocks protect deep work but accumulate a larger backlog and more social strain on release.
- Failure mode of blocked traffic — silent drop, auto-reply, or delegate coverage. This decides whether senders wait anxiously or know exactly when to expect you.
- Reversibility — a soft "focus mode" you can peek past versus a hard lock (phone in a timed box). Harder is more protective but removes your own judgment mid-window.
When it helps, and when it misleads¶
Its strength is that it removes an interruption before it becomes a decision, which is far cheaper than resisting each one as it lands — and the true cost of an interruption (the reorientation, the dropped thread, the error) is usually much larger than the interruption itself. The aviation sterile cockpit rule, which bars flight crews from any non-essential activity or conversation during critical phases of flight, is the same idea codified into safety regulation.[n1]
Its failure modes cluster around the allow-list, which is the whole ballgame: too wide and the blackout leaks until it protects nothing; too narrow and it can swallow a genuine emergency. Blocked people are left stranded if the blocked traffic is not routed anywhere, turning a focus tool into a reliability problem. And the classic misuse is the standing blackout that never lifts — "do not disturb" worn as a permanent shield against accountability rather than a bounded protection for one goal, which quietly severs you from things you are responsible for. The discipline that guards against this is to bind every blackout to a defined window with a defined end, and to route, never merely drop, whatever it blocks.
How it implements the components¶
access_suppression_boundary— the blackout is the boundary: it specifies exactly which inbound channels are closed for the window and enforces the closure.exception_gate— the pre-authorized allow-list is the standing gate through which only explicit, named exceptions may pass.
It does not raise graduated friction against the goals you reach toward yourself (environmental_friction_layer) — that is Temptation Friction — and it implements only the *standing allow-list; the in-the-moment judgment of whether a specific interruption qualifies is Exception Trigger Card. The window it runs inside (goal_protection_window) is set by Protected Goal Window Schedule.*
Related¶
- Instantiates: Active Goal Shielding — Notification Blackout supplies the inbound-suppression boundary the archetype depends on.
- Consumes: Protected Goal Window Schedule — a blackout runs for the length of a window it does not itself define.
- Sibling mechanisms: Temptation Friction · Exception Trigger Card · Cue Removal or Substitution · Protected Goal Window Schedule · Progress Marker Board · Commitment Device
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Notification Blackout operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it cuts off the inbound interruption channel for the goal's duration, letting nothing reach you except a short, pre-authorized allow-list.
Independent corroboration: The frozen evidence defines Notification Blackout as 'Cuts off the inbound interruption channel for the goal's duration, letting nothing reach you except a short, pre-authorized allow-list', so its operative form is Control, Automation & Runtime.
Nearest alternative: Rule, Policy & Commitment — Notification Blackout includes features of a standing rule, threshold, contractual commitment, or policy constraint governing future conduct, but its defining operation is a live operational control that automatically routes, enforces, adapts, or responds during execution.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Aviation & Aeronautics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Aviation's sterile-cockpit rule is a clear institutional lineage for excluding nonessential interruption during a bounded critical phase.
Related originating lineages:
- Human-Computer Interaction — Digital do-not-disturb controls operationalized blackout for information channels.
- Organizational & Management Science — Protected focus blocks and escalation allowlists provide the workplace governance form.
- Psychology — Attention research supplies the evidence that interruption during a goal episode imposes switching and resumption costs.
Review resolution: Authoritative-source research resolves the primary-origin disagreement. The sterile-flight-deck rule is a direct institutional precedent for excluding nonessential interruption during bounded critical phases; attention research explains its generalization. Origin breadth is limited to formative lineages; present-day applicability is recorded separately as domain_reach=universal.
Attribution caveat: The generalized productivity protocol extends a safety rule far beyond its original operational setting.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
Notes¶
A blackout only closes the inbound door. The competing goals you reach for on your own — opening a news tab, checking a side project — pass straight through it untouched. Closing the outbound door is a different job; pairing a blackout with Temptation Friction is what covers both directions.
[n1] The U.S. Federal Aviation Administration's "sterile cockpit rule" prohibits flight crews from performing non-essential duties or engaging in non-essential conversation during critical phases of flight, notably below 10,000 feet. It is a regulatory instance of blacking out interruptions precisely during the phase where attention errors are most costly. ↩