Grade urgency by consequence and how soon it lands
Aliases: urgency matrix · time criticality · missed-cost ranking
What it is
Urgency answers whether a notice should take attention now. The grade is a product of two quantities: what happens if it is missed (consequence) and how soon that consequence materializes (time criticality). A door unlocking, a one-time code that dies in five minutes, and a like on a photo can all be sent with the same commercial appetite; only the code is both time-bounded and costly to miss. Urgency is not the sender's desire, and not how loud or red the surface is.
This entry is only about the criterion that places an item in a tier. It does not ask whether the interrupt will wreck the task in progress, and it does not ask whether false alarms will later numb people to real ones.
Why it happens
Attention is rationed, so the system must rank. People rank by missed cost times the response window: high cost and a short window deserve an immediate cut-in; high cost with a long window can wait for a gap; a short window with trivial cost only manufactures hurry. If senders substitute click-through or revenue for those axes, the ranking diverges from the user's loss function—countdown sales occupy the top tier, account anomalies sit in a silent queue.
Tiers have to be perceptible. If banner-plus-sound is used for every grade, the taxonomy exists in a config file and nowhere in the experience. People calibrate to whatever has recently looked like "highest." Harmless items in that slot teach a lower weight for the next genuinely costly event.
Studying it
Use ranking and trade-off tasks, not "is this important?" ratings. Have people sort the same set into now / later / ignorable, then trade "missed by ten minutes" against "missed by a day."
Independent variables: consequence class (safety, money, social, marketing), deadline window, sender identity. Dependent variables: sort agreement, mismatch with the system's default tier, share of items labeled top-tier.
In the lab, "important" often becomes a moral claim (family always wins). In logs, opens follow the task of the moment. Keep stated preference and in-situ opens apart. High open rate is not high urgency—promotions can be opened often with near-zero miss cost.
Where it stops holding
Mandated public alerts (earthquake, civil defense) do not use a product's consequence matrix; channel and presentation are regulated. On-call, ops, and trading floors define latency in seconds; a consumer three-tier scheme is too coarse. Social consequence is idiosyncratic: a like is deferrable for one person and live coordination for another. When event type alone cannot predict the grade, default low, not high.
Applying it
- For each type, write the reversible loss of missing it for an hour and the deadline by which it must be handled. Only types high on both get heads-up or sound; the rest go to the shade or an inbox.
- Keep marketing, achievements, and announcements off the urgent channel even when the copy includes a countdown.
- Watch the top-tier share: if more than half of a week's pushes sit there, change the classification rules before changing motion.
- Verify by sampling twenty recent sends and having someone outside the grading team re-rank them on consequence × latency. For every mismatch, record which axis was wrong and change only that axis.