Beyond the Toolkit: Spreading a System Across People & Products
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
"We don’t call them UX designers or front-end designers or visual designers. They’re all just designers."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"This DP&M tool is not just another knowledge base, it’s a living database that supports managing relationships and parsing information into views tailored to user roles."
Ellie Krysl Jon FukudaPlanned Right. Managed Right. Designed Right.
June 6, 2023
"Two-thirds of our internal team had experienced a late or lost delivery, reflecting real customer frustration."
Anat Fintzi Rachel MinnicksDelivering at Scale: Making Traction with Resistant Partners
June 9, 2022
"We all walked away better for it."
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020
"I prefer to think of my career as a series of trampolines and your resume as a portfolio of life experiences."
Maria GiudiceEmpowering change: Reigniting purpose, passion and impact in research
March 13, 2025
"Sharing is hustle — holding brown bags, office hours, town halls, and surveys to get feedback."
Nalini P. KotamrajuAn Organizational Story: Salesforce Lightning Design System
June 9, 2016
"Iterative engagement models mean we test, learn, and adapt rather than seeking a perfect solution from the start."
Aaron Stienstra Lashanda HodgeLeveraging Civic Design to Advance Equity and Rebuild Trust in the US Federal Government
December 8, 2021
"Sometimes the best way to understand a problem is to run the game multiple times and see why decisions differ."
Terry BuckmanWargaming (An Introduction)
August 10, 2023
"Your partners need to trust that you are going to make their goals your goals."
Jess GrecoClaiming your power: Practical tools for amplifying your unique voice
March 13, 2025
