Saliency

Picture your user for a second. Really picture them. They're not sitting in a quiet white room waiting for your signal. They're on a train. A podcast is playing. Two other apps are buzzing. Their kid wants something. There's an itch on their arm, a billboard out the window, and a half-finished thought about a work email. Into all of that, you want to drop one signal and have it land.

That's saliency: standing out enough from the background to actually get sensed. It's the first thing a signal has to survive, and plenty of good opportunities to engage die right here. Not because the idea was bad, but because the signal never registered over the noise of life.

And here's the tension that runs through this whole chapter. The very thing that makes a signal impossible to ignore is what makes it easy to resent. Push too hard and the user doesn't just tune you out. They reach for the off switch. We've all done it. A smoke detector that shrieks every time you make toast doesn't get tolerated and worked around, it gets the battery pulled, and then it's gone for the one night it actually matters. Your notifications are the toast alarm more often than you'd like to admit. So every strategy here is really one balancing act: loud enough to be noticed, quiet enough to be kept.

A red light in a fair

One idea before anything else, because it trips up almost everyone: saliency isn't a property of your signal. It's relational. Think of a bright red light. In a fair full of lights, it's nothing. In a dark room, you can't look away. Same light. What changed is everything around it. Get that, and half this chapter is already yours.

What makes something stand out splits into two families, and knowing which one you're pulling on saves you a lot of guessing.

The first is bottom-up: the signal against its background. This is the stuff you control, by crafting the signal itself, and the good news is you can mostly measure it. This badge is 25% bigger than its neighbors. This particular red clears the contrast threshold against that grey. It's the raw, reflexive layer, and it works about the same on everyone.

• Contrast is the master lever. A difference from the surroundings in color, brightness, size, shape, or orientation. It's where "pop-out" comes from: drop one yellow dot into a field of blue ones and your eye finds it before you've decided to look. Contrast is measurable and tunable, which is exactly why it's the one you reach for first.
• Motion and change. The eye is wired to catch transients: a sudden appearance, a flicker, something that moves when everything else is still. We evolved to notice the thing that just twitched in the grass, and screens inherited that reflex for free. A single animated element on a static page is almost impossible to ignore.
• Intensity. Plain magnitude: bigger, louder, brighter. The bluntest lever, and the one teams overuse, because it's the easiest to turn up and the fastest to curdle into noise.
• Uniqueness. Not just different, but the only one that's different. This is the von Restorff effect: in a list of similar items, the odd one out is the one people remember. One row styled unlike the other nine pulls the eye and sticks in the memory.

The second family is top-down: the saliency the person brings to your signal. This is the layer people forget, and it's the stronger of the two, but it's people-dependent. Some of it is cultural and learned, so it only works if you know your user. Some of it is baked into all of us by evolution. Either way, you're still the one crafting the signal. What's already there is the receiver, the wiring in the user's head. You don't get to build the radio, but you do get to choose a broadcast it's already tuned to pick up.

• Goal relevance. Whatever you're chasing seems to shine in a different colour from everything around it. You're about to cross the street and suddenly every traffic light pops. You're starving on a busy avenue and the one food sign is the only thing you can see. Hook your signal to a goal the user already has, and it gets salient for free.
• Self-reference. Your own name across a noisy room, your face in a group photo. The brain runs a permanent background scan for anything that's about you. It's the cocktail-party effect: you can be deaf to a whole conversation until someone, three tables away, says your name.
• Emotional and biological pull. Some shapes and signals come pre-loaded. Faces (we find them everywhere, even in power outlets and cars), threats (a snake, a spider, anything lunging at you), a baby's cry, the scent of reward. Evolution tuned us to look at these before we decide to. (Notice this is about looking, about grabbing your attention, not understanding. Understanding is the next chapter.)
• Broken expectation. Surprise is pure saliency. The brain is a prediction machine, and the wider the gap between what it predicted and what actually showed up, the harder the thing grabs. A glitch, an object out of place, a price that's wrong by an order of magnitude.
• Novelty. The close cousin of surprise: something never seen here before. Novelty is context-dependent and a little cultural, what's new to one person is wallpaper to another, which is why it lives down here with the people-dependent levers and not up in the raw stuff.
• Learned value. A signal that earned its importance through past association. The buzz in your pocket means nothing to a visitor from 1980 and means "someone wants my attention" to you, because you were trained, one notification at a time, to care about it.

So the practical takeaway, the one to keep on a sticky note: don't make it "bigger" in the abstract. Make it different from its immediate neighborhood, and if you can, plug it into something the user already carries, a goal, a name, an instinct. Isolation plus relevance beats brute intensity almost every time.

One warning before the list, because I watch it happen in every workshop I run. The second I say "trigger," the room hears "push notification." Maybe a text message. Suddenly everything is a nudge, and the whole conversation shrinks to how many messages we can send before people mute us. So widen the frame now: a trigger is anything that gets the behavior considered. The toothbrush on the sink is a trigger. The doorway to the kitchen is a trigger. And some of the strongest ones come factory-installed, hunger, boredom, the itch to check what that buzz was. Those you don't send. You ride them.

Now the strategies.

The strategies

Contrast

The oldest trick there is, and still the best: make your signal different from whatever surrounds it. The notification badge is the textbook case: a dot of saturated red, often nudged off the tidy grid of icons, near impossible for the eye to skip. And contrast isn't only visual, and it isn't only digital. A jingle that doesn't sound like the room, a thing that moves when nothing else does, a beat of stillness right after a rush. All contrast.

How:

• Read the room first: what's the pattern of noise where your signal lives?
• Break it by adding: one knob from the bottom-up list turned past the background. A more saturated color, a bigger element, motion when all else is still.
• Or break it by interrupting: a sudden gap in a constant hum, a held beat after a fast sequence. Not because silence is a signal, but because the break in the expected pattern is.
• Making something pop without making it ugly or annoying is craft. This is a fine place to lean on a good UI designer.

Alerts, and the channels they ride

The loud version: a push, an SMS, an email, a banner, even a phone call. Alerts don't wait to be discovered, they shove their way into the user's mind, which is exactly their power and exactly their danger. Their quiet superpower is the channel: mail, email, the notifications tray, SMS are doors the user handed you, watched with half an eye for signals they want, so a message on the right door gets noticed almost for free.

How:

• Make the alert borrow from the rest of the chapter: contrast in the sound, relevance in the timing.
• Pick the channel this user actually responds to. Some live in email; some haven't opened it since 2019 but read every SMS.
• Save redundancy across channels for the genuine can't-miss moments, a payment failing, a booking lapsing. Redundancy everywhere is just noise everywhere.
• Some channels are governed by law. Know the rules before you lean on them.

Environmental and ambient cues

Not every trigger has to shout. Your toothbrush on the sink is a trigger: it doesn't buzz, it waits where you'll see it. A billboard, the icon on your home screen, the item left visible in a cart, a progress bar that's simply always there. Quiet, repeatable, and free of goodwill costs, because they demand nothing in the moment. They're just available.

How:

• Put the cue where the behavior should happen, out in the world or right in the flow, and let it sit.
• Lean on repetition: a cue seen many times at low intensity becomes familiar (the mere-exposure effect), and familiar things get spotted faster and trusted sooner.
• Reach for these when the behavior is tied to a place or a routine.

Know your user, and use what they already carry

The people-dependent lever, and the most underused one in the chapter, because it asks you to actually know who you're designing for. You're not making the signal louder, you're tuning it to something the user already carries: a goal they're chasing, a value they've learned, an expectation you can either ride or deliberately break. The payoff is a signal that goes loud without spending a cent of goodwill.

How:

• Map what your user is already looking for, already trained on, already expecting. Then reinforce it (the reorder prompt the moment they pass the store) or break it (surprise grabs hardest when it violates what this user took for granted).
• Before you turn up the volume, try turning up the relevance. The reminder that's invisible at three in the afternoon is impossible to miss the second it matters, and relevance is the closest thing to a free lunch in this whole chapter.

Borrow what the brain can't ignore

Some signals work on almost everyone, no user research required, because they hijack wiring evolution installed long before your product existed. A name. A face. A baby's cry. Sudden motion. Something that simply doesn't belong in the scene. These cut through nearly any noise floor, which is why they're powerful and why they're easy to abuse: a human face looking toward your call to action genuinely pulls the eye. A fake "1 unread" badge pulls it too, and torches your trust the second the user catches the lie.

How:

• When a signal truly matters and you can't count on knowing the user, reach for a near-universal grabber: a face turned toward the thing you want noticed, a flicker of motion, the user's own name, one element that clearly doesn't fit.
• Ration them. If everything uses the panic-grabbers, nothing does.

Switch senses, and protect the channel

Two jobs, one instinct: don't waste attention, and don't burn it. When the eyes are saturated, one more visual element just vanishes into the pile, so move to a sense that's free, a distinct buzz, a short characteristic sound. And above everything, protect the channel you've got. Saliency is a budget, and every loud, irrelevant signal is a withdrawal.

How:

• Keep a rough tally of how much you're asking of each sense and each channel; when one saturates, switch.
• Spend the loud stuff only on what's truly worth it: batch the low-priority signals, let people snooze, cap frequency.
• Watch, like a hawk, for the first mutes and opt-outs. The off switch, once found, almost never gets flipped back.

Watch for: the smoke detector. The second false alarm is the last one anyone listens to.

Is it working? One honest test: of the people who could have noticed your signal, how many reacted? Chase that noticed-rate, and watch its shadow just as closely, the mute rate, the opt-outs. Saliency climbing while mutes climb isn't a win, it's a countdown, and open-rates drifting down month over month are fatigue arriving before anyone complains. And always test in the noisiest real context, never a clean mockup: a button that's obvious in your design file disappears on a sunlit phone on a moving train. The full measuring craft is Chapter 15.

From the field

I worked with a motorcycle oil brand that noticed it was selling less oil than expected in a new market. The reason was simple: riders kept forgetting to change the oil. The boring fixes are a sticker on the frame and asking the rider to compare the odometer against a number they once wrote down. Both are easy to stop seeing. What we played with instead was pure saliency: a small, bright light built right into the oil-filler cap, somewhere you would never expect a light on a bike, blinking for a minute after the engine shuts off. (The device feels the engine's vibration, so it knows the moment you've stopped, and it counts running hours instead of guessing from mileage.) A light where no light belongs, exactly when you're parking and have a free second, is almost impossible to not notice. It carries the same information a sticker would. The difference is that the sticker fades into the bike, and the unexpected light can't.

Worked example

Let me make it concrete with a food-delivery app, because they fight the saliency war on every front at once, and you can name every move.

Walk through any city and you can't miss them: the branded delivery backpacks strapped to a hundred motorcycles, all the same loud color, weaving through grey traffic. That's an environmental cue at city scale, a signal that's simply always there, and it's high contrast at the same time, one bright color against the street. On TV and on billboards, more ambient presence, quietly building mere-exposure familiarity so the brand feels like an old friend before you've ever ordered. Then, right around noon and eight in the evening, the push notification lands, and notice it isn't random. It's timed to the moment you're already getting hungry, which is goal relevance, riding a need you already have rather than manufacturing one. And here's the secret weapon you'll meet properly in the next chapter: over time they quietly resignify an existing trigger, your own hunger, until the feeling itself starts to prompt the app, no notification required.

Count the levers: ambient cues, contrast, mere-exposure, well-timed alerts on the right channel, goal relevance, and a resignified internal trigger. Not one of them is loud on its own. Stacked, they make the app the first thing your thumb reaches for the moment your stomach growls. The notification was just the training wheels. The real win is when your hunger opens the app for them.

At a glance

• Why it matters: if the signal is never sensed, the user's ability and motivation never even get a vote. Saliency is the first barrier, and a lot of good ideas die at it.
• The mechanism: saliency is relational. Bottom-up is the stuff you craft and can measure (contrast, motion, intensity, uniqueness). Top-down is the stuff the user brings (goal relevance, self-reference, instinct, surprise, novelty, learned value).
• The strategies: contrast · alerts & the channels they ride · ambient cues · use what they already carry · borrow what the brain can't ignore · switch senses & protect the channel.
• Key concept: different from the neighborhood, plugged into a goal. Isolation plus relevance beats brute intensity.
• Watch out for: trigger fatigue. Every loud, irrelevant signal moves the user one tap closer to the off switch, and few people ever flip it back.

[image: comic-style - a stick figure in a storm of speech-bubbles, bells, and notifications, with one bright red dot cleanly cutting through the chaos; caption "stand out, but don't get muted"]