the four modes
before designing any surface, name its mode: what the visitor's success looks like here. the mode disciplines every later choice.
what it teaches
- Persuade — the visitor decides and acts; design is the product. landing pages, marketing, pricing. earn attention and action.
- Operate — the visitor completes a task. app UI, dashboards, settings. scanability, consistency, native expectations outrank expression; brand lives in precise details.
- Read — the visitor understands something. docs, guides, changelogs. structure for comprehension, then make the reading worth staying in.
- Experience — the visitor is inside the work itself. portfolios, galleries. the artifact leads from the first viewport; the interface recedes.
two subtleties:
- mode is per surface, not per project. a tool's landing page is Persuade even though the product is Operate; a fashion house's documentation is Read.
- mode is not stored globally. it persists only in that surface's brief — the next surface may differ.
why
design guidance without a mode collapses into averages — the landing page gets Operate's caution, the dashboard gets Persuade's drama, both wrong. naming the visitor's success first gives every later trade-off (palette strategy, type character, motion budget) an arbiter.
when to use
at the start of any new surface: choose the mode from the requested surface, never from the product's category.
good and bad
bad
product: workflow platformdesign mode: persuade
the product category is the shortcut, but the surface is an existing operator dashboard. persuasion styling on an operating tool adds drama where the visitor needs scanability and consistency — task time and error rate rise while the page looks "designed." the same shortcut in reverse gives a landing page the caution of a settings screen, and it fails to earn the action it exists for.
good
surface: workflow editorvisitor success: complete a configuration safelydesign mode: operate
the mode follows the local visitor outcome, so palette, type character, and motion budget get an arbiter before they are chosen — decisions stop being re-argued taste and become consequences of the named success. each surface stays optimized for its own job instead of averaged toward a house compromise.