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
"Users creatively circumvent broken enterprise systems, which traditional metrics often miss."
Alexandra SchmidtEnterprise UX Playbook
December 1, 2022
"We set a goal to fill 25% of our early career roles with underrepresented demographics and landed 37%."
Jen Crim Jess Quittner Saritha Kattekola Alex Karr Gurbani PahwaCulture, DIBS & Recruiting
June 11, 2021
"Leadership doesn’t necessarily mean managing people; it means scaling impact through teaching, training, and setting examples."
Christian CrumlishAMA with Christian Crumlish, author of Product Management for UX People
March 24, 2022
"We turned design thinking on ourselves to tackle our own hiring challenges—applying tools meant for customers to our own processes."
Libby MaurerTreating Diversity & Inclusion in Hiring as a Design Problem
December 5, 2019
"When we engage people in the planning process, they take ownership of their city."
Ali Jeffery Sheri ChudowHow DesignOps Helped Enable Wall Street to Work Remotely
October 22, 2020
"Patricia Moore’s aging research revealed how product design often excludes elderly users by living their constraints."
Daniel GloydDesigning From the Inside Out: How Method Acting Can Inspire Design Research
February 12, 2026
"Technology can revolutionize how we think about education."
Kristin SkinnerFive Years of DesignOps
September 29, 2021
"What we measure is super important because it determines what people pay attention to. Without governance, priorities and ratings become outdated."
Johanna KollmannInsights-Driven Product Strategy: Get your Research to Count
December 6, 2022
"Human behavior is anything but linear, rational, or predictable."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
Latest Books All books
Dig deeper with the Rosenbot
Where can UX researchers find reliable, up-to-date information and recommendations on research tool options?
What are the benefits of linking AI-powered research repositories with tools like Slack for organizational adoption?
How do research operations teams manage the tension between consolidating tools and needing specialized capabilities?