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
"Please stop by the Rosenfeld Bookstore to check out signed books and brand new titles."
Bria Alexander Louis RosenfeldOpening Remarks Day 2
March 26, 2024
"We talked all about resilience, curated by myself yesterday."
Bria AlexanderDay 3 Welcome
September 25, 2024
"The infrastructure of civilization was someone else’s problem. What a lie that was. It was my problem this whole time."
Sha HwangThe Lost Year
June 11, 2021
"We didn’t have enough knowledge initially to have a strong opinion about what was good design for these users."
David CroninThe GE Design System and Thoughts about Craft at Scale
May 13, 2015
"A confusing, difficult hiring process is itself an equity issue—transparency helps reduce gatekeeping."
Charlotte Vorbeck Shahzma Esmail Edward Alton Sarah McArthur Ariel KennanPipeline to Civic Design
December 9, 2021
"Values determine the team environment you create; they permeate through leadership and affect performance and happiness."
Kim Holt Emma Wylds Pearl Koppenhaver Maisee XiongA Salesforce Panel Discussion on Values-Driven DesignOps
September 8, 2022
"Trust your UX team to represent each other when attending different scrum teams’ ceremonies."
Chris HodowanecAgile + User Experience: How to navigate the Agile landscape as an UX Practitioner
November 16, 2022
"It became less important to keep doing fresh research and more important to grow the collective team knowledge."
Scott Jensen Sarah Delaney Carmen LiuShort Take #2: UX/Product Lessons from Your Industry Peers
December 6, 2022
"How can I guide my community to design the form and behavior of light on the edge of becoming this?"
Greg PetroffExit Interview #1: Greg Petroff: From Silicon Valley Executive to Sonoma County Possibilitarian
September 24, 2025
