“For & Against Consistency”
summary
Argues that internal, external, real-world consistency are distinct trade-offs and gives concrete failures and wins: a 1966 M2‑F2 test flight at 8,000 ft descends at 18,000 ft/min and requires ignoring cockpit procedures to stop pilot induced oscillation after a simulator brake‑handle/wheel mismatch; Google Docs shows inconsistent labels (share vs add people) and mixed Material/Kennedy modals; emoji 1F601 displays wildly different tones across platforms; design tools reuse shortcuts (Photoshop → Sketch → Principle) to leverage procedural memory and avoid pilot induced oscillation in UIs.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:18Disclaimer
- 9:52What happened?
- 11:55Intuitive
- 12:22Predictable
- 19:371. Color 2. Typography
- 20:45never underestimate
- 23:18Rectangle Rectangle
- 26:45software is magic
- 27:04Why be inconsistent?
- 27:17Technology should make things easier than they are in the real world.
- 28:27BE INCONSISTENT When you want to stand out
- 28:56BE INCONSISTENT When you want to have fun
- 29:26BE INCONSISTENT To use the advantages of technology
related talks
21mConsistency considered harmful
36mConsistency is Key - Working with a Design System
03m"A Story about Design and Experience"
15mHoly War between Designers & Developers
01h 05m“Wouldn’t it be cool…” and other bad design approaches
20mMicrointeractions for the System: Design in the Age of Techlash
40m“Where We Can Go”
37mConsistency is Key - Working with a Design System