Notification Tier System¶
Routing system — instantiates Attention Budgeting
Classifies every signal into a graded lane — interrupt-now, batch, digest, background-log, or suppress — so each notification arrives with the intensity its class deserves.
A Notification Tier System budgets attention by sorting, not capping. Every signal is assigned to one of a small set of graded lanes — interrupt-now, batch-for-later, daily-digest, silent background-log, suppress — and each lane delivers with a matching intensity, so a critical event buzzes the phone while a routine update accretes quietly into a digest nobody has to watch. Its distinctive feature is that every signal gets a lane and the lane determines its loudness; there is no global ceiling on how many notifications exist, only a rule that maps each one to the delivery mode its class warrants. This is what separates it from a quota: it does not ration interrupt-rights, it grades them, ensuring the loudest channel is reserved for what truly earns the interruption and everything else recedes to a lane that fits.
Example¶
A field-service platform used by 300 technicians sends everything the same way — a new job assignment, a part-back-in-stock note, a company newsletter, an emergency dispatch all arrive as identical phone buzzes. Technicians, buzzed forty times a shift, have turned notifications off entirely, so emergency dispatches now get missed. The platform introduces a tier system. Emergency dispatch → interrupt-now, full-screen, sound. New job assignment → batched, delivered at natural breaks. Inventory and status updates → rolled into an end-of-shift digest. Newsletters → silent in-app inbox. Anything with no action attached → suppressed. Every message still exists; what changed is that each now arrives in a lane matched to how much it deserves to interrupt. Technicians turn notifications back on, because the buzz means something again — and the emergency dispatch, alone in the top lane, gets seen.
How it works¶
- Define the lanes. Establish a small, ordered set of delivery modes, from full interrupt down through digest to silent log and suppress, each with a distinct intensity.
- Classify every signal. Map each signal type to a lane by a stated rule — time-sensitivity, consequence, whether a human must act — so placement is principled, not arbitrary.
- Match delivery to lane. The lane dictates how the signal appears; the top lane is loud and reserved, lower lanes get progressively quieter until the bottom lane is invisible-until-sought.
- Bind each lane to a handling expectation. Each lane implies what the recipient does with it — act now, review in batch, skim the digest, ignore unless searched — so the tier carries a behavior, not just a volume.
The system's job is placement: get every signal into the right lane so the loud lane stays credible and nothing important lands in a silent one.
Tuning parameters¶
- Number of tiers — more lanes fit each signal precisely but burden users with a taxonomy to learn; fewer lanes are simple but blunt.
- Interrupt-lane admission — how strict the rule is for the top lane. Strict admission keeps interrupts meaningful but risks demoting a real one; loose admission slides back toward everything-buzzes.
- Batch cadence — how often the batch/digest lanes flush. Frequent flushing feels responsive but nibbles at focus; infrequent flushing protects attention but delays middling-importance items.
- Per-user override — how much recipients may re-tier signals themselves. User control fits individual context but can let someone mute a lane they shouldn't.
- Default lane — where an unclassified new signal lands. A quiet default is safe against noise but can bury a novel-but-important signal until someone re-tiers it.
When it helps, and when it misleads¶
Its strength is that it preserves all the information while fixing its intensity, which is the right move when signals genuinely differ in urgency and none can simply be deleted. By reserving the loud lane, it protects the credibility of an interrupt — the property that erodes when everything is equally loud and recipients habituate, tuning out even the alarms that matter.[n1] A well-tiered stream keeps the top lane rare enough to still command a response.
It misleads when tiering is treated as a substitute for reduction: adding elaborate lanes without ever suppressing anything just reorganizes the noise, and if too many signal types creep into the interrupt lane, the hierarchy flattens and the fatigue returns under a fancier taxonomy. The classic misuse is a "high-priority" lane that becomes a dumping ground because every team insists its signal is high-priority. The guarding discipline is to keep the top lane genuinely scarce, audit which signals actually get acted on and demote the ones that don't, and remember that a tier system sorts loudness — it does not, by itself, cap total volume, so it pairs naturally with a mechanism that does.
How it implements the components¶
salience_hierarchy— the graded lanes are the salience hierarchy made operational: each tier delivers at a set intensity, so foreground signals look and behave like foreground and background ones recede.interruption_policy— the rule mapping signals to lanes is the policy for what may interrupt now versus wait, digest, or stay silent.action_link— each lane carries a handling expectation, tying its signals to a behavior (act, review, skim, ignore).
It does not impose a numeric cap on total interrupt volume (attention_budget, overload_signal) — that's Alert Budget, which rations rather than sorts; a tier system can leave the loud lane crowded unless a budget bounds it.
Related¶
- Instantiates: Attention Budgeting — Notification Tier System is the routing instantiation: it grades every signal into a lane matched to how much it should interrupt.
- Consumes: pairs naturally with Alert Budget, which caps the volume the top lane is allowed to carry.
- Sibling mechanisms: Alert Budget · Dashboard Triage View · Attention WIP Limit · Quiet Hours Policy · Watch Rotation · Executive Attention Review · Editorial Priority Calendar · Focus Block Schedule
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Notification Tier System operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it classifies every signal into a graded lane — interrupt-now, batch, digest, background-log, or suppress — so each notification arrives with the intensity its class deserves.
Independent corroboration: The frozen evidence defines Notification Tier System as 'Classifies every signal into a graded lane — interrupt-now, batch, digest, background-log, or suppress — so each notification arrives with the intensity its class deserves', so its operative form is Control, Automation & Runtime.
Nearest alternative: Rule, Policy & Commitment — Notification Tier System 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: Human-Computer Interaction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Notification and interaction design developed multiple delivery lanes—interrupt, batch, digest, background, suppress—matched to urgency.
Related originating lineages:
- Computer Science & Software Engineering — Messaging and monitoring systems implement routing, batching, and suppression behavior.
- Organizational & Management Science — Operational severity and escalation policies contribute the tier definitions.
- Psychology — Attention and habituation research explains why the highest-intensity lane must remain rare to preserve response.
Review resolution: Both independent reviews agree on primary origin human_computer_interaction; reconciliation resolves alternate_origin_disagreement. Formative alternate lineages retained: psychology, computer_science, organizational_management. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis describes the historical relationship among lineages. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=true preserves the reviewers' boundary judgment.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Habituation — the decline in response to a stimulus that is repeated without consequence. When notifications of all kinds arrive at the same intensity, recipients habituate to the whole stream, which is why grading delivery so the top lane stays rare is what keeps a real alert from being tuned out. ↩