The red dot always wins the wrong fight

There’s a small, slightly embarrassing experiment worth knowing before you design your next notification. People were offered a choice between two tasks. One was labelled urgent — a countdown, a closing window — but paid a smaller reward. The other had no time pressure and paid more. The catch was that both rewards were shown up front, so the “urgent” one was, plainly, the worse deal. People took the urgent task anyway. Researchers called it the mere-urgency effect: the sense that something must be done now pulls us toward it even when we can see it isn’t worth as much.

The word doing the work there is mere. Not real urgency — the manufactured kind. A deadline that exists only because someone attached a clock to it. Our attention treats the clock as if it were evidence about value, and it usually isn’t.

I think about this every time I’m tempted to add a red dot.

A badge is a manufactured deadline in the shape of a dot. It says: something is unresolved, and resolving it is available right now. That’s a remarkably strong pull, because it borrows two mechanisms at once — the itch of an open loop, and the felt urgency of a thing you could close in one tap. The problem is that the dot has no idea whether what’s behind it matters. A friend request, a terms-of-service update, and “your payment failed” all get the same crimson circle. To the visual system they’re identical calls to action. To the user’s life they are not remotely equal.

So the failure mode isn’t that badges don’t work. It’s that they work too indiscriminately. Ship enough of them and you train a reflex that clears dots rather than a habit that does valuable things. The urgent-trivial beats the important-untimed, screen after screen, until the user’s attention is being spent by whoever shouts, not by whatever helps.

The design move is not “never badge.” It’s to treat urgency as a scarce currency you spend on things that are actually time-sensitive to the user — a payment that will fail, a draft that will expire, a person waiting on a reply. When a signal genuinely maps to a closing window, urgency is honest and helpful; it points attention at the thing that will cost the user something if ignored. The dishonest version is urgency applied to keep engagement up: the “3 new” counter on a feed, the badge that reappears the instant you clear it. Those borrow the same reflex and give nothing back, and users eventually learn the tell — the badge that’s always there stops meaning anything, and then your real alerts inherit its noise.

A practical test I’d run on any notification: if you removed the urgency cue, would the user still want to know this, on their own schedule? If yes, it doesn’t need the red dot — a quiet, dismissable marker respects that it matters without pretending it’s on fire. If the honest answer is “they’d only act because it feels pressing,” you’ve found a manufactured deadline, and shipping it spends trust you’ll want later.

The uncomfortable part is that manufactured urgency works in the short run — that’s exactly why it’s a trap. The metric moves, so it feels validated. But you’re not creating value, you’re reallocating a fixed pool of attention toward whatever you made loudest. Do it to the trivial and you’ve taught your most valuable users to associate your product with noise. Reserve it for what’s truly timely, and the rare red dot keeps the one thing a notification is for: meaning it when it says now.