Summary
The speaker, who leads a small UX firm, draws on a decade of consulting with major enterprises like IBM, Google, Salesforce, Marriott, and Cisco to reveal key learnings about design systems. Starting with a story about IBM’s ambitious growth of hundreds of designers, he highlights the importance of thinking beyond a component library to a system spanning multiple related products. Using Google’s Material Design as a benchmark, he discusses how visual consistency extends beyond color and typography to interaction, motion, voice, and editorial style. He underscores the challenge of achieving true cohesiveness over time, not just right after launch. Exercises like component cutouts and prioritization worksheets help teams identify necessary parts of their system. The speaker shares practical strategies like stitching prototypes together across teams—as done at Marriott by Livia Lavatte—to demonstrate value to stakeholders. Andrew from Sun Microsystems exemplifies the risks of centralized but bottlenecked library ownership, while Salesforce’s Gina models a balanced centralized team with distributed contributors. Decision-making frameworks like Cap Walkins’ care-scale help balance autonomy and system consistency. The talk stresses the critical need for executive buy-in, for treating the system as a product, and for inclusive leadership representing UX, visual, interaction, and content strategy domains (called UV and civics). He advises starting with flagship products but also knowing where not to play—avoiding contentious areas like homepages—and focusing on injecting design systems into reusable shells like navigation. Finally, he calls on design system stewards to embrace identities as connectors, evangelists, and product managers, sustaining a living design system that positively impacts customer experiences across diverse product ecosystems.
Key Insights
-
•
Design systems should be treated as living products, not static artifacts that end at launch.
-
•
Successful design systems require executive endorsement and organizational alignment from the top.
-
•
Visual style alone is insufficient; motion, voice, editorial style, and interaction design are also key components.
-
•
Centralized design system teams need to federate influence and collaborate with product teams for relevance and adoption.
-
•
Prioritizing flagship products (usually 3-5) helps focus design system efforts effectively amidst many products.
-
•
Injecting design system components into shared navigation shells and footers can accelerate adoption enterprise-wide.
-
•
Exercises like component cutouts and prioritization worksheets surface organizational language and focus areas.
-
•
Decision-making tools that rate how much stakeholders care about elements help balance system coherence and product autonomy.
-
•
Content strategy leaders must be integrated into design system leadership to address voice and editorial aspects.
-
•
Prototypes linking multiple team outputs—as done by Livia Lavatte at Marriott—enable storytelling that secures stakeholder buy-in.
Notable Quotes
"I don’t want a component library for the account home. I want a system for all of that."
"When you look at Google you ask yourself is all this cohesive. Visually, they’ve done a damn good job."
"That’s like a solitary model. One talented person builds the library, and if he’s busy, you get nothing new. That doesn’t scale."
"Design systems aren’t done when the style guide launches. You’re done when it starts to positively impact customer experience."
"Treat your design system like a product that others in your organization are your customers."
"You need voices from UX, visual, interaction, and content strategy teams on your leadership to inject their influence."
"Executive support makes your design system’s mission easier to achieve and sustain."
"Not every area is worth pursuing; the homepage often has conflicting goals and unstable patterns."
"How do you facilitate decisions so people reveal how much they care about design choices? Use a simple zero-to-ten scale."
"Being a connector and evangelist is part of the modern design system steward’s role."
Or choose a question:
More Videos
"We are witnessing the most rapid loss of biodiversity in human history."
Alex Hurworth Bonnie John Fahd Arshad Antoine MarinDesigning a Contact Tracing App for Universal Access
October 23, 2020
"Building connections early in their career could create even more opportunities further along their career path."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"If you come with a big idea, they’ll try to dial you back to the smallest iota you can test first."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Strategy should be continuous, circular, and evolve with every action the organization takes."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020
"If you focus on desktop accessibility, you’re leaving out some of your most important users who may have mobile-only access."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
November 17, 2022
"It’s important to socialize the research program internally so teams get excited and take initiative."
Feleesha SterlingBuilding a Rapid Research Program (Videoconference)
May 18, 2023
"Culturally resonant experiences can influence society in ways governments only dream of, with velocity and speed."
Neil BarrieWidening the Aperture: The Case for Taking a Broader Lens to the Dialogue between Products and Culture
March 25, 2024
"Knowledge management isn’t just about preserving work, it’s about retaining motivated, growing people."
John DevanneyThe Design Management Office
November 6, 2017
"We decided to jump off the wall — it was scary but the opportunity was too big to pass up."
Katy MogalBut Do Your Insights Scale?
March 12, 2021