## Core Insight Simplicity is defined from the perspective of the least experienced user of a piece of code. Design for normal people — geniuses can use simple things, but not all normal people can use complex things. The reverse is not true. ## The Mall Map Example The worst mall maps have a tiny yellow triangle labeled "the tiny yellow triangle means 'You are here'" in small text off to the side. The best have a giant red dot with "YOU ARE HERE" in front of you. To the designer, the triangle map seems reasonable — he spent so much time on it that he forgot it needed to be instantly readable to a stranger. The gap between designer familiarity and user experience is the source of most unnecessary complexity. ## Implications - **Design for the person least familiar with the code** — not for yourself - **Simplicity expands your audience** — a system usable by normal people is also usable by experts - **The familiarity trap** — complexity that feels simple to its author is invisible complexity to everyone else - **Context matters** — what is simple in one context (manual) is complex in another (billboard) ## Cross-Domain Connections - [[Confusion Kills Products]] — the same familiarity trap in sales/product copy: what's obvious to the builder is confusion to the customer - [[Fellow-Pupil Teaching Model]] — the same mechanism in teaching: masters forget what confused them, so recent learners often explain better - [[Genius as Bridge Infrastructure Not Stride - Justin Skycak]] — names the same gap as "expert blind spot": experts can't see the bridges (context) that novices lack ## Source - [[Code Simplicity by Max Kanat-Alexander]] — Ch 6: Simplicity