Imagine growing up in a time when your parents didn’t need to send you a notification saying it was time to come home.
You looked around.
The streetlights had turned on.
That was your cue.
There were no screen-time notifications, calendar reminders, parental tracking apps, or “It’s getting late” alerts. The environment communicated a change, and you understood what it meant.
This everyday experience reveals an important UX principle:
Sometimes, the best instruction is no instruction at all.
The interface simply needs to communicate the right information at the right time.
The environment is already communicating
We interpret signals from our surroundings every day.
A red traffic light tells us to stop. A door handle can suggest whether to push or pull. A walk signal tells us when to cross. A streetlight turning on suggests that evening has arrived.
These cues work because they appear in context and carry familiar meanings.
We don’t need a notification explaining every action. We recognise the signal and decide what to do next.
Digital products can work the same way.
Instead of telling users what is happening through another message, the interface can make the current state visible.
Good UX doesn’t always need to interrupt
Consider these common product messages:
- “Something is happening.”
- “Your session is ending.”
- “You can continue.”
These messages may communicate information, but they can leave users wondering what is actually happening or what they should do.
Now consider a different approach:
Instead of: “Something is happening.”
Show: An upload progress indicator displaying 72%.
Instead of: “Your session is ending.”
Show: A visible session-progress indicator.
Instead of: “You can continue.”
Make: The next action visually obvious.
The principle is straightforward: when users can understand a situation from the interface itself, an additional instruction may be unnecessary.
Understand the relationship between cues and actions
A useful way to think about contextual cues is:
Cue → Interpretation → Action
First, users notice a signal.
Next, they interpret what it means.
Finally, they decide what to do.
For example, when a traffic light turns red, the signal communicates a familiar meaning, and the driver knows to stop.
In a digital product, a progress indicator can communicate how much of a task is complete. A visible button can suggest the next action. A change in interface state can show that something has happened.
For a cue to work well, it should be noticeable, appear in the right context, have a familiar meaning, and help users understand what to do next.
The goal isn’t simply to make the cue louder.
The goal is to make it understandable.
4. Not every cue needs to interrupt
Notifications, alerts, and pop-ups have their place. Sometimes, users genuinely need immediate attention drawn to something important.
But not every change deserves an interruption.
Consider the difference between interruptive and contextual signals.
Interruptive signals
- Notifications
- Alerts
- Pop-ups
Contextual signals
- Progress indicators
- Visible interface states
- Colour or position changes
- Empty states
- Environmental signals
A contextual cue can help users understand what’s happening while allowing them to continue their task.
Before introducing an interruption, consider whether the interface itself can communicate the information.
5. Try the “Do I Really Need a Notification?” test
Before adding another notification, ask:
- What has changed?
- Can users see that change?
- Is the signal shown in the right context?
- Is its meaning clear?
- Does the situation genuinely require an interruption?
If users can understand the change through a clear, contextual signal, a notification might not be necessary.
This doesn’t mean removing all alerts. It means using interruptions deliberately, rather than relying on them to compensate for unclear interfaces.
6. Apply it to your next design
Pick one moment in your product where you currently use a notification, alert, pop-up, or long instruction.
Ask yourself:
Can the interface communicate this on its own?
Try this sequence:
State → Context → Visual cue → Action
Make the current state visible. Place the cue where it matters. Give it a familiar meaning. Make the next action easy to identify.
Then evaluate whether users can understand what’s happening without needing an additional explanation.
The bigger UX lesson
Streetlights didn’t tell us exactly what to do.
They gave us enough information to figure it out.
That distinction matters in product design.
The best interfaces don’t need to constantly direct users through every step. They provide enough context for people to understand the situation and move forward confidently.
Don’t always give users instructions. Give them better cues.
UX Crumbs helps designers turn everyday observations into practical UX lessons, one small bite at a time.
Explore UX Crumbs: https://play.google.com/store/apps/details?id=com.uxcrumbs.mobile&pcampaignid=web_share
Comments