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
"Making your chief legal officer your best friend as a designer makes a lot of sense."
Amy MarquezINVEST: Discussion
June 15, 2018
"Capturing quotes directly—even assumed ones—makes empathy mapping more specific."
Aditi Ruiz Christian Crumlish Farid SabitovA PM State of Mind: Empathy Mapping Your Product Manager, Pt. 1
December 6, 2022
"Nobody’s going to use digital calendars because they’re just more work and no benefit."
Sam LadnerData Exhaust and Personal Data: Learning from Consumer Products to Enhance Enterprise UX
June 8, 2016
"Not growing the team was disheartening but led me to create training for partners to start taking a user-centered approach themselves."
Abbey Smalley Sylas SouzaScaling UX Past the Size of Your Team
January 8, 2024
"You bring energy that blows me away. I’m so excited by your excitement."
Bria Alexander Louis RosenfeldWelcome
September 8, 2022
"People get stuck during the sessions when asked to describe their brand voice in just one or two words."
Trisha Causley[Demo] Complexity in disguise: Crafting experiences for generative AI features
June 5, 2024
"Security means protecting business, productivity, safety."
Heidi TrostTo Protect People, You Have to Protect Information: A Human-Centered Design Approach to Cybersecurity
January 23, 2025
"Rapid research programs enable designers to submit research questions and feel empowered to participate actively in the research process."
Feleesha SterlingBuilding a Rapid Research Program
May 18, 2023
"Am I the right person to conduct this type of research for this culture? That’s a question most companies don’t have researchers asking."
Sharon Banh Dave Hora Marieke McCloskey Alicia ZhongReimagining research: What does the field need to grow? [Advancing Research Community Workshop Series]
October 16, 2024
