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 shifted from building each application type individually to creating a platform that planners can use to build their own."
Laura Smith Tom GaylerEmbedding Service Design and Agile Practice within UK Planning Teams to Create Services that Last
December 3, 2024
"What are three recent examples of how you nurture creativity or resilience for yourself or others?"
Alana WashingtonTheme 1: Introduction and Provocation
January 8, 2024
"Managing up assumes research is below something, but I see advising as partnerships and equals."
Christian MadsbjergInfluencing Strategy
March 31, 2020
"Two designers in Belgium seized a COVID moment to advance inclusion in digital public services where equality, not equity, is the policy."
Charlotte LeeTheme 1 Intro
December 8, 2021
"A centralized model for design systems can be problematic because it distances the team from end users."
Dan DonaldDesign Systems as a Vehicle for Systemic Change
June 1, 2023
"The most important thing you can do as a colleague, boss, or friend is ask what helps you work better."
Jessica NorrisADHD: A DesignOps Superpower
September 9, 2022
"My superpower is to connect the dots between people, places, ideas, and opportunities."
Dante GuintuHow to Crush the Talent Crunch
September 8, 2022
"Model companies are students in a classroom wanting good points—they’re happy to run external expert evals to improve."
Peter Van DijckHands-on AI #2: Understanding evals: LLM as a Judge
October 15, 2025
"Code is definitely considered the source of truth; we're working hard to make Figma an extension of that."
Charles Lee Jennie YipBuilding a New Home for the Atlassian Design System
October 22, 2020
