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
"Horst Rittel introduced wicked problems to describe problems where consensus on definition is difficult, and calling them problems can be misleading—maybe they’re better called messes or tangles."
Hugh DubberlyProblems with Problems: Reconsidering the Frame of Designing as Problem-Solving
June 19, 2019
"Joe Mesman and Peria will talk about how AI can take design sprints beyond their traditional limits."
Jon FukudaTheme 3 Intro
September 25, 2024
"The veterinary pathway is well established as a way to safely get clinical validation before human healthcare."
Eric ShumakeAn AMA on UX's Role in Healthcare
April 22, 2026
"You have to find your champion as high up in the company as possible to push for research and equitable pay."
Mike DavidsonFireside Chat
March 11, 2022
"When someone gives you their phone number or interview with you, you become a steward of their data."
Amy Brana StuartRest in Peace Fly-in-fly-out Design
June 9, 2022
"In science, it’s better to miss a phenomenon than to misidentify one that doesn’t really exist."
Victor Lombardi Ted Booth HK Dunston Andrew OtwellBridging Design and Climate Science
February 14, 2024
"Automate the hell out of structured data, but stay involved in messy, rich data."
Maria RosalaAI-Assisted Qualitative Analysis: What to Automate and What to Own
June 5, 2026
"There’s no good answer yet for how to resolve the inequities created by differential access to digital technology."
Leah BuleyClosing Plenary: The Crisis of Digital
March 31, 2020
"How can I know what I think until I see what I say? EM Forster."
JD Buckley Margot Dear Jim Kalbach Janaki KumarCOMMUNICATE: Discussion
June 14, 2018
