Feedback & System Status

Feedback is everything an interface says back after someone acts: the button that depresses, the spinner, the saved tick, the error under the field. System status is the standing answer to "what is happening right now?" — loading, syncing, offline, done. Together they are the half of every interaction the user didn't do themselves, and the half they rely on to know whether their action worked.

Why it decides outcomes

Without feedback, people guess. They press Pay twice, refresh mid-upload, or leave a form they already submitted because nothing told them it went through. Every one of those guesses turns into a duplicate charge, a lost file or a support ticket. Feedback is cheap to build and expensive to omit — which is why visibility of system status is the first of Nielsen's heuristics.

Speed is part of it. The Doherty threshold is the case for responding fast enough that people stay in flow; when the work genuinely takes longer, the honest move is to say so and show progress rather than freeze.

The recurring failure modes

  • Silent waits. A long operation with no sign it started, so it reads as broken.
  • Feedback far from the action. A confirmation that appears in a corner while the user is looking at the button they just pressed.
  • Completion not acknowledged. The task finished, but the screen looks the same as before it started.
  • Errors without a way out. A red message that names the problem and offers no next step — the opposite of what helping users recover from errors asks for.
  • Progress you can't see. A multi-step flow with no sense of how far along you are; the goal-gradient effect is why showing it helps people finish.

The interface should never leave the user wondering whether it heard them.

Small details, large effects

Most feedback lives in micro-interactions — the trigger, the response and the state that proves both happened. The micro-interactions guide covers the anatomy; empty states cover the screen that has nothing to show yet, which is a status message too. For the words inside an error, see the how-to on writing error messages.

Where to go next

Browse how everyday tools handle saving, sending and syncing in the catalog — Slack, Google Drive and Figma all live on status signals. Then continue to interaction design for the actions that produce feedback, and UX writing for the messages that carry it.

7 articles

Information Architecture

Twitch UX Teardown: Which Filters Survive a Tab Change

On Twitch's VALORANT directory, an English + Esports filter set survives the switch from Live Channels to Videos only in part: the Language badge comes along, the Esports chip doesn't, and nothing on the page says so.

TYPENORMLabs · 5 min · October 9, 2026

Web
Gaming
Information Architecture
Twitch UX Teardown: Which Filters Survive a Tab Change

UX Writing

Letterboxd UX Teardown: How the Film Browser Labels Itself

Letterboxd's genre filter reports its result in a plain sentence, "There are 320,379 dramatic films." Elsewhere on the same signed-out browse path, stat icons carry no labels, a weekly ranking drops the word "week" after one click, and one list goes by two names.

TYPENORMLabs · 5 min · October 11, 2026

Web
Media & Entertainment
UX Writing
Letterboxd UX Teardown: How the Film Browser Labels Itself

Information Architecture

Prime Video UX Teardown: One Yellow Bag for Three Different Bills

A UX teardown of Prime Video's signed-out browse flow: rankings and Most Liked labels get a white tag on every tile, while the cost of watching gets one small yellow bag that means Prime, Paramount+ or a rental, and a Free to me filter that comes back empty without saying why.

TYPENORMLabs · 5 min · October 6, 2026

Web
Media & Entertainment
Information Architecture
Prime Video UX Teardown: One Yellow Bag for Three Different Bills

Feedback & System Status

Best Buy UX Teardown: A Shortlist You Can't Take Home

A UX teardown of Best Buy's signed-out headphone search: facets that cut 449 results to 6 in two clicks, a store location the shopper never chose, a shortlist where every visible card is unavailable, and one Add to cart button on the page, for a $399.99 sponsored pair.

TYPENORMLabs · 6 min · September 28, 2026

Ecommerce
Web
Feedback & System Status
Best Buy UX Teardown: A Shortlist You Can't Take Home

Interaction Design

TechCrunch UX Teardown: The Reading Mode That Drops the Date

A UX teardown of TechCrunch's read flow: one switch turns the feed into a dense scan queue and carries the preference into the next section — then removes the timestamp and the content type the returning reader came for.

TYPENORMLabs · 5 min · September 10, 2026

Web
Media & Entertainment
Interaction Design
TechCrunch UX Teardown: The Reading Mode That Drops the Date

Information Architecture

Reuters UX Teardown: A Search That Sorts Like a Wire

A UX teardown of Reuters' signed-out read flow: dependable section fronts, an article page that gives the reader its figures early, and a search that ranks 14,934 matches by the clock, then leaves a Business story at the top of a Technology filter.

TYPENORMLabs · 5 min · September 11, 2026

Web
Media & Entertainment
Information Architecture
Reuters UX Teardown: A Search That Sorts Like a Wire

Interaction Design

Airbnb UX Teardown: A Header That Forgets the Trip

A UX teardown of Airbnb's signed-out search flow: a filter button that counts homes before you commit, one all-fees price carried from histogram to Reserve, hotels at the top of a Homes search, and a header that forgets the trip on the listing page.

TYPENORMLabs · 6 min · September 18, 2026

Traveltech
Web
Interaction Design
Airbnb UX Teardown: A Header That Forgets the Trip

In the TYPENORMSchool library

The whole library →

Explore the map