i

The Basement

B · 4 of 6 rooms

Everything upstairs shows interaction working. This floor shows it breaking — not to mock, but because a fault traced honestly points back at the exact principle it violated. The basement is the Stairwell’s evidence room.

House rule: no failure ships without the principle it broke and the official record behind it.

FLR·B·001

The Norman Door

broke: affordance

A door whose handle says pull while its hinge says push. You pull, it resists, you push, you feel briefly stupid — and that misplaced feeling is the entire lesson of this room. Don Norman's founding argument: when a person fails at a door, the fault is not the person, it is a missing or lying affordance. A flat plate can only be pushed; a graspable bar begs to be pulled; a door that needs a sign saying PUSH has already failed as a door.

The Norman door is the basement's patron exhibit because it scales. Every interface that requires a tooltip to explain which way it opens — the icon that doesn't look tappable, the card that is secretly a button, the swipe nobody discovers — is the same door wearing different hardware.

The lessonAffordances are the interface's honest signage: the shape of the thing should announce its use. When users fail predictably, redesign the handle, not the user.
the handle: “pull me” but… hinge side physics: “push me”
FIG B·001 — hardware and physics giving opposite instructions.
The recordNorman, The Psychology of Everyday Things (1988; retitled The Design of Everyday Things) — the concept's citable birth, plus the Gibson (1979) origin of "affordance" and Norman's own later clarification of the term's drift.
StairwellAffordance — including the Gibson→Norman drift, documented there.
Upstairs kinFloor 2's every component carries "the trade it was built to make" — the anti-Norman-door discipline.
FLR·B·002

Dark Patterns

broke: honesty itself

Everything else in this basement is incompetence; this exhibit is intent. A dark pattern — the field now says deceptive pattern, following Harry Brignull, who coined the original term in 2010 and later led the renaming — is an interface engineered to make you do what the business wants by exploiting exactly the principles the rest of this building teaches. The same knowledge, aimed the other way.

The register here is factual and increasingly legal: the FTC's click-to-cancel rulemaking, the EU's DSA provisions and GDPR consent case-law mean several of these specimens are no longer merely rude — they are enforcement actions with docket numbers. The basement documents the named types:

  • Roach motelEasy in, deliberately hard out — the one-click subscribe beside the phone-call cancel.
  • ConfirmshamingThe decline link written to insult you: “No thanks, I hate saving money.”
  • Sneak into basketThe pre-added insurance you must notice to remove.
  • Drip pricingFees revealed only at the final step, after the effort is sunk.
  • Privacy ZuckeringConsent flows where the sharing option glows and the refusal hides.
  • False urgencyThe countdown that resets; the “2 rooms left” that never sells out.
The lessonEvery deceptive pattern is a legitimate principle inverted — friction, defaults, framing, urgency. The building's knowledge is dual-use; this room is where the Institute says so plainly.
SUBSCRIBE one click CANCEL exit, eventually
FIG B·002 — the roach motel, as floor plan.
The recordBrignull, deceptive.design taxonomy (2010–) and Deceptive Patterns (2023); FTC click-to-cancel rule and enforcement record; EU consent-design case law.
StairwellDefaults, friction & framing — the principles that make these work, and the ethics clause attached to each.
Upstairs kinFloor 4's Cancellation flow — the battleground room where regulation is currently redrawing the pattern live.
FLR·B·003

The Hawaii Alert, 2018

broke: constraint & confirmation-of-consequence

On the morning of 13 January 2018, an operator at Hawaii's Emergency Management Agency intended to run the routine internal test of the ballistic-missile alert system and instead sent the live warning — BALLISTIC MISSILE THREAT INBOUND TO HAWAII. SEEK IMMEDIATE SHELTER. THIS IS NOT A DRILL — to every phone in the state. Thirty-eight minutes passed before the official correction.

The official post-mortems (FCC; state) describe the interface: the live alert and its test sat as near-identical items in the same menu, the confirmation step was the same reflexive are you sure? that guarded both, and — the detail this building exists for — there was no way to un-send. Every floor of the Institute is present in the failure: a menu without separation of consequence (Floor 3), a confirm where the stakes demanded ceremony (the Undo vs Confirm entry's limit case), no recovery flow (Floor 4), and a whole system (Floor 5) where one dropdown was load-bearing for a state's peace of mind.

The lessonConsequence must be legible in the interface's very geometry: the catastrophic action cannot live one row away from the routine one, dressed identically. Confirmation is not ceremony-proportional by default — the designer must make it so. And for the truly irreversible, the absence of undo is itself a design decision, made by whoever didn't make it.
STATE EMA — ALERT MENU Amber Alert (CAE) – Kauai Tsunami Warning (CEM) – State PACOM (CDW) – State Only DRILL – PACOM (CDW) – State Only the live one the drill, one row down
FIG B·003 — reconstruction after the official reports: consequence without geometry.
The recordFCC Public Safety & Homeland Security Bureau report (2018); Hawaii EMA internal investigation; both public.
StairwellConstraint · mapping · error tolerance — three principles, one morning.
Upstairs kinThe menu is a Floor 3 pattern; the missing un-send is Floor 4's recovery flow, absent where it mattered most.
FLR·B·004

Mode Error

broke: visibility of system state

A mode is when the same action means different things depending on hidden state — and a mode error is the moment the human's model of that state and the machine's diverge. Caps Lock is the everyday specimen: the keyboard you're using is briefly not the keyboard you think you're using. The grave specimens live in aviation's human-factors literature, where decades of documented incidents trace to autoflight mode confusion — crews commanding one thing while the automation, legitimately and lethally, was in a state that heard another. That body of official reporting is why "mode awareness" is a certification topic and not a design nicety.

Software's daily mode errors are gentler but constant: typing into the wrong window, the vim novice's panic, the camera that was on video when you pressed for a photo, the message sent to the channel you forgot you'd switched to. The pattern is identical at every scale — state changed; the announcement didn't reach the human.

The lessonModes are sometimes necessary; invisible modes never are. Every mode needs a persistent, glanceable announcement — and the more consequential the divergence, the louder the state must dress. The best fix is fewer modes; the honest fallback is modes that cannot be missed.
A a A CAPS — hidden state one key, two meanings — the mode decides, quietly
FIG B·004 — the smallest mode error, standing in for the largest.
The recordNorman on modes (1988); aviation human-factors and accident-investigation literature on autoflight mode awareness (official reports; FAA/NTSB and international equivalents).
StairwellVisibility of system state — Nielsen's first heuristic, and the modal's namesake risk (Floor 3).
Upstairs kinFloor 1's Seven States — the discipline that makes state announce itself at the smallest grain.

Not open yet

Two rooms are planned and unwritten. They are named because a basement that shows only its finished exhibits is doing the exact thing this floor is about.

  • Cookie banner
  • Accidental commerce