Keep users informed. Always. Even silence is a message — and usually the wrong one.
01 — Where it starts
A lift that doesn't tell you where it's going
You press the button. The doors close. The lift moves. But there's no floor indicator — no display, no number, no sound. Just movement in a metal box.
Do you get out at the next floor and check? Wait and hope? Press every button until something makes sense?
That's what it feels like when a digital product goes quiet. You took an action. Something is happening. But the system isn't telling you what — or whether it worked at all.
The doors close. The lift moves. No floor. No number. No idea where it's headed.
02 — The principle
Always keep users in the loop
Nielsen's first heuristic is deceptively simple: keep users informed about what is happening, with appropriate feedback, within a reasonable time.
That's it. But "appropriate" and "reasonable" do a lot of work in that sentence.
"Appropriate means relevant to the action. Reasonable means fast enough that the user hasn't already assumed something went wrong."
Without visibility
You type. Nothing appears
You'd immediately wonder — is my keyboard working? Did I make a mistake? Is the system receiving this? The moment feedback disappears, the interaction breaks.
With visibility
You type. Characters appear in real time
Instant confirmation. The system is listening. You're in control. You don't have to wonder — you can see it working.
03 — A simple example
The most basic feedback loop in digital products
Think about typing in a text field. Characters appear as you press each key. That's it — that's Heuristic 1 in its most basic form.
Now imagine a system where nothing appears until you press Enter. You'd immediately wonder: is my keyboard working? Did I make a mistake? Is the system receiving my input?
The moment feedback disappears, the interaction breaks. We depend on constant confirmation that our input is being received.
Same field, two experiences. One leaves you guessing. The other shows you it heard every keystroke.
04 — A real failure
My medical insurance experience
Real failure — personal experience
Payment made. Page loaded. Nothing
I recently renewed my medical insurance online. Filled the form. Reviewed everything. Made the payment. Got redirected to a page where I was supposed to receive my updated policy document.
Instead, the page just... sat there.
No loading indicator
No success message
No download button
Not even an error
Naturally, my mind started racing. Did my payment go through? Should I try again? Would I be double-charged if I retried?
To find out — I had to check my bank statement, call my insurance agent, share a screenshot, wait 30+ minutes, and receive my policy two days later.
What it should have said
"Payment successful. We're processing your policy. You will receive it within 24 hours."
One sentence. That's all it would have taken.
05 — The stakes
Silence is never neutral in a product
This isn't just about good design — it's about building trust. Especially in high-stakes contexts, users need to feel confident their action has been received and is being handled.
High stakes, no feedback
Financial transactions
Did my payment go through? No confirmation leads to repeat transactions, support calls, and anxious users who have no idea what happened to their money.
High stakes, no feedback
Healthcare & insurance
Is my form submitted? Is my policy active? In healthcare, uncertainty isn't just frustrating — it creates real-world consequences.
Good visibility
Progress bars & loading states
A simple spinner transforms waiting from anxiety into patience. It signals: the system is working. You did the right thing. Hang tight.
Good visibility
Success confirmations
A tick, a green banner, a "Thank you" — these cost almost nothing to build and deliver enormous psychological relief to the user.
Lack of feedback leads to confusion, repeat actions, and unnecessary support queries — all of which hurt both UX and business performance.
Visibility isn't a nice-to-have. It's how a product earns trust.
06 — The takeaway
Visibility is a form of respect
Visibility of System Status isn't just a UX best practice — it's a form of respect. For the user's time. Their attention. Their trust in your product.
Whether it's a blinking light, a progress bar, a success tick, or a simple "Thank you" — good products always keep users in the loop. Because the moment a user feels left in the dark, the experience is broken — even if everything technically worked.
"A good product doesn't just work. It communicates. And sometimes, one sentence is all it takes."
— The lesson from my insurance renewal
T1
Apply this to your next design
Walk through your product's critical actions — form submissions, payments, uploads, deletions. At each step ask: does the user know something happened? If the answer is "they'll figure it out" — you have a visibility problem.
T2
Up next
H2: Design in a Language They Already Know. How using the right words, familiar metaphors, and real-world references makes products feel natural — without users needing to think twice.