Best Practices when Creating and Maintaining a Design System
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
"It is impossible to survive in this industry by pushing against the current all the time; you must put yourself in positions to leverage the current."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"We’re all capable of creating and perpetuating toxic work relationships."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Tools are a blessing and a curse; they’re not people and they can’t replace the relationships you need to get the work right."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"If you are a glue person expecting to be indispensable, you are more dispensable than you think. But if you’re a catalyst moving information and translating to action, that’s more valuable now."
John CutlerThe Alignment Trap
November 29, 2023
"Just because you can color code something doesn’t mean you should."
Abby CovertStuck? Diagrams Help
October 27, 2022
"Use four simple questions to find out what people really want and why — it avoids misaligned efforts."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"Too often, futures imaginaries want to erase or align difference rather than reckon with it."
Devon PowersImagining Better Futures
March 9, 2022
"The best teams I know are a quarter ahead of the product roadmap, seeking out impactful strategic research projects themselves."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Skills are like onboarding material for the model; you write them as simple markdown files that describe workflows or tools."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
