[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757RWMADV23BYD631HJ3TK2":3,"skill-same:01M757RWMADV23BYD631HJ3TK2":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M757RWMADV23BYD631HJ3TK2","laws-of-ux-and-psychology",null,"Reference-grade catalogue of the attributed cognitive laws behind interface design (Fitts, Hick-Hyman, Miller, Jakob, Tesler, Postel, Doherty, Peak-End, and the behavioral-econ cluster) — each with origin, a concrete UI application, the design rule, and the pitfall.","jpoindexter\u002FVanta","jpoindexter","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2729617?v=4","01M72VRRYY1CP7RPF3B7GHH0CR","01M757GWDBT6RD147ZZ79N4MEX",4,"MIT","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fdesign-system-skills\u002Flaws-of-ux-and-psychology\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: laws-of-ux-and-psychology\ndescription: Reference-grade catalogue of the attributed cognitive laws behind interface design (Fitts, Hick-Hyman, Miller, Jakob, Tesler, Postel, Doherty, Peak-End, and the behavioral-econ cluster) — each with origin, a concrete UI application, the design rule, and the pitfall.\ntags: [ux, psychology, cognition, laws-of-ux, principles]\n---\n# Laws of UX & Cognitive Principles\n\nThese are not style opinions. Each \"law\" is a named finding from perceptual psychology, cognitive science, or behavioral economics that constrains how *every* human uses *every* screen — desktop, mobile, watch, voice, kiosk. Jon Yablonski's *Laws of UX* (lawsofux.com, 2020) collected the design-facing subset; the originals trace to the researchers credited below. Cite the source when you invoke a law in a design review — \"this fails Fitts\" lands harder than \"the button feels small.\"\n\nRead each law as a fixed five-part block: **Origin** (who\u002Fwhen), **Principle** (the mechanism, with the math where it exists), **In the UI** (one concrete control or screen), **Implication** (the general rule you derive), **Pitfall** (the failure mode). Keep \"In the UI\" and \"Implication\" distinct: the first is an example, the second is the rule.\n\nThe laws also *combine* — most good interactions satisfy several at once and most bad ones violate a cluster. A fast, optimistic submit serves Doherty *and* Flow; a forgiving, system-parsed input field serves Postel *and* Tesler *and* Recognition-over-recall. When two laws appear to conflict (Hick says fewer choices, but Jakob says match the conventional five-tab bar users expect), Jakob usually wins for plumbing and Hick for content — convention is a learned default that costs nothing, novelty is the expensive part.\n\n---\n\n## 1. Targeting & decision laws (the geometric ones)\n\n### Fitts's Law\n- **Origin:** Paul Fitts, 1954. Formalized in *The information capacity of the human motor system*.\n- **Principle:** Time to acquire a target = `T ≈ a + b·log₂(2D\u002FW)`, where `D` = distance to target, `W` = target width along the motion axis. Acquisition time grows *logarithmically* with distance and *shrinks* as the target gets bigger. Doubling size helps far more than the formula's modest log on distance suggests in dense UIs.\n- **In the UI:** A primary CTA rendered 48px tall and placed near the user's current focus is hit fast; the same action as a 16px text link in a far corner is slow and error-prone. Screen *edges and corners* have effectively infinite width (the pointer stops dead) — macOS menu bar, Windows Start corner, the right-click context menu spawned *at* the cursor (`D≈0`).\n- **Implication:** Make important, frequent targets big and near. Anchor destructive or rare targets far and small. Exploit edges, corners, and the pointer's own position for the loudest actions.\n- **Pitfall:** Tiny icon-only buttons crammed together (toolbar of 24px glyphs at 4px gaps) — every click is a coin-flip. Also: a big *visual* button with a small *hit area* (padding outside the clickable region) silently breaks the law.\n\n### Hick's Law (Hick-Hyman Law)\n- **Origin:** William Edmund Hick **and** Ray Hyman, 1952 — independent papers, jointly named. Don't drop Hyman.\n- **Principle:** Decision time rises logarithmically with the number of equally-probable choices: `RT = b·log₂(n + 1)`. Each doubling of options adds a roughly constant slice of deliberation, not a linear pile.\n- **In the UI:** A checkout with one obvious \"Pay\" button decides instantly; a settings page dumping 40 toggles at once stalls the user. Chunking the 40 into 6 labeled groups, or revealing advanced options behind a disclosure, restores speed.\n- **Implication:** Reduce or *categorize* choices. Use progressive disclosure, smart defaults (a pre-selected sensible option removes the decision entirely), and grouping. Highlight a recommended path so the user can skip the comparison.\n- **Pitfall:** Over-applying it into death-by-wizard — splitting one coherent choice across ten one-question screens adds navigation cost and hides context. Hick's targets *count and grouping*, not \"fewer screens always.\"\n\n---\n\n## 2. Memory & cognition laws\n\n### Miller's Law\n- **Origin:** George A. Miller, 1956, *The Magical Number Seven, Plus or Minus Two*.\n- **Principle:** Working memory holds ~7±2 **chunks**, not items. The number is about *units of meaning*, and a chunk can be large (a familiar acronym, a grouped phone segment). **Nuance\u002Fmyth:** \"7\" is widely misquoted as a hard cap on menu items or nav links — it is not. Cowan's later work (2001) refines the real span to ~4 chunks. The usable lesson is *chunk and group*, not \"never exceed seven.\"\n- **In the UI:** A phone number shown as `+1 (415) 555-0132` is four chunks and trivially held; `+14155550132` is twelve digits and slips. Card numbers grouped in 4s, OTP fields in segments, nav grouped into labeled sections.\n- **Implication:** Format and group information into meaningful chunks so the user holds a structure, not a stream. Don't make the user keep facts in their head across steps — show them on screen (recognition over recall, §5).\n- **Pitfall:** Citing \"7±2\" to justify capping a menu at seven links, or worse, padding to seven. Navigation breadth is governed by scanability and labeling, not this number.\n\n### Jakob's Law\n- **Origin:** Jakob Nielsen, 2000.\n- **Principle:** Users spend most of their time on *other* sites and apps. They form mental models from the aggregate, and they expect *yours* to work the same way. Familiarity is transferred expectation.\n- **In the UI:** A logo top-left links home; a magnifying glass means search; a cart icon top-right holds purchases; underlined blue-ish text is a link. Users \"know\" your product before they see it because they've used a thousand like it.\n- **Implication:** Honor conventions for anything the user didn't come to admire — navigation, controls, icons, gestures. Innovate on your *core value*, not on where the back button lives. When you must break a convention, make the new pattern obvious and cheap to learn.\n- **Pitfall:** \"Reimagining\" the scrollbar, hijacking the back gesture, or inventing a novel hamburger-replacement to look fresh. Novelty in plumbing is a tax the user pays on every visit.\n\n### Von Restorff Effect (Isolation Effect)\n- **Origin:** Hedwig von Restorff, 1933.\n- **Principle:** When multiple similar objects are present, the one that *differs* is the most likely to be noticed and remembered.\n- **In the UI:** On a row of grey secondary buttons, one filled accent \"Continue\" owns attention. A pricing table's \"Most popular\" tier lifted, bordered, and badged is the one people recall and pick.\n- **Implication:** Make the single most important element visually distinct — and *only* it. Distinctiveness is a scarce resource spent on one focal point.\n- **Pitfall:** Emphasizing everything (three \"primary\" buttons, five highlighted plans) — when all stand out, none does. Beware relying on color alone for the distinction (fails for colorblind users; pair with shape\u002Fweight\u002Flabel).\n\n### Serial Position Effect\n- **Origin:** Hermann Ebbinghaus (memory curve work, 1880s–1900s); primacy\u002Frecency formalized in the serial-position literature thereafter.\n- **Principle:** Items at the **start** (primacy) and **end** (recency) of a series are recalled best; the middle sags.\n- **In the UI:** Put the most important nav items first and last in a top bar; the throwaway middle holds lower-stakes links. The last step of a flow and the first impression carry disproportionate memory weight.\n- **Implication:** Anchor high-value items to the ends of any sequence — nav, lists, onboarding steps, menus. Don't bury the key action in the middle of a long list.\n- **Pitfall:** Alphabetical or arbitrary ordering of a critical menu, dropping your most-used action into position 6 of 11 where it's least remembered and least scanned.\n\n---\n\n## 3. Complexity & robustness laws (system-side)\n\n### Tesler's Law (Conservation of Complexity)\n- **Origin:** Larry Tesler, Xerox PARC, early 1980s.\n- **Principle:** Every application has an irreducible amount of inherent complexity. The only question is **who absorbs it** — the system\u002Fengineer, or the user. It cannot be deleted, only relocated.\n- **In the UI:** An email \"To:\" field that accepts a raw address, a pasted name, *or* a contact pick — the app does the parsing so the user doesn't format anything. Date pickers that read \"next friday.\" Shipping forms that derive city\u002Fstate from a ZIP.\n- **Implication:** Push complexity *into the system*. Do the parsing, the inference, the defaulting, the validation server-side so the user's surface stays simple. Engineering effort is the right place for the cost to land.\n- **Pitfall:** \"Just make the user enter it in the exact format\" — exporting your parsing complexity onto every user, every time. Equally wrong: hiding *necessary* complexity so far that power users can't reach it.\n\n### Postel's Law (Robustness Principle)\n- **Origin:** Jon Postel, 1980, RFC 760\u002F761 (and 793): \"be conservative in what you send, liberal in what you accept.\"\n- **Principle:** Be liberal in what you *accept* as input, conservative in what you *emit*. Tolerate variation at the boundary; produce clean, predictable output.\n- **In the UI:** A phone field that accepts `415-555-0132`, `(415) 555 0132`, or `4155550132` and normalizes on submit. Search that forgives typos. Forms that trim whitespace and case-fold emails silently.\n- **Implication:** Forgive the user's input format; never reject for cosmetics you could clean yourself. Reserve hard validation for genuine ambiguity, and explain it precisely when you must.\n- **Pitfall:** Over-liberalism that swallows real errors (accepting a malformed email so the user never gets the receipt). Robustness means *forgive formatting*, not *accept garbage*.\n\n---\n\n## 4. Time, motivation & memory-of-experience laws\n\n### Doherty Threshold\n- **Origin:** Walter J. Doherty **and** Arvind J. Thadani, IBM, 1982.\n- **Principle:** When system response drops below **400ms**, the human and machine enter a tight feedback loop and *productivity jumps* — users stay in flow and even do more than asked. Above ~400ms, attention drifts and the experience feels like waiting.\n- **In the UI:** Keep interactions under 400ms. Where the real work is slower, fake the speed: **optimistic UI** (show the liked state instantly, reconcile later), **skeleton screens** instead of spinners, instant input echo, prefetch on hover\u002Fintent.\n- **Implication:** Treat perceived performance as a first-class feature. Respond to *every* input within 100ms even if only to acknowledge; complete or progress-indicate within 400ms wherever possible.\n- **Pitfall:** Blocking the UI on a network round-trip with a bare spinner, or animating a transition so long (600ms+) it re-introduces the wait you optimized away. Eye-candy that costs latency is a regression.\n\n### Goal-Gradient Effect\n- **Origin:** Clark Hull, 1932 (animal-learning studies). Applied to consumers as **endowed progress** by Kivetz, Urminsky & Zheng, 2006.\n- **Principle:** Motivation to reach a goal *increases* the closer one is to it. The \"endowed progress\" refinement: artificial early progress (a punch card pre-stamped twice) accelerates completion versus an empty start.\n- **In the UI:** Progress bars and steppers that fill as the user advances. A profile-completion meter at \"60%\" pulls people to 100%. Onboarding that pre-checks the steps they've already done so they start \"ahead.\"\n- **Implication:** Show progress, and front-load a sense of advancement. Break long flows into a visible track so each step feels like nearing the finish.\n- **Pitfall:** A progress bar that lies or resets (jumping back, an extra surprise step after \"100%\") destroys trust — the gradient pulls them in, the lie throws them out.\n\n### Zeigarnik Effect\n- **Origin:** Bluma Zeigarnik, 1927.\n- **Principle:** People remember *incomplete* or interrupted tasks better than completed ones — open loops nag at working memory.\n- **In the UI:** A \"3 of 5 steps complete\" onboarding checklist, a half-filled profile prompt, an empty cart badge — each open loop draws the user back. Inbox unread counts exploit it (sometimes abusively).\n- **Implication:** Use visible incompleteness to motivate return and continuation — checklists, setup progress, saved drafts. Make the open loop closable in one obvious action.\n- **Pitfall:** Manufacturing endless open loops (permanent badges, never-finishable checklists) breeds anxiety and notification fatigue. The effect is a nudge, not a leash.\n\n### Peak–End Rule\n- **Origin:** Daniel Kahneman and colleagues, ~1993 (Redelmeier & Kahneman colonoscopy study; Fredrickson & Kahneman).\n- **Principle:** People judge an experience largely by its most intense moment (the **peak**, good or bad) and its **end** — not by the sum or average of every moment.\n- **In the UI:** Invest in the high points (a delightful first success, a celebratory \"shipped!\" moment) and the endings (the post-purchase confirmation, the empty state after completing a task). A graceful, well-recovered error can become a positive peak.\n- **Implication:** Map the journey's peaks and its ending, and design those deliberately. A smooth average with a frustrating finish is remembered as frustrating.\n- **Pitfall:** Polishing the mid-funnel while the *end* is an abrupt blank page or a dead-end error. Optimizing the average and neglecting the two moments that actually get encoded.\n\n### Aesthetic–Usability Effect\n- **Origin:** Masaaki Kurosu and Kaori Kashimura, Hitachi, 1995 (ATM-layout study).\n- **Principle:** Users *perceive* more aesthetically pleasing designs as more usable — and are more tolerant of minor usability problems in them.\n- **In the UI:** A clean, well-typeset, harmonious interface earns trust and patience; users forgive small frictions and rate it easier even when task-time is identical to an ugly one.\n- **Implication:** Visual quality is functional — it buys credibility, trust, and forgiveness. Don't dismiss polish as \"just cosmetics\"; it changes measured perception.\n- **Pitfall (the risk):** Beauty *masks* real usability problems — in testing, a pretty prototype hides flaws users would report in a plain one. Test with realistic visuals *and* probe for issues the gloss is hiding; never let aesthetics substitute for actual task success.\n\n---\n\n## 5. Cognitive load, attention & focus\n\n### Cognitive Load Theory\n- **Origin:** John Sweller, 1988.\n- **Principle:** Working memory has limited capacity, split three ways: **intrinsic** (inherent difficulty of the task), **extraneous** (load added by *how* it's presented — clutter, jargon, bad layout), and **germane** (effort that builds useful understanding). You can't lower intrinsic load, but you must minimize extraneous to leave room for the task.\n- **In the UI:** Strip extraneous load: remove decorative noise, reduce field count, use plain labels, chunk content, defer non-essential controls. Reserve the user's capacity for the actual decision.\n- **Implication:** Audit every screen for extraneous load and cut it. Match information density to the task's intrinsic difficulty; add scaffolding (germane) only where it genuinely aids learning.\n- **Pitfall:** Confusing \"minimal\" with \"low-load\" — hiding essential controls *raises* load (now the user hunts). Load is about clarity and chunking, not pixel-emptiness.\n\n### Selective Attention \u002F Inattentional Blindness (Banner Blindness)\n- **Origin:** Inattentional blindness — Simons & Chabris, 1999 (\"invisible gorilla\"). **Banner blindness** — Benway & Lane, 1998.\n- **Principle:** Attention is selective; users focused on a goal literally do not see elements they've learned to ignore — especially ad-shaped, banner-shaped, or peripheral content.\n- **In the UI:** A genuine call-to-action styled like an ad banner (top, full-width, colorful, off to the side) gets skipped. Important messages dressed as marketing are invisible to task-focused users.\n- **Implication:** Place critical information *in the path of the task*, in the content column, not in banner\u002Fsidebar real estate. Don't make essential UI look like advertising.\n- **Pitfall:** Sticking a key notice in a top banner or right rail and assuming it was seen. If it looks like an ad, it's gone.\n\n### Flow\n- **Origin:** Mihály Csíkszentmihályi, 1975.\n- **Principle:** A state of full, energized focus reached when challenge and skill are balanced, goals are clear, and feedback is immediate. Interruptions and latency break it.\n- **In the UI:** Keep responses fast (ties to Doherty), feedback immediate, the next step clear, and modal interruptions rare. Power-user shortcuts let skill rise with challenge.\n- **Implication:** Protect flow — minimize disruptive dialogs, defer non-urgent notifications, keep the path forward obvious, and give instant feedback on every action.\n- **Pitfall:** Interrupting deep work with cookie banners, upsell modals, or \"rate us\" prompts mid-task — each one ejects the user from flow and resets their context.\n\n### Recognition over Recall\n- **Origin:** Long-standing memory psychology; codified for UI in Nielsen's heuristic \"Recognition rather than recall\" (1994). See the `usability-heuristics` skill for the full heuristic set.\n- **Principle:** Recognizing something shown is far cheaper than recalling it unaided. Visible options beat memorized commands.\n- **In the UI:** Dropdowns and pickers over \"type the exact code\"; recently-used and autocomplete over blank fields; visible breadcrumbs over remembering where you are.\n- **Implication:** Show options and context; don't force the user to hold information across screens or remember syntax. Make actions and state *visible*.\n- **Pitfall:** Command-line-style UIs for novice tasks, or forms that reference a value the user saw two screens ago and must now retype from memory.\n\n---\n\n## 6. Productivity, scope & behavioral-economics cluster\n\nThese shape product and UX decisions; cited compactly because each is a single sharp idea.\n\n| Law \u002F Principle | Origin | The idea | Use it for | Pitfall |\n|---|---|---|---|---|\n| **Parkinson's Law** | C. Northcote Parkinson, 1955 | Work expands to fill the time allotted. | Imposed deadlines\u002Ftimers focus effort (booking holds, \"offer ends in 10:00\"). | Manufactured fake urgency erodes trust; real scarcity only. |\n| **Pareto (80\u002F20)** | Vilfredo Pareto; named by Joseph Juran | ~80% of effects come from ~20% of causes. | Prioritize the 20% of features that drive 80% of use; optimize hot paths first. | Treating it as exact law; neglecting the long-tail 20% that retains power users. |\n| **Occam's Razor** | William of Ockham (14th c.) | Among competing solutions, prefer the one with fewest assumptions. | Cut redundant steps, fields, options; simplest flow that works. | Over-simplifying past the task's irreducible complexity (see Tesler). |\n| **Loss Aversion** | Kahneman & Tversky, prospect theory, 1979 | Losses loom ~2× larger than equivalent gains. | \"Don't lose your progress,\" abandoned-cart, free-trial framing. | Dark-pattern coercion (\"you'll lose everything!\") to trap users. |\n| **Anchoring** | Tversky & Kahneman, 1974 | First number\u002Foption seen biases all later judgments. | Show a higher \"was\" price, place the target plan beside a premium one. | Deceptive anchors (fake original prices) are manipulative and often illegal. |\n| **Choice Overload** | Iyengar & Lepper, 2000 (jam study) | Too many options reduces likelihood of *any* choice and satisfaction with it. | Curate, recommend a default, limit visible plans\u002FSKUs. | Confusing with Hick's (that's *speed*; this is *paralysis & regret*). |\n\nThe distinction between **Hick's Law** and **Choice Overload** is worth holding precisely, because they look identical on a cluttered screen but prescribe differently. Hick is about *deliberation time* — it scales with how many options you make a person *evaluate*, and the fix is reducing or grouping so the relevant set is small. Choice overload is about *paralysis and post-decision regret* — beyond a threshold of roughly a dozen comparable options, people defer choosing entirely or feel worse about whatever they picked, and the fix is curation plus a recommended default that lets them opt out of comparing. A plan-picker with 4 tiers is a Hick problem (speed it up); a marketplace with 200 near-identical SKUs is a choice-overload problem (curate and recommend).\n\n> **Loss aversion \u002F anchoring \u002F choice overload are powerful and dual-use.** They describe real biases — use them to *help* users decide (clear defaults, honest comparison), never to coerce. Manufactured scarcity, fake anchors, and confirmshaming are dark patterns; they win the click and lose the trust.\n\n---\n\n## 7. Gestalt grouping (brief — see `layout-and-composition`)\n\nThe Gestalt principles (Wertheimer, Koffka, Köhler, 1920s; **Common Region** and **Uniform Connectedness** added later by Palmer & Rock) describe how the eye groups before it reads:\n\n- **Proximity** — elements placed close together are perceived as one group. Spacing *is* grouping.\n- **Common Region** — elements inside a shared boundary (a card, a panel) read as a set, even if far apart.\n- **Uniform Connectedness** — elements joined by a line or shared background read as connected — the strongest grouping cue.\n\nIn practice: control grouping with *whitespace and containers*, not dividers. A form field and its label belong to the same region; a save button belongs near what it saves. The full Gestalt treatment — similarity, closure, continuity, figure\u002Fground — lives in the **`layout-and-composition`** skill; don't re-derive it here.\n\n---\n\n## 8. Do \u002F Don't\n\n| Do | Don't |\n|---|---|\n| Make frequent, important targets big and near; use edges\u002Fcorners (Fitts). | Cram tiny icon buttons at small gaps, or give a big button a small hit area. |\n| Reduce and group choices; offer a sensible default (Hick). | Dump 40 ungrouped options, or fragment one choice into 10 screens. |\n| Chunk data into meaningful units (Miller). | Cite \"7±2\" to cap menu items. |\n| Honor platform conventions for plumbing (Jakob). | Reinvent the scrollbar, back gesture, or nav to \"look fresh.\" |\n| Push complexity into the system (Tesler); forgive input formats (Postel). | Demand exact formats; or accept genuinely broken input. |\n| Respond \u003C400ms; use optimistic UI + skeletons (Doherty). | Block on a spinner, or add a 600ms transition that re-adds the wait. |\n| Design the peaks and the *ending* deliberately (Peak-End). | Polish the average and leave an abrupt blank\u002Ferror finish. |\n| Use polish to earn trust (Aesthetic-Usability)… | …but let beauty mask flaws or skip usability testing. |\n| Emphasize one focal point (Von Restorff). | Make three things \"primary\" — emphasis on all = emphasis on none. |\n| Show progress; front-load it (Goal-Gradient, Zeigarnik). | Reset a progress bar or invent endless open loops. |\n| Put critical info in the task path (Selective Attention). | Style essential UI like an ad banner. |\n| Use biases to help users decide (anchoring, defaults). | Weaponize them — fake scarcity, fake anchors, confirmshaming. |\n\n---\n\n## 9. Summary table (law → use it for → pitfall)\n\n| Law | Attribution | Use it for | Pitfall |\n|---|---|---|---|\n| Fitts's | Fitts, 1954 | Size\u002Fplace targets; exploit edges & corners | Tiny clustered buttons; visual ≠ hit area |\n| Hick-Hyman | Hick & Hyman, 1952 | Cut\u002Fgroup choices; defaults | Death-by-wizard; over-fragmenting |\n| Miller's | Miller, 1956 | Chunk & format data | \"7±2\" as a hard menu cap |\n| Jakob's | Nielsen, 2000 | Honor conventions | Reinventing plumbing |\n| Tesler's | Tesler, ~1980s | Shift complexity to system | Exporting parsing to the user |\n| Postel's | Postel, 1980 | Forgive input, clean output | Swallowing real errors |\n| Doherty | Doherty & Thadani, 1982 | \u003C400ms; optimistic UI, skeletons | Blocking spinners; slow transitions |\n| Peak-End | Kahneman et al., 1993 | Design peaks + endings | Neglecting the finish |\n| Aesthetic-Usability | Kurosu & Kashimura, 1995 | Polish earns trust\u002Fforgiveness | Masking real usability flaws |\n| Von Restorff | von Restorff, 1933 | One distinct focal point | Emphasizing everything |\n| Serial Position | Ebbinghaus | Important items at start\u002Fend | Burying key action in the middle |\n| Goal-Gradient | Hull, 1932; Kivetz 2006 | Progress bars; endowed progress | Resetting\u002Flying progress |\n| Zeigarnik | Zeigarnik, 1927 | Checklists; open loops | Endless un-closable loops |\n| Cognitive Load | Sweller, 1988 | Cut extraneous load | Hiding essentials (raises load) |\n| Selective Attention | Simons & Chabris 1999; Benway & Lane 1998 | Put key info in task path | Banner-styled essential UI |\n| Flow | Csíkszentmihályi, 1975 | Fast, clear, uninterrupted | Mid-task modals\u002Fupsells |\n| Recognition>Recall | Nielsen heuristic, 1994 | Pickers, autocomplete, visible state | CLI-style novice tasks |\n| Parkinson's | Parkinson, 1955 | Honest deadlines\u002Ftimers | Fake urgency |\n| Pareto | Pareto \u002F Juran | Prioritize the vital 20% | Ignoring the long tail |\n| Occam's | Ockham | Simplest flow that works | Over-simplifying past Tesler floor |\n| Loss aversion \u002F Anchoring | Kahneman & Tversky, 1979\u002F1974 | Framing, comparison, defaults | Coercive dark patterns |\n| Choice overload | Iyengar & Lepper, 2000 | Curate; recommend a default | Confusing with Hick (speed vs paralysis) |\n| Gestalt grouping | Wertheimer et al.; Palmer & Rock | Group via space & regions | Dividers instead of whitespace |\n\n---\n\n## 10. Cross-device application\n\nThe laws are universal; their *thresholds* shift by input method and context.\n\n| Law | Mobile \u002F touch | Desktop \u002F pointer | Watch \u002F TV \u002F voice |\n|---|---|---|---|\n| **Fitts's** | Touch targets **≥44×44pt (iOS) \u002F 48×48dp (Android)**, ≥8px apart — the finger is a fat, imprecise pointer with no hover. Thumb-reach zones matter: primary actions in the bottom third. | Precise cursor allows smaller targets, but still respect ≥24px clickable and use screen edges\u002Fcorners (infinite targets) the mouse can slam into. | Watch: huge targets, few per screen. TV: D-pad focus order *is* the target model — distance = button presses. Voice: no spatial targets; \"distance\" is dialog depth. |\n| **Hick's** | Small screen forces fewer visible choices — lean on progressive disclosure, sheets, and defaults harder than on desktop. | Room for more options, but still group; menus and command palettes scale choice without scaling decision time. | Severe choice limits — 2–4 options per screen on watch\u002FTV; voice must offer ≤3 spoken options or it overflows memory. |\n| **Doherty** | Perceived performance is *more* critical — flaky networks. Lean on optimistic UI, skeletons, prefetch, and offline-first; never block the thumb on a round-trip. | Faster networks raise the bar — under 400ms is the floor, 100ms feels instant. | Voice has its own latency budget: a reply must begin \u003C1s or the interaction feels broken; fill with a brief acknowledgment. |\n| **Miller \u002F Cognitive Load** | Tiny viewport = brutal extraneous-load budget; chunk aggressively, one primary task per screen. | More room to show context — but don't mistake space for license to clutter. | Watch\u002Fvoice: hold almost nothing — strip to a single decision; never recite a long list aloud. |\n| **Jakob's** | Honor *platform* conventions (iOS vs Android navigation, share sheets, back behavior) — see `platform-conventions`. | Honor web\u002Fdesktop conventions (menu bar, right-click, keyboard shortcuts). | Honor the platform's own paradigm (watch crowns, TV remotes, voice turn-taking). |\n\n**The through-line:** smaller and less-precise the input, the *larger* the targets, the *fewer* the choices, the *faster* the response must feel, and the *less* the user can hold in memory. Design for the most constrained context your screen will run in, then expand — not the reverse.\n\n---\n\n## 11. Using the laws — workflow & worked example\n\nThe laws map to stages of a design. Reach for them in this order when building or auditing a screen:\n\n| Stage | Question | Laws that answer it |\n|---|---|---|\n| **Structure** | How many things, grouped how? | Hick (count), Miller (chunking), Gestalt\u002FCommon Region (grouping), Pareto (which 20% to surface) |\n| **Hierarchy** | What's the one focal point? | Von Restorff (distinct focal point), Serial Position (ends), Selective Attention (in the task path) |\n| **Targets** | Can they hit \u002F reach it? | Fitts (size, distance, edges), cross-device touch minimums |\n| **Flow & speed** | Does it stay responsive and uninterrupted? | Doherty (\u003C400ms), Flow (no mid-task interruptions) |\n| **Memory** | Are we making them remember? | Recognition over recall, Miller, Tesler (system absorbs it) |\n| **Input** | Are we forgiving? | Postel (liberal input), Tesler (parse it for them) |\n| **Motivation** | Will they finish? | Goal-Gradient (progress), Zeigarnik (open loops), Loss aversion (framing) |\n| **Memory of it** | How will they recall the experience? | Peak-End (peaks + ending), Aesthetic-Usability (polish → trust) |\n\n**Worked diagnostic — a sign-up form that converts poorly.** Walk the laws as a checklist:\n\n- *Structure:* 14 fields shown at once → **Hick** + **Cognitive Load** violation. Cut to the 4 the account genuinely needs now; defer the rest (Tesler — derive what you can server-side; Pareto — most fields aren't load-bearing for signup).\n- *Targets:* \"Create account\" is a 14px text link bottom-right → **Fitts** violation on the most important action. Make it a full-width 48px button.\n- *Speed:* submit shows a blank spinner for 2s → **Doherty** + **Flow** violation. Optimistic transition to the next step; validate in the background.\n- *Input:* email rejected for a trailing space → **Postel** violation. Trim and case-fold silently.\n- *Memory:* \"enter the code from the previous screen\" → **Recognition over recall** violation. Carry it forward or show it.\n- *End:* success lands on a blank dashboard → **Peak-End** miss. Add a brief \"You're in\" moment and a clear first action.\n\nSix named laws, six concrete fixes, each defensible in review by its source. That's the point of the catalogue: it turns \"this feels off\" into \"this fails Fitts, here's the threshold.\"\n\n**The squint\u002Fmeasure tests:** for **Fitts**, drop the design to mobile size and try to tap each primary action with a thumb — if you miss, it's too small or too cramped. For **Hick\u002FLoad**, count the decisions visible above the fold; more than ~5 unrelated ones is a smell. For **Doherty**, profile the p95 of every interaction and flag anything over 400ms for an optimistic-UI treatment. For **Von Restorff**, squint at the screen — exactly one element should still read; if two compete, your focal point is split.\n\n---\n\n> Use a law to *diagnose* (name what's wrong and why) and to *justify* (defend a decision in review with its source). They are constraints on human cognition, not preferences — but every one has a dual-use edge. Apply them to serve the user's goal; the moment a law is used to trick rather than help, it's a dark pattern. When in doubt, the canonical attributed reference for the named \"Laws of UX\" is Jon Yablonski's lawsofux.com; the underlying findings trace to the researchers credited in each block above.\n","# Laws of UX & Cognitive Principles\n\nThese are not style opinions. Each \"law\" is a named finding from perceptual psychology, cognitive science, or behavioral economics that constrains how *every* human uses *every* screen — desktop, mobile, watch, voice, kiosk. Jon Yablonski's *Laws of UX* (lawsofux.com, 2020) collected the design-facing subset; the originals trace to the researchers credited below. Cite the source when you invoke a law in a design review — \"this fails Fitts\" lands harder than \"the button feels small.\"\n\nRead each law as a fixed five-part block: **Origin** (who\u002Fwhen), **Principle** (the mechanism, with the math where it exists), **In the UI** (one concrete control or screen), **Implication** (the general rule you derive), **Pitfall** (the failure mode). Keep \"In the UI\" and \"Implication\" distinct: the first is an example, the second is the rule.\n\nThe laws also *combine* — most good interactions satisfy several at once and most bad ones violate a cluster. A fast, optimistic submit serves Doherty *and* Flow; a forgiving, system-parsed input field serves Postel *and* Tesler *and* Recognition-over-recall. When two laws appear to conflict (Hick says fewer choices, but Jakob says match the conventional five-tab bar users expect), Jakob usually wins for plumbing and Hick for content — convention is a learned default that costs nothing, novelty is the expensive part.\n\n---\n\n## 1. Targeting & decision laws (the geometric ones)\n\n### Fitts's Law\n- **Origin:** Paul Fitts, 1954. Formalized in *The information capacity of the human motor system*.\n- **Principle:** Time to acquire a target = `T ≈ a + b·log₂(2D\u002FW)`, where `D` = distance to target, `W` = target width along the motion axis. Acquisition time grows *logarithmically* with distance and *shrinks* as the target gets bigger. Doubling size helps far more than the formula's modest log on distance suggests in dense UIs.\n- **In the UI:** A primary CTA rendered 48px tall and placed near the user's current focus is hit fast; the same action as a 16px text link in a far corner is slow and error-prone. Screen *edges and corners* have effectively infinite width (the pointer stops dead) — macOS menu bar, Windows Start corner, the right-click context menu spawned *at* the cursor (`D≈0`).\n- **Implication:** Make important, frequent targets big and near. Anchor destructive or rare targets far and small. Exploit edges, corners, and the pointer's own position for the loudest actions.\n- **Pitfall:** Tiny icon-only buttons crammed together (toolbar of 24px glyphs at 4px gaps) — every click is a coin-flip. Also: a big *visual* button with a small *hit area* (padding outside the clickable region) silently breaks the law.\n\n### Hick's Law (Hick-Hyman Law)\n- **Origin:** William Edmund Hick **and** Ray Hyman, 1952 — independent papers, jointly named. Don't drop Hyman.\n- **Principle:** Decision time rises logarithmically with the number of equally-probable choices: `RT = b·log₂(n + 1)`. Each doubling of options adds a roughly constant slice of deliberation, not a linear pile.\n- **In the UI:** A checkout with one obvious \"Pay\" button decides instantly; a settings page dumping 40 toggles at once stalls the user. Chunking the 40 into 6 labeled groups, or revealing advanced options behind a disclosure, restores speed.\n- **Implication:** Reduce or *categorize* choices. Use progressive disclosure, smart defaults (a pre-selected sensible option removes the decision entirely), and grouping. Highlight a recommended path so the user can skip the comparison.\n- **Pitfall:** Over-applying it into death-by-wizard — splitting one coherent choice across ten one-question screens adds navigation cost and hides context. Hick's targets *count and grouping*, not \"fewer screens always.\"\n\n---\n\n## 2. Memory & cognition laws\n\n### Miller's Law\n- **Origin:** George A. Miller, 1956, *The Magical Number Seven, Plus or Minus Two*.\n- **Principle:** Working memory holds ~7±2 **chunks**, not items. The number is about *units of meaning*, and a chunk can be large (a familiar acronym, a grouped phone segment). **Nuance\u002Fmyth:** \"7\" is widely misquoted as a hard cap on menu items or nav links — it is not. Cowan's later work (2001) refines the real span to ~4 chunks. The usable lesson is *chunk and group*, not \"never exceed seven.\"\n- **In the UI:** A phone number shown as `+1 (415) 555-0132` is four chunks and trivially held; `+14155550132` is twelve digits and slips. Card numbers grouped in 4s, OTP fields in segments, nav grouped into labeled sections.\n- **Implication:** Format and group information into meaningful chunks so the user holds a structure, not a stream. Don't make the user keep facts in their head across steps — show them on screen (recognition over recall, §5).\n- **Pitfall:** Citing \"7±2\" to justify capping a menu at seven links, or worse, padding to seven. Navigation breadth is governed by scanability and labeling, not this number.\n\n### Jakob's Law\n- **Origin:** Jakob Nielsen, 2000.\n- **Principle:** Users spend most of their time on *other* sites and apps. They form mental models from the aggregate, and they expect *yours* to work the same way. Familiarity is transferred expectation.\n- **In the UI:** A logo top-left links home; a magnifying glass means search; a cart icon top-right holds purchases; underlined blue-ish text is a link. Users \"know\" your product before they see it because they've used a thousand like it.\n- **Implication:** Honor conventions for anything the user didn't come to admire — navigation, controls, icons, gestures. Innovate on your *core value*, not on where the back button lives. When you must break a convention, make the new pattern obvious and cheap to learn.\n- **Pitfall:** \"Reimagining\" the scrollbar, hijacking the back gesture, or inventing a novel hamburger-replacement to look fresh. Novelty in plumbing is a tax the user pays on every visit.\n\n### Von Restorff Effect (Isolation Effect)\n- **Origin:** Hedwig von Restorff, 1933.\n- **Principle:** When multiple similar objects are present, the one that *differs* is the most likely to be noticed and remembered.\n- **In the UI:** On a row of grey secondary buttons, one filled accent \"Continue\" owns attention. A pricing table's \"Most popular\" tier lifted, bordered, and badged is the one people recall and pick.\n- **Implication:** Make the single most important element visually distinct — and *only* it. Distinctiveness is a scarce resource spent on one focal point.\n- **Pitfall:** Emphasizing everything (three \"primary\" buttons, five highlighted plans) — when all stand out, none does. Beware relying on color alone for the distinction (fails for colorblind users; pair with shape\u002Fweight\u002Flabel).\n\n### Serial Position Effect\n- **Origin:** Hermann Ebbinghaus (memory curve work, 1880s–1900s); primacy\u002Frecency formalized in the serial-position literature thereafter.\n- **Principle:** Items at the **start** (primacy) and **end** (recency) of a series are recalled best; the middle sags.\n- **In the UI:** Put the most important nav items first and last in a top bar; the throwaway middle holds lower-stakes links. The last step of a flow and the first impression carry disproportionate memory weight.\n- **Implication:** Anchor high-value items to the ends of any sequence — nav, lists, onboarding steps, menus. Don't bury the key action in the middle of a long list.\n- **Pitfall:** Alphabetical or arbitrary ordering of a critical menu, dropping your most-used action into position 6 of 11 where it's least remembered and least scanned.\n\n---\n\n## 3. Complexity & robustness laws (system-side)\n\n### Tesler's Law (Conservation of Complexity)\n- **Origin:** Larry Tesler, Xerox PARC, early 1980s.\n- **Principle:** Every application has an irreducible amount of inherent complexity. The only question is **who absorbs it** — the system\u002Fengineer, or the user. It cannot be deleted, only relocated.\n- **In the UI:** An email \"To:\" field that accepts a raw address, a pasted name, *or* a contact pick — the app does the parsing so the user doesn't format anything. Date pickers that read \"next friday.\" Shipping forms that derive city\u002Fstate from a ZIP.\n- **Implication:** Push complexity *into the system*. Do the parsing, the inference, the defaulting, the validation server-side so the user's surface stays simple. Engineering effort is the right place for the cost to land.\n- **Pitfall:** \"Just make the user enter it in the exact format\" — exporting your parsing complexity onto every user, every time. Equally wrong: hiding *necessary* complexity so far that power users can't reach it.\n\n### Postel's Law (Robustness Principle)\n- **Origin:** Jon Postel, 1980, RFC 760\u002F761 (and 793): \"be conservative in what you send, liberal in what you accept.\"\n- **Principle:** Be liberal in what you *accept* as input, conservative in what you *emit*. Tolerate variation at the boundary; produce clean, predictable output.\n- **In the UI:** A phone field that accepts `415-555-0132`, `(415) 555 0132`, or `4155550132` and normalizes on submit. Search that forgives typos. Forms that trim whitespace and case-fold emails silently.\n- **Implication:** Forgive the user's input format; never reject for cosmetics you could clean yourself. Reserve hard validation for genuine ambiguity, and explain it precisely when you must.\n- **Pitfall:** Over-liberalism that swallows real errors (accepting a malformed email so the user never gets the receipt). Robustness means *forgive formatting*, not *accept garbage*.\n\n---\n\n## 4. Time, motivation & memory-of-experience laws\n\n### Doherty Threshold\n- **Origin:** Walter J. Doherty **and** Arvind J. Thadani, IBM, 1982.\n- **Principle:** When system response drops below **400ms**, the human and machine enter a tight feedback loop and *productivity jumps* — users stay in flow and even do more than asked. Above ~400ms, attention drifts and the experience feels like waiting.\n- **In the UI:** Keep interactions under 400ms. Where the real work is slower, fake the speed: **optimistic UI** (show the liked state instantly, reconcile later), **skeleton screens** instead of spinners, instant input echo, prefetch on hover\u002Fintent.\n- **Implication:** Treat perceived performance as a first-class feature. Respond to *every* input within 100ms even if only to acknowledge; complete or progress-indicate within 400ms wherever possible.\n- **Pitfall:** Blocking the UI on a network round-trip with a bare spinner, or animating a transition so long (600ms+) it re-introduces the wait you optimized away. Eye-candy that costs latency is a regression.\n\n### Goal-Gradient Effect\n- **Origin:** Clark Hull, 1932 (animal-learning studies). Applied to consumers as **endowed progress** by Kivetz, Urminsky & Zheng, 2006.\n- **Principle:** Motivation to reach a goal *increases* the closer one is to it. The \"endowed progress\" refinement: artificial early progress (a punch card pre-stamped twice) accelerates completion versus an empty start.\n- **In the UI:** Progress bars and steppers that fill as the user advances. A profile-completion meter at \"60%\" pulls people to 100%. Onboarding that pre-checks the steps they've already done so they start \"ahead.\"\n- **Implication:** Show progress, and front-load a sense of advancement. Break long flows into a visible track so each step feels like nearing the finish.\n- **Pitfall:** A progress bar that lies or resets (jumping back, an extra surprise step after \"100%\") destroys trust — the gradient pulls them in, the lie throws them out.\n\n### Zeigarnik Effect\n- **Origin:** Bluma Zeigarnik, 1927.\n- **Principle:** People remember *incomplete* or interrupted tasks better than completed ones — open loops nag at working memory.\n- **In the UI:** A \"3 of 5 steps complete\" onboarding checklist, a half-filled profile prompt, an empty cart badge — each open loop draws the user back. Inbox unread counts exploit it (sometimes abusively).\n- **Implication:** Use visible incompleteness to motivate return and continuation — checklists, setup progress, saved drafts. Make the open loop closable in one obvious action.\n- **Pitfall:** Manufacturing endless open loops (permanent badges, never-finishable checklists) breeds anxiety and notification fatigue. The effect is a nudge, not a leash.\n\n### Peak–End Rule\n- **Origin:** Daniel Kahneman and colleagues, ~1993 (Redelmeier & Kahneman colonoscopy study; Fredrickson & Kahneman).\n- **Principle:** People judge an experience largely by its most intense moment (the **peak**, good or bad) and its **end** — not by the sum or average of every moment.\n- **In the UI:** Invest in the high points (a delightful first success, a celebratory \"shipped!\" moment) and the endings (the post-purchase confirmation, the empty state after completing a task). A graceful, well-recovered error can become a positive peak.\n- **Implication:** Map the journey's peaks and its ending, and design those deliberately. A smooth average with a frustrating finish is remembered as frustrating.\n- **Pitfall:** Polishing the mid-funnel while the *end* is an abrupt blank page or a dead-end error. Optimizing the average and neglecting the two moments that actually get encoded.\n\n### Aesthetic–Usability Effect\n- **Origin:** Masaaki Kurosu and Kaori Kashimura, Hitachi, 1995 (ATM-layout study).\n- **Principle:** Users *perceive* more aesthetically pleasing designs as more usable — and are more tolerant of minor usability problems in them.\n- **In the UI:** A clean, well-typeset, harmonious interface earns trust and patience; users forgive small frictions and rate it easier even when task-time is identical to an ugly one.\n- **Implication:** Visual quality is functional — it buys credibility, trust, and forgiveness. Don't dismiss polish as \"just cosmetics\"; it changes measured perception.\n- **Pitfall (the risk):** Beauty *masks* real usability problems — in testing, a pretty prototype hides flaws users would report in a plain one. Test with realistic visuals *and* probe for issues the gloss is hiding; never let aesthetics substitute for actual task success.\n\n---\n\n## 5. Cognitive load, attention & focus\n\n### Cognitive Load Theory\n- **Origin:** John Sweller, 1988.\n- **Principle:** Working memory has limited capacity, split three ways: **intrinsic** (inherent difficulty of the task), **extraneous** (load added by *how* it's presented — clutter, jargon, bad layout), and **germane** (effort that builds useful understanding). You can't lower intrinsic load, but you must minimize extraneous to leave room for the task.\n- **In the UI:** Strip extraneous load: remove decorative noise, reduce field count, use plain labels, chunk content, defer non-essential controls. Reserve the user's capacity for the actual decision.\n- **Implication:** Audit every screen for extraneous load and cut it. Match information density to the task's intrinsic difficulty; add scaffolding (germane) only where it genuinely aids learning.\n- **Pitfall:** Confusing \"minimal\" with \"low-load\" — hiding essential controls *raises* load (now the user hunts). Load is about clarity and chunking, not pixel-emptiness.\n\n### Selective Attention \u002F Inattentional Blindness (Banner Blindness)\n- **Origin:** Inattentional blindness — Simons & Chabris, 1999 (\"invisible gorilla\"). **Banner blindness** — Benway & Lane, 1998.\n- **Principle:** Attention is selective; users focused on a goal literally do not see elements they've learned to ignore — especially ad-shaped, banner-shaped, or peripheral content.\n- **In the UI:** A genuine call-to-action styled like an ad banner (top, full-width, colorful, off to the side) gets skipped. Important messages dressed as marketing are invisible to task-focused users.\n- **Implication:** Place critical information *in the path of the task*, in the content column, not in banner\u002Fsidebar real estate. Don't make essential UI look like advertising.\n- **Pitfall:** Sticking a key notice in a top banner or right rail and assuming it was seen. If it looks like an ad, it's gone.\n\n### Flow\n- **Origin:** Mihály Csíkszentmihályi, 1975.\n- **Principle:** A state of full, energized focus reached when challenge and skill are balanced, goals are clear, and feedback is immediate. Interruptions and latency break it.\n- **In the UI:** Keep responses fast (ties to Doherty), feedback immediate, the next step clear, and modal interruptions rare. Power-user shortcuts let skill rise with challenge.\n- **Implication:** Protect flow — minimize disruptive dialogs, defer non-urgent notifications, keep the path forward obvious, and give instant feedback on every action.\n- **Pitfall:** Interrupting deep work with cookie banners, upsell modals, or \"rate us\" prompts mid-task — each one ejects the user from flow and resets their context.\n\n### Recognition over Recall\n- **Origin:** Long-standing memory psychology; codified for UI in Nielsen's heuristic \"Recognition rather than recall\" (1994). See the `usability-heuristics` skill for the full heuristic set.\n- **Principle:** Recognizing something shown is far cheaper than recalling it unaided. Visible options beat memorized commands.\n- **In the UI:** Dropdowns and pickers over \"type the exact code\"; recently-used and autocomplete over blank fields; visible breadcrumbs over remembering where you are.\n- **Implication:** Show options and context; don't force the user to hold information across screens or remember syntax. Make actions and state *visible*.\n- **Pitfall:** Command-line-style UIs for novice tasks, or forms that reference a value the user saw two screens ago and must now retype from memory.\n\n---\n\n## 6. Productivity, scope & behavioral-economics cluster\n\nThese shape product and UX decisions; cited compactly because each is a single sharp idea.\n\n| Law \u002F Principle | Origin | The idea | Use it for | Pitfall |\n|---|---|---|---|---|\n| **Parkinson's Law** | C. Northcote Parkinson, 1955 | Work expands to fill the time allotted. | Imposed deadlines\u002Ftimers focus effort (booking holds, \"offer ends in 10:00\"). | Manufactured fake urgency erodes trust; real scarcity only. |\n| **Pareto (80\u002F20)** | Vilfredo Pareto; named by Joseph Juran | ~80% of effects come from ~20% of causes. | Prioritize the 20% of features that drive 80% of use; optimize hot paths first. | Treating it as exact law; neglecting the long-tail 20% that retains power users. |\n| **Occam's Razor** | William of Ockham (14th c.) | Among competing solutions, prefer the one with fewest assumptions. | Cut redundant steps, fields, options; simplest flow that works. | Over-simplifying past the task's irreducible complexity (see Tesler). |\n| **Loss Aversion** | Kahneman & Tversky, prospect theory, 1979 | Losses loom ~2× larger than equivalent gains. | \"Don't lose your progress,\" abandoned-cart, free-trial framing. | Dark-pattern coercion (\"you'll lose everything!\") to trap users. |\n| **Anchoring** | Tversky & Kahneman, 1974 | First number\u002Foption seen biases all later judgments. | Show a higher \"was\" price, place the target plan beside a premium one. | Deceptive anchors (fake original prices) are manipulative and often illegal. |\n| **Choice Overload** | Iyengar & Lepper, 2000 (jam study) | Too many options reduces likelihood of *any* choice and satisfaction with it. | Curate, recommend a default, limit visible plans\u002FSKUs. | Confusing with Hick's (that's *speed*; this is *paralysis & regret*). |\n\nThe distinction between **Hick's Law** and **Choice Overload** is worth holding precisely, because they look identical on a cluttered screen but prescribe differently. Hick is about *deliberation time* — it scales with how many options you make a person *evaluate*, and the fix is reducing or grouping so the relevant set is small. Choice overload is about *paralysis and post-decision regret* — beyond a threshold of roughly a dozen comparable options, people defer choosing entirely or feel worse about whatever they picked, and the fix is curation plus a recommended default that lets them opt out of comparing. A plan-picker with 4 tiers is a Hick problem (speed it up); a marketplace with 200 near-identical SKUs is a choice-overload problem (curate and recommend).\n\n> **Loss aversion \u002F anchoring \u002F choice overload are powerful and dual-use.** They describe real biases — use them to *help* users decide (clear defaults, honest comparison), never to coerce. Manufactured scarcity, fake anchors, and confirmshaming are dark patterns; they win the click and lose the trust.\n\n---\n\n## 7. Gestalt grouping (brief — see `layout-and-composition`)\n\nThe Gestalt principles (Wertheimer, Koffka, Köhler, 1920s; **Common Region** and **Uniform Connectedness** added later by Palmer & Rock) describe how the eye groups before it reads:\n\n- **Proximity** — elements placed close together are perceived as one group. Spacing *is* grouping.\n- **Common Region** — elements inside a shared boundary (a card, a panel) read as a set, even if far apart.\n- **Uniform Connectedness** — elements joined by a line or shared background read as connected — the strongest grouping cue.\n\nIn practice: control grouping with *whitespace and containers*, not dividers. A form field and its label belong to the same region; a save button belongs near what it saves. The full Gestalt treatment — similarity, closure, continuity, figure\u002Fground — lives in the **`layout-and-composition`** skill; don't re-derive it here.\n\n---\n\n## 8. Do \u002F Don't\n\n| Do | Don't |\n|---|---|\n| Make frequent, important targets big and near; use edges\u002Fcorners (Fitts). | Cram tiny icon buttons at small gaps, or give a big button a small hit area. |\n| Reduce and group choices; offer a sensible default (Hick). | Dump 40 ungrouped options, or fragment one choice into 10 screens. |\n| Chunk data into meaningful units (Miller). | Cite \"7±2\" to cap menu items. |\n| Honor platform conventions for plumbing (Jakob). | Reinvent the scrollbar, back gesture, or nav to \"look fresh.\" |\n| Push complexity into the system (Tesler); forgive input formats (Postel). | Demand exact formats; or accept genuinely broken input. |\n| Respond \u003C400ms; use optimistic UI + skeletons (Doherty). | Block on a spinner, or add a 600ms transition that re-adds the wait. |\n| Design the peaks and the *ending* deliberately (Peak-End). | Polish the average and leave an abrupt blank\u002Ferror finish. |\n| Use polish to earn trust (Aesthetic-Usability)… | …but let beauty mask flaws or skip usability testing. |\n| Emphasize one focal point (Von Restorff). | Make three things \"primary\" — emphasis on all = emphasis on none. |\n| Show progress; front-load it (Goal-Gradient, Zeigarnik). | Reset a progress bar or invent endless open loops. |\n| Put critical info in the task path (Selective Attention). | Style essential UI like an ad banner. |\n| Use biases to help users decide (anchoring, defaults). | Weaponize them — fake scarcity, fake anchors, confirmshaming. |\n\n---\n\n## 9. Summary table (law → use it for → pitfall)\n\n| Law | Attribution | Use it for | Pitfall |\n|---|---|---|---|\n| Fitts's | Fitts, 1954 | Size\u002Fplace targets; exploit edges & corners | Tiny clustered buttons; visual ≠ hit area |\n| Hick-Hyman | Hick & Hyman, 1952 | Cut\u002Fgroup choices; defaults | Death-by-wizard; over-fragmenting |\n| Miller's | Miller, 1956 | Chunk & format data | \"7±2\" as a hard menu cap |\n| Jakob's | Nielsen, 2000 | Honor conventions | Reinventing plumbing |\n| Tesler's | Tesler, ~1980s | Shift complexity to system | Exporting parsing to the user |\n| Postel's | Postel, 1980 | Forgive input, clean output | Swallowing real errors |\n| Doherty | Doherty & Thadani, 1982 | \u003C400ms; optimistic UI, skeletons | Blocking spinners; slow transitions |\n| Peak-End | Kahneman et al., 1993 | Design peaks + endings | Neglecting the finish |\n| Aesthetic-Usability | Kurosu & Kashimura, 1995 | Polish earns trust\u002Fforgiveness | Masking real usability flaws |\n| Von Restorff | von Restorff, 1933 | One distinct focal point | Emphasizing everything |\n| Serial Position | Ebbinghaus | Important items at start\u002Fend | Burying key action in the middle |\n| Goal-Gradient | Hull, 1932; Kivetz 2006 | Progress bars; endowed progress | Resetting\u002Flying progress |\n| Zeigarnik | Zeigarnik, 1927 | Checklists; open loops | Endless un-closable loops |\n| Cognitive Load | Sweller, 1988 | Cut extraneous load | Hiding essentials (raises load) |\n| Selective Attention | Simons & Chabris 1999; Benway & Lane 1998 | Put key info in task path | Banner-styled essential UI |\n| Flow | Csíkszentmihályi, 1975 | Fast, clear, uninterrupted | Mid-task modals\u002Fupsells |\n| Recognition>Recall | Nielsen heuristic, 1994 | Pickers, autocomplete, visible state | CLI-style novice tasks |\n| Parkinson's | Parkinson, 1955 | Honest deadlines\u002Ftimers | Fake urgency |\n| Pareto | Pareto \u002F Juran | Prioritize the vital 20% | Ignoring the long tail |\n| Occam's | Ockham | Simplest flow that works | Over-simplifying past Tesler floor |\n| Loss aversion \u002F Anchoring | Kahneman & Tversky, 1979\u002F1974 | Framing, comparison, defaults | Coercive dark patterns |\n| Choice overload | Iyengar & Lepper, 2000 | Curate; recommend a default | Confusing with Hick (speed vs paralysis) |\n| Gestalt grouping | Wertheimer et al.; Palmer & Rock | Group via space & regions | Dividers instead of whitespace |\n\n---\n\n## 10. Cross-device application\n\nThe laws are universal; their *thresholds* shift by input method and context.\n\n| Law | Mobile \u002F touch | Desktop \u002F pointer | Watch \u002F TV \u002F voice |\n|---|---|---|---|\n| **Fitts's** | Touch targets **≥44×44pt (iOS) \u002F 48×48dp (Android)**, ≥8px apart — the finger is a fat, imprecise pointer with no hover. Thumb-reach zones matter: primary actions in the bottom third. | Precise cursor allows smaller targets, but still respect ≥24px clickable and use screen edges\u002Fcorners (infinite targets) the mouse can slam into. | Watch: huge targets, few per screen. TV: D-pad focus order *is* the target model — distance = button presses. Voice: no spatial targets; \"distance\" is dialog depth. |\n| **Hick's** | Small screen forces fewer visible choices — lean on progressive disclosure, sheets, and defaults harder than on desktop. | Room for more options, but still group; menus and command palettes scale choice without scaling decision time. | Severe choice limits — 2–4 options per screen on watch\u002FTV; voice must offer ≤3 spoken options or it overflows memory. |\n| **Doherty** | Perceived performance is *more* critical — flaky networks. Lean on optimistic UI, skeletons, prefetch, and offline-first; never block the thumb on a round-trip. | Faster networks raise the bar — under 400ms is the floor, 100ms feels instant. | Voice has its own latency budget: a reply must begin \u003C1s or the interaction feels broken; fill with a brief acknowledgment. |\n| **Miller \u002F Cognitive Load** | Tiny viewport = brutal extraneous-load budget; chunk aggressively, one primary task per screen. | More room to show context — but don't mistake space for license to clutter. | Watch\u002Fvoice: hold almost nothing — strip to a single decision; never recite a long list aloud. |\n| **Jakob's** | Honor *platform* conventions (iOS vs Android navigation, share sheets, back behavior) — see `platform-conventions`. | Honor web\u002Fdesktop conventions (menu bar, right-click, keyboard shortcuts). | Honor the platform's own paradigm (watch crowns, TV remotes, voice turn-taking). |\n\n**The through-line:** smaller and less-precise the input, the *larger* the targets, the *fewer* the choices, the *faster* the response must feel, and the *less* the user can hold in memory. Design for the most constrained context your screen will run in, then expand — not the reverse.\n\n---\n\n## 11. Using the laws — workflow & worked example\n\nThe laws map to stages of a design. Reach for them in this order when building or auditing a screen:\n\n| Stage | Question | Laws that answer it |\n|---|---|---|\n| **Structure** | How many things, grouped how? | Hick (count), Miller (chunking), Gestalt\u002FCommon Region (grouping), Pareto (which 20% to surface) |\n| **Hierarchy** | What's the one focal point? | Von Restorff (distinct focal point), Serial Position (ends), Selective Attention (in the task path) |\n| **Targets** | Can they hit \u002F reach it? | Fitts (size, distance, edges), cross-device touch minimums |\n| **Flow & speed** | Does it stay responsive and uninterrupted? | Doherty (\u003C400ms), Flow (no mid-task interruptions) |\n| **Memory** | Are we making them remember? | Recognition over recall, Miller, Tesler (system absorbs it) |\n| **Input** | Are we forgiving? | Postel (liberal input), Tesler (parse it for them) |\n| **Motivation** | Will they finish? | Goal-Gradient (progress), Zeigarnik (open loops), Loss aversion (framing) |\n| **Memory of it** | How will they recall the experience? | Peak-End (peaks + ending), Aesthetic-Usability (polish → trust) |\n\n**Worked diagnostic — a sign-up form that converts poorly.** Walk the laws as a checklist:\n\n- *Structure:* 14 fields shown at once → **Hick** + **Cognitive Load** violation. Cut to the 4 the account genuinely needs now; defer the rest (Tesler — derive what you can server-side; Pareto — most fields aren't load-bearing for signup).\n- *Targets:* \"Create account\" is a 14px text link bottom-right → **Fitts** violation on the most important action. Make it a full-width 48px button.\n- *Speed:* submit shows a blank spinner for 2s → **Doherty** + **Flow** violation. Optimistic transition to the next step; validate in the background.\n- *Input:* email rejected for a trailing space → **Postel** violation. Trim and case-fold silently.\n- *Memory:* \"enter the code from the previous screen\" → **Recognition over recall** violation. Carry it forward or show it.\n- *End:* success lands on a blank dashboard → **Peak-End** miss. Add a brief \"You're in\" moment and a clear first action.\n\nSix named laws, six concrete fixes, each defensible in review by its source. That's the point of the catalogue: it turns \"this feels off\" into \"this fails Fitts, here's the threshold.\"\n\n**The squint\u002Fmeasure tests:** for **Fitts**, drop the design to mobile size and try to tap each primary action with a thumb — if you miss, it's too small or too cramped. For **Hick\u002FLoad**, count the decisions visible above the fold; more than ~5 unrelated ones is a smell. For **Doherty**, profile the p95 of every interaction and flag anything over 400ms for an optimistic-UI treatment. For **Von Restorff**, squint at the screen — exactly one element should still read; if two compete, your focal point is split.\n\n---\n\n> Use a law to *diagnose* (name what's wrong and why) and to *justify* (defend a decision in review with its source). They are constraints on human cognition, not preferences — but every one has a dual-use edge. Apply them to serve the user's goal; the moment a law is used to trick rather than help, it's a dark pattern. When in doubt, the canonical attributed reference for the named \"Laws of UX\" is Jon Yablonski's lawsofux.com; the underlying findings trace to the researchers credited in each block above.\n",{"name":5,"tags":23,"description":7},[24,25,26,27,28],"ux","psychology","cognition","laws-of-ux","principles","main","4911ae44bbb35beef4511ba298475ba5a82b7e1c","design-system-skills\u002Flaws-of-ux-and-psychology",0,"https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta","https:\u002F\u002Fdocs.vanta.theft.studio","https:\u002F\u002Fgithub.com\u002Fjpoindexter","jason.theft.studio","Just some guy trying to build stuff","2026-11-12 17:11:35",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add jpoindexter\u002FVanta --skill laws-of-ux-and-psychology",{"tool":45,"command":46},"bunx","bunx skills add jpoindexter\u002FVanta --skill laws-of-ux-and-psychology",{"tool":48,"command":49},"pnpm","pnpm dlx skills add jpoindexter\u002FVanta --skill laws-of-ux-and-psychology","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fdesign-system-skills\u002Flaws-of-ux-and-psychology\u002FSKILL.md",true,[],[54,61,68,75,82,88],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7582PEM7XM8B98VFRDV0C0J","write-changelog","Turn a range of commits into a user-facing changelog","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fsrc\u002Fmigrate\u002F__fixtures__\u002Fopenclaw\u002Fskills\u002Fwrite-changelog\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7582KTQJMP5Y7GS83MS1C7Z","debug-flaky-test","Reproduce and isolate a flaky test before fixing it","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fsrc\u002Fmigrate\u002F__fixtures__\u002Fopenclaw\u002Fskills\u002Fdebug-flaky-test\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7582HG7XFM4Z5NGG1YFECT8","triage-incident","First 10 minutes of an incident — stabilize, then diagnose","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fsrc\u002Fmigrate\u002F__fixtures__\u002Fhermes\u002Fskills\u002Ftriage-incident\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7582DQABK7A96XHMB770KQZ","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fskills-library\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7582BBK8H0HGSXKK08FCXJ1","vanta-port-adapter","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fskills-library\u002Fvanta-port-adapter\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M75828P8PX5XSBMJ2BVVDA9Y","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fskills-library\u002Ftest-driven-development\u002FSKILL.md",[],[]]