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
"Partner with data scientists to pick and adjust statistical tests because quantitative ethnography requires new assumptions."
Vitorio MilianoDon’t call it AI: Turn words into numbers with quantitative ethnography
March 11, 2026
"I had to learn to speak contractor — shorter, simpler, in-viewport text without scrolling."
Sara ConklinExit Interview: 20 Years of Tech, One Very Big Bet, and a Lot of Heat Pumps
April 10, 2026
"Involving people with disabilities from the start reveals impact and usability issues that automated testing simply cannot catch."
Sam ProulxOnline Shopping: Designing an Accessible Experience
October 3, 2023
"We have at least 10 minutes of breaks between each session so you can take in everything."
Bria AlexanderOpening Remarks
January 8, 2024
"Google Translate completely reinvented itself by replacing many translation systems with a single neural network capable of zero-shot translations."
Luke WroblewskiDesigning AI Applications
March 5, 2026
"Design for one extent to many is Microsoft’s inclusive design motto that guides effective accessibility."
Amber KnablEmpowering innovation: The critical role of inclusive product development in the AI era
June 4, 2024
"AI is fluent without standing; it never says this will not work, it never pushes back on the company."
Angelos ArnisOur Fragmented Identity
June 12, 2026
"You need someone human deciding what information is good enough and tagged well for AI to surface it."
Kate Towsey Jake BurghardtResearchOps AMA with Kate Towsey & Jake Burghardt
October 16, 2025
"We’ve been over-indexing on the individual and not considering belonging and connectivity enough."
Daniel GloydDesigning Warmth
February 26, 2025
