A badge that never clears dulls sensitivity to new items

What it is

A badge uses appearing to say there is new unfinished work. If it stays lit for a long time and does not clear on handling or viewing, people take the light as that item’s default skin. After habituation, genuinely new items stack on a dot that is already on, and the navigation no longer has a “just lit up” change to catch. The problem is not that the number is large. It is that the signal no longer has an on and an off.

Why it happens

Vision is sensitive to a mark that appears, and habituates to a mark that remains. A red dot is an event on day one and part of the icon by week three. Habituation has two roads: the work truly never gets cleared (an inbox forever at 400), or it was handled and the system still does not extinguish (already-read still badged). The first is workload beyond clearing capacity; the signal is still honest, but it has failed as “new” and needs another device (inner sort, a digest). The second is the signal lying: the off never happens, and people learn to ignore.

Once ignore is learned, later lights are hard to save, because that item in the choice field has been filed under “always like that”. Products that use badges as growth hooks habituate faster — people quickly find no corresponding unfinished object inside, and then also turn off attention to honest badges.

Studying it

Watch across sessions: days the badge stays lit, whether people still change which station they enter because of it, and whether new arrivals during the lit period are still reported in speech. Independent variable: clear rule (clear on view / clear on handle / never). Dependent variables: decay across days of entries caused by the badge, and missed reports of “I did not notice more arrived”.

A single lab task will not show habituation; it has to run by day. A marketing dot unrelated to handling should decay faster, and can serve as a control.

Where it stops holding

Safety alerts and system failures that must stay visible until repaired pay habituation as a cost; they must not auto-clear for sensitivity’s sake — and they belong on a banner more than on a nav badge. An honest huge inbox will fail as “new”; it can flash only when something arrived since last leave. A user-driven “mark as unread” should bring the badge back; that is not a habituation failure.

Applying it

• Write a clear-off condition for each badge kind: viewed, handled, or “no new arrival since last visit”. No off condition, no nav badge.
• Marketing and growth hints are one-shot marks that must expire; do not occupy the unfinished-work channel.
• For an honest large pile, give a transient “new arrivals” instead of expecting the same always-on number to still be an event.
• How to check: across several days, watch the rate of entries caused by the badge. When it matches no-badge, habituation holds. A badge still on after handle or view is a signal that does not turn off. New arrivals the user describes as “it was always like that” are changes not caught as events.

Related

• Within the group: E5.17.1 A nav badge signals unfinished work inside that destination · E5.17.2 Large counts on badges need a compacted display · E5.17.4 Badge logic must match the actual state exactly
• Adjacent: E6.12 When Notices Dismiss · E5.02 Bottom Tab Bars
• Search terms: habituation · stale badge · notification fatigue