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
"Using skittles to map skills made it less personal but more fun and engaging for designers."
Shaping design, designers and teams
November 8, 2018
"The purpose of a design operating model is to place the customer at the centre of everything the whole organisation does."
Sabrina Mach Nina WainwrightHow to Design Your Design Operating Model
September 29, 2021
"We need to stop treating digital and physical services as separate—they’re one holistic experience."
Samuel ProulxInvisible barriers: Why accessible service design can’t be an afterthought
December 3, 2024
"Design, product, engineering, legal, and leadership all need to be involved; it should never be just one group’s responsibility."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility (Videoconference)
May 26, 2022
"Product design and development can often mirror what happens in a chef’s kitchen: lots of coordination and spinning plates behind the scenes."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"Don't be cool, be good—work hard at managing your teams because they need you to nail it."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"We had to partner closely with information security to ensure every piece of data in research files was tracked and compliant."
Operationalizing DesignOps
November 7, 2018
"Executives see research value when they’ve lost money on bad bets and want to mitigate risk for future decisions."
Leah Buley Joe NatoliAsk Me Anything with Leah Buley and Joe Natoli, co-authors of The User Experience Team of One (2nd edition)
October 8, 2024
"Tell tight, brief stories of insights focused on impact, not on how you conducted your research."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020