Design system change management
summary
Burberry decides that a design system cannot assume seamless runtime integration across independent product teams so the team builds a central reference site that collates design specifications, UI components and underlying logic and acts as a quality benchmark. Engineering rejects making the common repo the system because of autonomy and compatibility concerns, so the organisation adopts a loose rather than strict governance model. Practical tooling tactics include Figma version numbers (Greg Hunting’s approach) and an explicit deprecation policy; the compromise improves cross-team alignment.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:28Should the Component Library of Your Design System Act as a Reference or Be Directly Integrated into Your Apps
- 2:16Change Management of Design Systems
- 3:49Challenges Associated with Change Management
- 8:28How Integrated Are Your Design and Engineering Teams
- 8:54What Autonomy Do Your Engineers Have outside of Their Regular Delivery To Make Ui Updates
- 10:39Policy for Deprecation of the Older Versions of Components
related talks
20mGrand visions for a design system grounded in reality
23mDesign Systems 101
46mBuilding & Managing Design Systems
20mDesign Systems for the Rest of Us
18mDesign Systems in Practice
01h 03mDesign System Pitfalls & How to Escape Them
29mWorkflow in the Age of the Design System
57mBulletproof development with design systems