Your brain processes a button in 50 milliseconds. It decides whether to click in the next 100. The difference between an interface that feels obvious and one that makes users hesitate lives in that gap - and it's governed by principles discovered in psychology labs decades before the web existed.
This handbook maps 15 of them to practical interface decisions. Not as trivia, but as design constraints that predict how humans actually parse visual information and make choices under cognitive load.
The Ones That Shape Every Click
Fitts's Law explains why mobile navigation moved to the bottom of the screen. The time to acquire a target is a function of distance and size. Thumbs live at the bottom. Putting primary actions there cuts acquisition time by 40% compared to top-aligned navigation. This isn't preference - it's biomechanics.
Hick's Law is why feature-rich dashboards feel paralysing. Decision time increases logarithmically with the number of choices. Every additional button adds cognitive overhead. The fix isn't hiding features behind menus - that just moves the problem. It's structuring decisions into sequential steps, so users face two clear choices at a time instead of twelve ambiguous ones.
Miller's Law - the seven-item working memory limit - shows up everywhere designers don't expect it. Navigation menus with nine top-level items force users to chunk or forget. Phone numbers are formatted in groups for this reason. Checkout forms that ask for twelve pieces of information on one screen exceed working memory capacity. Users don't forget because they're careless - they forget because the interface demanded more simultaneous recall than human cognition supports.
The Gestalt Principles That Build Visual Logic
Proximity, similarity, continuation, closure - these aren't aesthetic choices. They're how the visual cortex groups information pre-attentively, before conscious thought kicks in. A form with inconsistent spacing between fields forces users to consciously parse which label belongs to which input. Consistent spacing makes the relationships obvious at a glance.
The Law of Similarity means that elements sharing visual properties are perceived as related. If your primary action button and your delete button look identical except for colour, you're relying entirely on text labels to prevent errors. Users will misclick. Not because they didn't read - because their visual system made the grouping decision faster than reading happens.
Figure-Ground separation determines whether users can find what they're looking for. If a modal dialog doesn't have sufficient contrast with the background, users experience it as part of the page content instead of a distinct layer. They'll try to interact with the dimmed background content, get confused when it doesn't respond, and abandon the flow. The fix is obvious once you know the principle: stronger visual separation makes the layer hierarchy explicit.
Principles That Shape Memory and Expectation
The Peak-End Rule explains why onboarding flows matter more than you'd think. Users remember experiences based on their peak moment and final moment, not the average quality of the whole interaction. A clunky signup flow followed by a delightful first-use experience leaves a positive memory. A smooth signup followed by a confusing dashboard leaves a negative one. This has direct implications for where you invest polish.
Serial Position Effect - users remember the first and last items in a list better than the middle - shapes everything from feature placement to content ordering. If you're listing product benefits, the strongest claims go first and last. The middle gets forgotten. If you're building a navigation menu, the most important sections go at the top or bottom, never buried in the middle.
Von Restorff Effect: distinctive items are remembered better. This is why call-to-action buttons break the colour scheme. But it only works if one thing stands out. If everything is distinctive, nothing is. The handbook shows examples of interfaces that violate this - three different button colours, competing for attention, all losing.
Where Theory Meets Practice
The value here isn't memorising laws. It's recognising them in the wild. When a user says "I didn't see the button", that's often Banner Blindness or Inattentional Blindness - their brain filtered it out because its position or styling matched learned patterns for ignorable content. When they say "I didn't understand what to do next", that's usually a Cognitive Load problem - too many simultaneous decisions or unclear mappings between actions and outcomes.
These principles don't tell you what to build. They tell you what will happen when humans use what you built. The handbook walks through each principle with before/after examples - interfaces that violate the principle and the redesign that aligns with it. The difference is measurable: task completion rates, error rates, time-on-task all improve when design decisions align with cognitive constraints.
For designers, this is the foundation beneath aesthetic judgment. For developers building interfaces, it's a checklist that catches usability issues before user testing. And for anyone arguing about design choices, it's a shared vocabulary grounded in evidence instead of preference.
The web is cognitive infrastructure now. Billions of people use it under time pressure, cognitive load, and distraction. Interfaces that respect how human perception and memory actually work don't just feel better - they fail less. That's not polish. That's engineering.