Simplicity is Not Simple
summary
Argues that simplicity is a concrete engineering goal: identifies how products become complicated, offers methods—subtract consolidate clarify—and shows real changes made on Android (navigation gestures setup flow volume controls notifications and Digital Wellbeing) plus examples like Amazon one‑click and terrible parking kiosks. Explains three iterative levels (structure flow interface), measures to spot bloat, and tradeoffs where adding labels or steps improves clarity. Demonstrations of what was built and how it actually simplified user work make this practical not philosophical.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:45Speaker introduction
- 1:05Simplicity challenge today
- 2:10Products as systems
- 5:05Complicated vs complex systems
- 6:09Chaotic systems can't simplify
- 8:59Naturally complex systems
- 10:24Self-created complexity
- 11:31Unnecessary product complexity
- 14:22Problem of max complication
- 16:10Simplicity can harm
- 18:20Ease versus friction
- 21:10Oversimplification caution
- 23:43Reducing product complication
- 27:52Simplification after launch
- 28:57Signs of unnecessary complexity
- 36:03Foundational simplification methods
- 39:37Google's simplification techniques
- 47:05Conservation of complexity
- 48:30Measuring simplicity
- 50:19Closing & Q&A
related talks
42mSimplicity is not simple
22mKeynote ‘The Art of Simplicity’
41mKeynote: The Art of Simplicity
41mEnchant, Simplify, Amaze: Android's Design Principles
28mThe awful design of everyday things
33mBeyond Buttons: Crafting Satisfying & Easily Marketable Products
20mOver-complicated? Over-simplified? The UX Efficient Frontier
53mIntentional Code - Minimalism in a World of Dogmatic Design