Summary
Drawing from over a decade of consulting with major companies like IBM, Cisco, Marriott, and Salesforce, the speaker explores the complexities and best practices of design systems in large organizations. He recounts initial engagements, such as with IBM's VP of Design, who emphasized the need for a system encompassing multiple products rather than isolated component libraries. Using Google's Material Design and Salesforce as examples, he highlights the importance of holistic design language covering typography, color, motion, and voice, and the need to break down design into atomic parts for consistency. He illustrates exercises like component cutouts and prioritization worksheets to organize efforts. The speaker stresses that a design system is not just a static artifact but a living product requiring strategic alignment, leadership support (citing John Wiley from Google), dedicated teams (highlighting Gina from Salesforce), and federated contributions. He shares insights on engaging flagship products, avoiding contentious areas like homepages, and radiating influence through navigation and core flows, as demonstrated in Marriott and Cisco projects. He also underscores the challenges of scaling teams, decision-making methods (notably Cap Watkins' care-level chart), and the value of prototypes, such as the one developed with Livia Lavatte, to align stakeholders and demonstrate progress. Ultimately, the talk paints design systems as dynamic ecosystems that connect people, processes, and products to improve efficiency, quality, and customer experiences.
Key Insights
-
•
Design systems succeed when treated as living products with dedicated roadmaps, backlogs, and support teams.
-
•
A design system must address multiple flagship products initially (3-5) to maintain manageable scope and influence.
-
•
Visual style alone is insufficient; cohesion requires alignment of typography, color, iconography, motion, and voice.
-
•
Centralized design system teams can balance cohesion across products but risk losing product-context influence.
-
•
Federating design system contributions across teams encourages diverse inputs and scalability.
-
•
Strong leadership endorsement, including executive support, is critical for design system success.
-
•
Prototypes stitching multiple product teams' work help communicate design system value to stakeholders.
-
•
Avoid focusing design system efforts on contentious areas like homepages where organizational conflicts run high.
-
•
Implementing decision frameworks based on stakeholders' care level improves resolution and autonomy.
-
•
Including content strategy and voice/tone leadership enriches design systems beyond UI components.
Notable Quotes
"I don't want a component library for the account home. I want a system for all of that."
"Google’s Material Design has echoes of design decisions flowing through many of their applications."
"Visual style isn’t just enough to make something feel cohesive."
"A design system is done not when the style guide is launched, but when it positively impacts customer experience."
"You have to treat the design system like a product that everyone in your organization will use."
"Getting exact endorsement from the top helps your cause immensely."
"You need to be the connector between people trying to drive decisions and others influencing them."
"Sometimes alignment work isn’t enjoyable, but it’s part of the job for design system success."
"Don’t just think about design systems as an artifact but as a living ecosystem connecting people, tools, and products."
"Short-term pairings with different design people help bring back contributions into the central system."
Or choose a question:
More Videos
"Slack has over 650 people actively talking and sharing experiences right now."
Bria AlexanderOpening Remarks
November 18, 2022
"If you create a separate team to work on the future, make sure they stay focused on the future, or you’ll never get out of the trap."
Ted Booth Sam Ladner Fredrik Matheson Russ UngerDiscussion
June 8, 2016
"Psychological safety is the felt permission for candor — permission to be honest without fear of negative consequences."
Alla WeinbergWorkers Are Sick of Change: The Cure is Psychological Safety
June 6, 2023
"Banks have 144 years of tech baggage making digital-first mindsets hard, and culture change is just as important as technology."
Julie Gitlin Esther RaiceDesign as an Agent of Digital Transformation at JPMC
June 9, 2021
"The pace of radical participatory research must match the pace of availability, trust, and relationship."
Victor UdoewaRadical Participatory Research: Decolonizing Participatory Processes
March 9, 2022
"I wrote the book because people have a lot of questions about how to become a product manager or how to work with product managers or what is product."
Christian CrumlishIntroduction by our Conference Chair
December 6, 2022
"Even though we are virtual, we are still a community and we are obligated to treat each other with dignity and respect."
Bria AlexanderDay 2 Welcome
September 24, 2024
"I was literally making up our strategy even though the company was profitable and growing."
Simon WardleyMaps and Topographical Intelligence
January 31, 2019
"Incremental change was used to drive a radical shift in policy despite initial resistance."
Sarah AuslanderIncremental Steps to Drive Radical Innovation in Policy Design
November 18, 2022
