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
"Service blueprint is a knowledge graph – it gives AI intent and helps AI be more useful."
Ben Reason Aline Horta Majid Iqbal Fabiano LeoniMaking the system visible: The fastest path to better decisions
November 20, 2025
"Users with cognitive challenges benefit enormously from features like reduced motion and focus mode on mobile."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
March 10, 2022
"We believe the responsibility for the voice of the customer should be shared by everyone on the team."
Anna Nguyen Emily BroganWhy Our Voice of the Customer is Better Than Yours
March 10, 2022
"Eventually, I expect AI to help create designs by combining patterns from meta design systems and research, making design more about crafting experiences."
Abby Covert Tomer SharonPanel: Collaboration Tools
November 6, 2017
"Automated testing tools saved us several days of manual testing and helped prioritize work more effectively."
Phil HeskethDesigning Accessible Research Workflows
September 29, 2021
"You never get all your usability testers to respond, you always need to recruit more than you think."
Irina Tikhonova Kari DietrichSmall Wins, Big Impact: Leveraging and Elevating User Engagement
December 9, 2021
"Education and awareness had to be core parts of what we were doing in this shift."
Tim FrickThe journey of building a sustainable design practice
April 23, 2025
"We created a simple WordPress site so all corners of the business could contribute and share insights, breaking down silos."
Catherine DubutBridging Physical and Digital Spaces: Approaches to Retail Service Design
March 18, 2021
"Traditional job requirements like college degrees and supervisory experience can bar otherwise skilled candidates in the public sector."
Justin Entzminger Terrance Smith Tracy M. Colunga Mai-Ling GarciaRisk and Reward: How to Diversify the Field of Civic Innovators and Designers
November 17, 2022
Latest Books All books
Dig deeper with the Rosenbot
How did the Echo Look miss motivational opportunities despite advanced AI features?
Why did early AI integrations like Google Translate and YouTube recommendations leave the interface unchanged?
How might deceptive patterns explain the privacy paradox where users say they value privacy but behave otherwise?