Navigating complex system updates
summary
Zalando updates a core product card that appears in 400 files with 40K instances and affects 50+ teams and ~140k component inserts per week; a wrong move risks a ~400 million euro fine. The team builds a product price component, uses Figma branching to sequence releases, and fixes a plugin called the lid in. Changes roll out with 95% adoption across screens go live on time and evidence shows no negative impact.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:31Our Team
- 1:35Shared Ownership
- 2:45Overview
- 5:00Joy
- 6:12Enabler
- 7:10Product Card
- 12:23Dynamic High
- 13:50Documentation
related talks
31mSlowly, then suddenly and all at once: building a design-led culture at Delivery Hero
19mEvolving systems with data and heart
23mHitting Ctrl+N: How to work through a design breakup
19mBehind the system: A showcase of files that inspire us
51mThe Power of Design Systems
12mDesign system change management
20mHigh Stakes: Building a Multi-Brand, World-Wide Design System
25mMulti-platform design system at Booking.com