Kent talks with Don Norman about why the core work of product engineering has not changed: watch people work, treat so-called user error as a design problem, and fix root causes instead of blaming symptoms.
Don walks through a remarkable arc from electrical engineering and cognitive psychology to Three Mile Island, Xerox PARC, Apple, and the first use of user experience in a job title. They talk about timing and failed products, cross-functional product teams, what AI changes for software builders, and why Don now cares most about designing for humanity, not only usability.
Don's career makes this episode unusually wide-ranging: early computing, human error, aviation safety, Unix, Apple product decisions, digital cameras, color TV, and the long arc from usable products to systems that shape society. The through-line is straightforward but demanding: if you want better products, watch what people actually do, notice the workarounds they no longer complain about, and treat clusters of small usability problems like real product debt.
The second half brings that thinking into the present. Don and Kent talk about AI coding tools as force multipliers that still need direction, architecture, and supervision, then zoom out to Design for a Better World and the Don Norman Design Award. The result is a conversation about product sense that spans decades without feeling dated: the tools change, but the responsibility to understand people, systems, and consequences does not.
Homework
- Spend time watching people do real work before you ask them for solutions; observation reveals the hidden setup, workarounds, and friction they now assume are just "how it works."
- After a release, step back and fix clusters of small usability issues as a system instead of waiting for one confusing bug to become catastrophic.
- Treat AI as a force multiplier you must instruct and supervise; stay responsible for the problem definition, architecture, and review.
Resources
Guest: Don Norman
Host: Kent C. Dodds
Video
