Everything so far in this course is about making a product usable — easy to understand, easy to operate. This next stretch of lessons is about something related but different: behavior design — understanding why people act the way they do, so a product can be designed to actually support the behavior it's meant to enable.
Psychologists describe human thinking as running on two systems. System 1 is fast, automatic, and intuitive — it's what reacts to a red error message or a familiar icon without conscious effort. System 2 is slow, deliberate, and effortful — it's what engages when reading terms and conditions or comparing pricing plans carefully. Most everyday product interactions run on System 1; a design that forces System 2 thinking for a simple task (a confusing form, an unclear button) creates real friction.
Design decisions sit on a spectrum between two ends: fully conscious, deliberate choices (comparing options, reading details) and fully automatic habits (tapping a familiar app icon without thinking). Neither end is "better" — a banking app's transfer confirmation should sit closer to the deliberate end on purpose, while a habit-forming daily-use app benefits from sitting closer to the automatic end.
| System | Speed | Good product fit |
|---|---|---|
| System 1 (fast, intuitive) | Instant, low effort | Everyday, repeated actions — navigation, familiar icons, habitual flows |
| System 2 (slow, deliberate) | Effortful, considered | High-stakes or irreversible actions — payments, deletions, legal agreements |
Why this comes first
The lessons ahead build directly on this idea — Fogg's Behavior Model and the Hook Model are both, in effect, frameworks for understanding which system a given product moment is designed for.