Design Thinking for Developers: Think out-of-the-box
summary
Argues that developers should adopt a human‑centric, empathy‑driven process with five concrete phases — empathize, define, ideate, prototype, test — using remote interviews, photo/video studies, body‑storming, Post‑it affinity mapping, dot‑voting and the four‑category prioritization. Recommends building low‑ and high‑fidelity prototypes (sketches, paper, Figma, Adobe Illustrator, 3D models) and iterating based on desirability/feasibility/viability. Gives a concrete success story — lowering truck tire pressure freed it from a bridge — and says workshops and prototypes reliably reveal better engineering solutions.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:13What is design thinking
- 5:12Out-of-the-box thinking example
- 8:27How design thinking helps
- 11:58Five phases of design thinking
- 13:03Empathize phase explained
- 17:02Define phase explained
- 21:18Ideate phase explained
- 27:04Prototype phase explained
- 30:39Testing phase explained
- 32:28Iterative process overview
- 33:36Why developers should learn design thinking
- 34:41Conclusion and Q&A
related talks
28mDesign thinking
30mDesign Thinking for Rubyists
41mDesign Thinking? Be Bold, get Radical
01h 11mWorkshop: Think Like a Designer
31mDesign Through a Developer's Eyes
01h 15mDesign Dive: An Immersive workshop on Design Thinking
59mPutting the Design Back in Architectural Design
41mLeadership By Design: How Design Thinking Can Help You Lead With Impact