How Users Actually Behave
People don't read, they scan; they don't optimize, they satisfice; they ignore what looks like an ad and never open the manual. Design for the real user, not the ideal one.
Designers imagine a calm, attentive user who reads every label, weighs every option, and follows instructions. That user does not exist. Real users are busy, distracted, half-reading on a phone while doing something else. The gap between the imagined user and the real one is where most usability problems live. Here’s how people actually behave — and how to design for them.
They scan, they don’t read
Users don’t read a page top to bottom — they scan it for the few words that match what they want, in a rough F-shaped pattern: across the top, a shorter pass below, then down the left edge. Everything else is barely seen.
Design for it: front-load the important words. Use headings, short paragraphs, bullets, and bold keywords. Put the critical stuff top-left. A wall of text is a wall the user walks away from.
They satisfice, they don’t optimize
From Steve Krug’s Don’t Make Me Think: users don’t choose the best option — they choose the first reasonable one. They click the first link that looks roughly right and back out if it’s wrong. They’re not reading all your options and comparing; they’re “muddling through.”
Design for it: make the likely-right choice obvious and hard to miss. Don’t rely on users carefully weighing everything — they won’t.
They don’t read instructions
Nobody reads the manual, the onboarding text, the tooltip, or the help doc until they’re already stuck. Users learn by poking at the interface, not by studying it.
Design for it: make the interface teach itself. Sensible defaults, inline hints exactly where they’re needed, and a design that’s discoverable by clicking beat any amount of documentation.
They ignore what looks like an ad
Banner blindness: users have learned to skip anything that looks like an advertisement — boxes in the top banner, the right rail, anything flashy or “promotional.” Tragically, they’ll skip your important message too if it’s styled like an ad.
Design for it: don’t dress real content or key actions up like marketing. Keep them in the content flow, in the interface’s normal visual language.
They miss changes they aren’t told about
Change blindness: if something updates without a clear signal — a total recalculates, an item is added, a filter applies — users often just don’t notice. Their attention was elsewhere.
Design for it: announce changes. Animate the update, flash a toast, move focus, briefly highlight what changed. Silent updates are invisible updates.
They recognize, they don’t recall
It’s far easier to recognize something on screen than to recall it from memory. This is why menus beat command lines for most people, and why “recently used” and autocomplete feel so good.
Design for it: show options rather than making users remember them. Keep choices visible; offer suggestions, history, and defaults.
They run on habit and muscle memory
Users build muscle memory fast — where the save button is, which corner the menu lives in. Move it and you break a habit they didn’t know they had, and it feels like the app is broken.
Design for it: be consistent, within your product and with platform conventions. Consistency is a feature; novelty in the wrong place is a bug.
They will do the “wrong” thing
Users mistype, paste weird formats, double-click, hit back at the worst moment, and click the destructive button by accident. Treating this as user error is a design cop-out.
Design for it:
- Be forgiving of input — accept phone numbers with spaces, trim stray characters, don’t reject a card number because of dashes.
- Prevent the worst mistakes — confirm destructive actions, and better, make them undoable (undo beats a confirmation dialog).
- Write helpful errors — say what went wrong and how to fix it, in plain language, right next to the problem.
They default to the defaults
Whatever you pre-select, most users keep. Defaults carry enormous weight — for better (a sensible default saves everyone effort) or worse (a dark-pattern default tricks people). Choose defaults that serve the user, because they will be accepted.
The one-sentence takeaway
Design for a distracted, impatient, habit-driven human scanning on a phone — not the calm, rational, attentive user in your head.
Do that, and the interface meets people where they actually are. Next, the named laws and principles that turn these behaviors into concrete design rules.
Foundational reading: Steve Krug, Don’t Make Me Think; Nielsen Norman Group (nngroup.com).