Summary
Design systems are essential for creating cohesive and scalable products. By providing a shared set of design guidelines, components, and styles, design systems help ensure consistency and efficiency throughout the design process. In this talk we’ll go through the best practices when creating and maintaining a Design System including different strategies, approaches to token creation, making good use of overrides, setting up principles and guidelines and how to scale a design system so that it becomes useful for design a dev teams alike.
Key Insights
-
•
Design systems serve as agreements that align design, development, product, and marketing teams around consistent UI rules.
-
•
The atomic design model builds UI from basic tokens to atoms, molecules, and templates, promoting scalable component creation.
-
•
Separating styles (colors, typography) from symbols (UI components) enables easy global updates in design systems.
-
•
A device-agnostic organization of components simplifies multi-platform updates by grouping variants inside each component.
-
•
Flat component hierarchies prevent navigation complexity and speed up UI element discovery and usage.
-
•
Documenting design system decisions and architecture helps onboard new team members and maintain consistency over time.
-
•
Managing overrides restricts what can be changed in component instances, reducing inconsistencies and errors.
-
•
Establishing a design system council with cross-functional stakeholders ensures alignment and evolves the system thoughtfully.
-
•
Version starring in tools like Sketch allows safe iterative work without disturbing team members until updates are published.
-
•
Including content guidelines and examples in design system documentation is essential but often underdeveloped and manual.
Notable Quotes
"Design system is basically an agreement that helps create a sense of consistency and familiarity in all the UIs that you create."
"Keeping styles separate from symbols makes it much easier to update colors or typography across your entire system."
"If you organize your design system device agnostic, you can update one component with all desktop, mobile, and tablet versions inside."
"Try to make your component hierarchy as flat as possible because tall, nested structures become hard to navigate."
"Respect your design system rules to ensure consistent experiences across your product and teams."
"Establish a design system council where all stakeholders gather regularly to maintain and evolve the system."
"Use the latest version starring feature so your team only gets updates when they’re ready, avoiding constant notifications."
"Iteration is the golden rule of design, including iterating on your design system rules themselves."
"Leave some space for creativity in your design system so designers can innovate without breaking consistency."
"Document your design decisions and architecture visually so new team members can quickly understand your system."
Or choose a question:
More Videos
"If growth board content overlaps with quarterly business reviews, don’t do both; instead, inject an outcome mindset into existing meetings."
Kit Unger Jackie Ho Veevi Rosenstein Vasileios XanthopoulosTheme 2: Discussion
January 8, 2024
"Adaptability isn’t weakness, it’s strength."
Mariesa LenzWhat Beekeeping Taught me about Product Teams
October 29, 2025
"Doing research is not always the most natural transition for people who don't really care about research."
Jesse ZolnaInviting the Whole Org to Come See For Yourself
March 30, 2020
"Keeping your craft sharp, learning new tools like auto layout in Figma, and challenging yourself help maintain relevance."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"The relationship with AI is like having a gopher or minion — don’t give it the final decision."
Louis Rosenfeld Billy Carlson Jon Fukuda Maria TaylorHow AI will Change DesignOps Tooling
October 3, 2023
"Optimizing something for ease of use does not mean it’s best for humanity — infinite scroll is a cautionary example."
Sheryl CababaExpanding your Design Lens with Systems Thinking
March 28, 2023
"Adoption is the only thing that matters in innovation. If you’re not changing behavior, you haven’t innovated."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"Not every head of design is the right leader for every phase of organizational maturity."
John DevanneyThe Design Management Office
November 6, 2017
"Mural democratizes collaboration by letting people contribute regardless of seniority or location."
Erika FlowersIntroduction to MURAL for UX
June 11, 2021
Latest Books All books
Dig deeper with the Rosenbot
How should I choose communication channels and message formats to effectively share research insights?
How do research operations teams manage the tension between consolidating tools and needing specialized capabilities?
What are practical strategies to build influence for research insights across multiple dispersed teams?