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
"After the payroll app was on the roadmap, folks started asking where's the revenue, and then they wanted to change the direction without experimentation."
Steve Sanderson Alissa Briggs Jeff Gothelf Bill ScottDiscussion
May 14, 2015
"Academic Purists believe one size fits all, ignoring context and stifling innovation."
Jason Mesut Martina Hodges-Schell Jose CoronadoUnmasking Design Leadership: Navigating leadership without neglecting ourselves
October 30, 2025
"The interface becomes a radically adaptive surface—an intelligent canvas that reacts to your behavior and context."
Josh Clark Veronika KindredSentient Design, AI, and the Radically Adaptive Experience (1st of 3 seminars)
January 15, 2025
"Meeting stakeholders where they are means using language and concepts they understand, not just tech jargon."
Magdalena ZadaraZero Hour: How to Get Far Quickly When Starting Your Digital Service Unit Late
November 16, 2022
"I kind of think of it one as like fields of influence — staff influences the team or pillar, principal influences organization-wide."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"Our sponsor sessions are not sales pitches; they are serious, high content learning opportunities for everyone."
Bria AlexanderOpening Remarks
November 17, 2022
"All designers have responsibility to communicate upstream and downstream, sharing their work context and contributing to the DP&M system."
Ellie Krysl Jon FukudaPlanned Right. Managed Right. Designed Right.
June 6, 2023
"It’s not always a charismatic repository that people flock to, but tools that seek you out where you work are more effective."
Ned Dwyer Emily Stewart James WallisThe Intersection of Design and ResearchOps
September 24, 2024
"We want to hear what resonates most in your hearts and minds."
Sarah BrooksTheme 3 Intro
December 10, 2021
