What brand design can learn from software developments
summary
Argues that brand teams should adopt three developer practices — design patterns, continuous delivery, open source governance — and shows one applied outcome: a relaunched MetLife creative system that retires Snoopy, uses a flexible grid with overlapping panels and market‑specific photography, and enforces a governing body plus agency training so new local designs can be proposed as reusable components. Claims these tools let large, legacy product sets scale creative work and reduce one‑off chaos.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:18Do startups need brands
- 3:07Gothic architecture
- 4:00Design building blocks
- 5:05Creative systems
- 7:25Reusable objects
- 8:07Patterns and creativity
- 9:30Continuous delivery
- 11:38Open source governance
- 13:40Conclusion
related talks
38mEnough Design
13mHolistic approach in product design
43mThe evolution of brand identities
23mDesign Systems and Creativity
22mRebranding, or the subtle art of juggling new and legacy design systems
28mTools of Destruction
25mDesign and (...), a look at design leaders taking on more responsibilities
40m“Where We Can Go”