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
"Critique is an opportunity to build a culture of trust upon grounded reality while developing your craft. - Chris"
Erika Kincaid Brenna Heaps Jessica TsukimuraConnecting the Dots: How to Foster Collaboration and Build a Strong Design Review Culture
June 8, 2022
"Saying no with purpose and rationale helped us scale from nine people to over 150 without burning out the team."
Catherine CourageThe Enterprise UX Journey: Lessons From the Voyage & The Opportunity Ahead
May 13, 2015
"Designers create value by making artifacts and experiences before fully understanding the space."
Shahrzad SamadzadehWhat Is My Value? Two Takes and Some Mistakes
January 8, 2024
"Our industry is new enough that we get to make design ops whatever we want it to be – that’s an incredible opportunity."
Bria Alexander Meredith Black Tim GilliganState of DesignOps Panel
October 1, 2021
"The biggest challenge I see is scaling without losing our humanity."
Bud Caddell Kristin Skinner Alana WashingtonDesignOps Community Sensing Session
May 13, 2021
"Similar inputs will produce similar high dimensional numbers."
Ian JohnsonLatent Scope: Finding structure in unstructured data
June 11, 2025
"My job was to insulate my team from the pressures and not let anyone else do UX work. That was wrong."
Rob Mitzel Sébastien MaloThe Tale of Two Companies: Building a Successful UX Practice in a Century-Old Enterprise
January 8, 2024
"Doing accessibility from the start saves cost by avoiding expensive retrofits and rework later on."
Gabriela BarnevaOperationalizing Inclusive Design in Design Ops
September 11, 2025
"The future of medicine will be written in algorithms if we let it."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
