The moments after a click: small UX details that build trust
Feedback states, honest buttons, mobile checks and six named UX laws: the details that decide whether a product feels reliable.

- first-year gain credited to one button change
- $300M
- minimum comfortable tap target
- 44px
- the phone width to test first
- 375px
- UX laws worth naming
- 6
Teams spend most of their design time on what users can do. The moments right after users act get far less attention, and that is where trust is won or lost. Did my click register? Was that saved? Should I try again? Every unanswered question makes a product feel less reliable.
Answer every action
Each action needs three kinds of response. First, instant acknowledgement: the button changes when pressed, a loading state appears. Second, a clear result: a short confirmation, or an error message that says what went wrong and how to fix it. Third, a next step: where to go now. Error messages should never blame the user and never be vague. ‘Card declined. Try another card or check the expiry date’ beats ‘Something went wrong’.
For content that takes a moment to load, skeleton screens (grey blocks in the shape of the coming content) usually feel faster than a spinner, because people can see what is about to appear.
Buttons matter more than they look
UX researcher Jared Spool tells the story of a large online retailer whose checkout asked shoppers to ‘Register’. Many abandoned their baskets. The team replaced it with ‘Continue’ and a note that no account was needed. Purchases rose sharply, and the change was credited with around $300 million in its first year. Google’s Dan Cobley has described a test of 41 shades of blue for links, with the winning shade worth around $200 million a year in ad revenue.
The lesson is not to obsess over colours. It is that small points of friction at decisive moments carry large costs. Practical rules for buttons: make tap targets at least 44 pixels high, use words that describe the outcome (‘Save changes’, not ‘Submit’), and show a pressed and a loading state.
Six UX laws worth naming
- Closure. Let the next card peek into view so people know a row scrolls.
- Figure-ground. Dim the background behind a dialog or focus area.
- Banner blindness. Do not style important messages like adverts; people skip them.
- Parkinson’s law. Tasks expand to fill the effort they ask for; pre-fill what you already know.
- Connectedness. Visually link the steps of a flow so they read as one journey.
- Choice overload. Fewer options up front lead to more decisions. In a well-known jam study by Iyengar and Lepper, shoppers offered six flavours were far more likely to buy than those offered twenty-four.
Test on a small phone first
A design that fits a laptop often breaks on a 375-pixel phone: text that overflows, buttons too close together, tables that scroll sideways, fixed bars covering content and modals taller than the screen. Check every page at phone, tablet and desktop widths before it ships; this site is tested that way.
Give dangerous actions their own design
Deleting, cancelling and overwriting should look different from everyday actions: a distinct colour, a clear description of what will be lost, a confirmation step and, where possible, an undo. One accidental deletion can cost more trust than a hundred smooth sessions earn.
Framework
After every action, answer three questions
- Did it register?Instant feedback: pressed state, spinner or skeleton
- Did it work?Clear confirmation in plain words
- What now?The next step, or how to fix an error
Checklist
Put it to work
Quick quiz
Check what stuck
The famous $300 million button change replaced ‘Register’ with…
Choice overload means…
A skeleton screen is…
Recap cards
Tap a card to check yourself.
Sources and credits
