How Great Products Make Hard Things Obvious: Teardowns

In earlier chapters you learned the principles. Now we watch them at work. We will take apart eight famous products and patterns, like a mechanic opening a clock. For each one we ask three questions: What was the hard problem? What made the solution feel obvious? And which principle explains the magic?

Before we start, a definition. When we say something "feels obvious," we mean the user just knows what to do, without reading instructions. That feeling is not luck. It is engineered.

The repeating recipe

Across every teardown below, the same four-step move comes up again and again. Learn it once, then watch each product perform it.

1. Hide complexity behind a clear conceptual model. A "conceptual model" is the simple mental picture you give the user (a blank box = "ask anything"; a sheet of paper = a document; LEGO bricks = blocks). They picture the model, never the machinery underneath.
2. Choose strong defaults. A "default" is the choice the product makes for you. Decide what 90% of people want, so almost nobody has to configure anything.
3. Give constant feedback. Every action produces an instant, visible, plain-language response. The user always knows the system heard them.
4. Remove steps and choices. Fewer options means faster decisions. Fewer screens means less to learn.

The named laws behind the recipe

Hick's Law (Hick–Hyman Law, 1952)

Named for William Edmund Hick and Ray Hyman. The time to make a decision grows logarithmically with the number of choices. "Logarithmically" means each extra option adds a smaller and smaller delay — but more choices still means slower decisions. It matters most for short lists like menus and buttons.

Affordance vs Signifier (Don Norman)

An affordance is a possible action an object offers (a chair affords sitting). A signifier is a perceivable cue that tells you the affordance exists and how to use it (a label, an arrow, a highlight). Norman added "signifier" in the 2013 revised edition of The Design of Everyday Things to clear up confusion. Keep them distinct: the affordance is the possibility; the signifier is the hint.

Direct Manipulation (Ben Shneiderman, coined 1982, paper 1983)

Three properties: (1) you see the object of interest continuously, ideally in its final form; (2) you act with physical gestures or labelled buttons, not typed commands; (3) actions are rapid, incremental, and reversible, with the effect immediately visible.

Jobs To Be Done (Clayton Christensen)

People "hire" a product to do a job. Understand the job, not the feature list.

Teardown 1 — Google Search: the blank box

Hard problem: index and rank billions of pages so anyone can find the right one. Obvious solution: a single empty box and one button. Principle: minimalism + Hick's Law. With one obvious choice, the decision is instant. The conceptual model is simply "type what you want."

Charmingly, the bare page was partly accidental. Marissa Mayer (Google's 20th employee and first female engineer) once asked co-founder Sergey Brin why the page was so empty; he reportedly said they had no webmaster and he did not do HTML. Early testers loaded the page and waited about a minute — so unused to white space that they thought more was still loading. Google added the bottom copyright line partly as a signal: "the page is done."

Teardown 2 — Apple / iPhone: touch the thing itself

Hard problem: a pocket computer that is also a phone, an iPod, and the internet — usable with no manual. Obvious solution: touch what you want. Pinch to zoom, swipe to scroll, tap to select. The iPhone (unveiled January 9, 2007) shipped with essentially no instruction booklet. Principle: direct manipulation plus strong affordances. A button looks pressable; a list looks scrollable. Steve Jobs called the finger "the most accurate pointing device in the world... one we're all born with." Killing the stylus and physical keyboard was the bet that let the whole screen become directly manipulable.

Teardown 3 — Stripe: "it just works"

Hard problem: accepting online payments once took weeks of merchant accounts, gateways, and confusing kits. Obvious solution: Stripe's promise of "payments in seven lines of code." Copy, paste, done. Principle: developer empathy — great docs, sane defaults, fewer steps. Stripe's documentation is an industry benchmark, with its famous three-column layout (navigation | explanation | live, runnable code). The recipe in plain sight: strong defaults out of the box, weeks compressed to a weekend, and clear test-mode feedback.

Teardown 4 — Superhuman: hire it to "feel fast"

Hard problem: email is a slow, heavy bottleneck. Obvious solution: a keyboard-driven client that feels instant, plus a human who onboards you. Principle: Jobs To Be Done. Customers do not hire Superhuman for "more features"; they hire it to feel fast and reach inbox zero. Founder Rahul Vohra enforces a "100-millisecond rule" — every interaction must respond under 100ms, the threshold where things feel instantaneous. Vohra personally onboarded the first ~200 users (concierge onboarding), and the team used Sean Ellis's product-market-fit survey to raise their "very disappointed without it" score from 22% to 58% in about a year by doubling down on what fans loved.

Teardown 5 — Linear: opinionated and keyboard-first

Hard problem: issue trackers bloat into slow, infinitely-configurable tools (the "Jira problem"). Obvious solution: an opinionated tool with one good way to work and a keyboard shortcut for nearly everything. Principle: strong defaults + remove choices (Hick's Law applied to the whole product). Linear deliberately constrains you with structures like Cycles, Triage, and Backlog instead of letting teams invent fifty custom statuses. Speed is treated as a core feature, not a nice-to-have.

Teardown 6 — Notion: everything is a block

Hard problem: one tool to be docs, wiki, database, and tasks, without drowning a blank-canvas user. Obvious solution: "everything is a block." Type "/" and snap bricks together. Co-founder Ivan Zhao calls it "LEGO for software." Principle: one powerful conceptual model (the block) hiding a flexible engine.

Teardown 7 — IKEA: wordless instructions

Hard problem: one assembly manual must work in dozens of languages. Obvious solution: drop words entirely — the stick-figure "IKEA man," arrows, and numbered pictures show rather than tell. Principle: visual signifiers (Norman) carry meaning without language. Text would need translating into around 35 versions per update, inviting mistranslation; wordless is one global, cheaper, lower-error artifact. IKEA's two stated rules: clarity (each step instantly understood) and continuity (a predictable flow between steps).

Teardown 8 — ATM & checkout: convention as obviousness

Hard problem: a stranger must complete a multi-step transaction under stress, with no training. Obvious solution: conventional, standardized flows: insert card → enter PIN → choose amount → take cash; or a checkout with a visible progress bar, one clear primary action per screen, saved address and card defaults, and confirmation at each step. Principle: convention and consistency — match the user's existing mental model so the next step is always obvious.

  Good checkout (obvious)        Broken checkout (hidden steps)
  [Cart]  ->  [Pay]  -> Done     [Cart] -> [Create account?!]
    |  progress bar shown          |  surprise shipping fee
    |  saved card default          |  no progress shown
    v                              v
  one click, confident          confused, abandons cart

The map at a glance

Notice how each teardown runs the same recipe. Google hides a ranking system behind a box (model + remove choices). The iPhone shows the object and reacts instantly (model + feedback). Stripe and Linear decide for you (defaults + remove steps). Superhuman obsesses over sub-100ms responses (feedback) tied to a single job. Notion gives one model but rescues it with templates (defaults). IKEA and the ATM lean on signifiers and convention so no words are needed at all.

Key takeaways

• The same four-step recipe powers every great product: clear conceptual model, strong defaults, constant feedback, fewer steps and choices.
• "Obvious" means the designer absorbed the complexity — it did not vanish, it moved off the user's shoulders.
• Keep affordance (the possible action) separate from signifier (the perceivable cue that reveals it).
• Hick's Law rewards fewer choices; direct manipulation rewards instant, reversible, visible feedback; JTBD reframes the real problem you are solving.
• Flexibility (Notion) is only friendly when defaults, templates, and good empty states guide the first step — the same rule applies to your own loading, empty, and error states.