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
"Your job is not producing assets; it’s usually some other kind of process. If it’s only about assets, find a better job."
Tom Armitage Carla Diana Kanene Ayo HolderDay 2 Panel: Looking ahead: Designing with AI in 2026
June 11, 2025
"Firsthand engagement with UX research shows that it doesn’t slow you down — it can actually help things move faster."
Hana NagelTurning Research Ripples into Waves
November 8, 2018
"Building trust is a slow, brick-by-brick process, especially when you’re entering new environments."
Melissa Eggleston Maya Israni Florence Kasule Owen Seely Andrea SchneiderPractical People Skills for Building Trust on Teams and with Partners
December 9, 2021
"If you want your question asked, please put it in the Slack channel, because I cannot keep up with the rapid things happening live."
Bria Alexander Louis RosenfeldOpening Remarks Day 1
March 25, 2024
"If you’d rather exclude a group of people from using your product than do accessibility, then think about the impact you’re making."
Alexis LucioScaling Accessibility Through Design Systems
June 9, 2022
"Without automation, none of these tools are talking to each other, and operational overhead for your Ops and DPM teams is actually absurd."
Candace MyersStandardizing Design at Scale
September 9, 2022
"Every app built into my phone is perfect when it comes to accessibility – Apple and Android set a strong example."
Sam ProulxMobile Accessibility and You
June 9, 2022
"Don't think constraints are real. Executives see them as excuses for not delivering."
Jess GrecoClaiming your power: Practical tools for amplifying your unique voice
March 13, 2025
"Marketers don’t try very interesting things when their confidence in data is low, which can create a downward spiraling reinforcing loop."
Sarah FlamionComplex Problem? Add Clarity by Combining Research and Systems Thinking
March 31, 2020
