A dot that cannot be cleared is ignored for good
Aliases: sticky badge · permanent unread · uncleared dot
What it is
The contract of a dot or a numeric badge is that the mark disappears after handling. Uncleared means the person already went in, or already tapped “mark as read,” and the corner mark is still there—because the system equated “there is something viewable” with “there is something unhandled,” or because an always-new promo slot lives in the count. Once the dot is a standing decoration of the entrance, it no longer means presence; it means “this product likes dots.” People learn not to look. The ignore is durable: after sensitivity drops, a later true unread cannot call it back.
Why it happens
A presence mark lives on change: nothing-to-something captures attention, something-to-nothing closes a handling loop. If it cannot clear, there is no “to nothing” half; the mark degrades into a birthmark of that icon, and attention stops being allocated to it. This is the same family of habituation as a confirmation clicked through, but it happens on a more peripheral, every-visit location, so the training count is higher. There is also a structural cause: the count includes items the user cannot handle (system notices, someone else’s draft, an expired event). They go in, find nothing they can do, come out with the mark still on, and write “dot = not about me” into the model. After that, every instance of this dot is first assumed irrelevant.
Studying it
Let a badge live for several rounds under “still on after viewing” versus “clears on view,” then insert one new item that really needs handling.
Independent variables: clear rule (open-to-clear / explicit read / never clears on view), whether unhandleable items are mixed in, whether the mark is a dot or a number. Dependent variables: whether that inserted item is noticed, time from appearance to enter, and whether people describe the mark as “always there.”
In the lab the badge is a stimulus and will get an extra glance. A harder test parks it on a sidebar that is not the primary task, with the primary task being document editing, and watches who still stops for the sidebar dot.
Where it stops holding
A state like “an update is available” remains true after the user declines; the mark may stay, but it should become a dismissible entrance or drop into settings, not masquerade as unread. Unread mail still sitting in the inbox should not clear merely because the nav was opened—that is an unhandled object, not an uncleared mark. Uncleared means the user has done everything this mark can ask, and it remains. A number moving from 3 to 2 is a partial honoring of clear; a 3 that never moves is dead.
Applying it
- Write a clear condition for every badge: viewed, explicitly read, or an action completed on the object. No condition, no mark.
- Count only items the current user can handle; do not mix promo slots and inert system messages into unread.
- Offer “mark all read” and actually clear; if it still shows after that, do not ship the entrance.
- Verify by walking the path the product considers handling, then checking whether the dot remains. If it does, ask a week-later user what the dot means. “It’s always there” means ignore has completed.