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
"Don’t expect perfection with the toolkits on day one; iterative feedback and time will flesh them out."
Michele WongHelping Them Help Us
January 8, 2024
"Speculation fills in the gaps where past experience fails us, often seen in hesitation or pauses."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"We have to create human-centered organizations where people thrive by trust and recognition, grow with influence, and want to make a difference."
Christian BasonInnovating With People: Unleashing the Potential of Civic Design
December 8, 2021
"If these two voices don’t work for you, you can reach out at [email protected]."
Bria Alexander Louis RosenfeldOpening Remarks Day 2
March 26, 2024
"Blushing is an inherently systemic reaction to understanding what’s acceptable in a situation or not."
Josina VinkNavigating the pitfalls of systems thinking in service design
December 4, 2024
"Design ops is at the heart of how we can achieve outstanding quality and value in design."
Stephen PollardClosing Keynote: Getting giants to dance - what can we learn from designing large and complex public infrastructure?
November 7, 2017
"If you request the mobile website on desktop it usually works better than requesting the desktop website on mobile."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
November 17, 2022
"Flexibility goes both ways: consultants must adapt to the client’s way, but clients must allow consultants to bring new approaches."
Melinda BelcherInsider preview of Enterprise Experience 2020
May 28, 2020
"Our Jira integration will be two-way so you can link design activities to epics, user stories, or tasks."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
