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
"Unless your products yield exceptional emotional value, they’re not going to succeed."
Kelly GotoEmotion Economy: Ethnography as Corporate Strategy
May 13, 2015
"We can no longer think of users as flat personas; we have to enrich those concepts with intersectional identities."
Lija HoganContexts of Use: A Framework for Connection
December 9, 2021
"Caring personally isn't about memorizing birthdays or throwing big team offsites; it’s about real conversations and learning what’s important to people."
Etienne FangThe Power of Care: From Human-Centered Research to Humanity-Centered Leadership
March 10, 2021
"This client project is very deliberate and explicit in focusing on culture and values."
Stephen PollardClosing Keynote: Getting giants to dance - what can we learn from designing large and complex public infrastructure?
November 7, 2017
"We were doing all the things until we got the advice to specialize; that moment changed everything."
Theresa NeilDesigning for Wellness: Specializing in Healthcare
May 22, 2024
"Would you feel confident leaving your project success to the flip of a coin based on the fact that almost half of all change fails?"
Amy EvansHow to Create Change
September 25, 2024
"If you need to cross a dangerous river, you don’t paddle straight into it; you use the opposing force of the river to move forward."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"Where in your design process is your biggest opportunity for AI adoption?"
Llewyn PaineDay 1 Using AI in UX with Impact
June 10, 2025
"We unapologetically move forward when high-level stakeholders miss deadlines, but also collect feedback via surveys."
Briana Thomas Christina RodriguezWhen Design Ops Comes in H.O.T. : A Tale of a Transformed Design Org
September 30, 2021
