Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Design Systems as a Vehicle for Systemic Change
Summary
When asked, I’m sure many people would point to something visual about design systems. In reality, most of the work and so the effort that can make these projects succeed or fail is unseen – the people bit. For many organisations, design systems present a challenge in terms of structure, delivery, and how to define value. Designing these unseen structures and pipelines can enable the great work everyone always wanted to do – while being communicative and collaborative in ways we’ve not done before.
Key Insights
-
•
Design systems are more about relationships and culture than just UI components.
-
•
A successful design system requires clear problem definition and measurable impact.
-
•
People challenges, like communication and collaboration, often impede design system success more than technical issues.
-
•
Centralized, federated, and hybrid team models each have unique trade-offs in managing design systems.
-
•
Design systems should empower users by reducing repetitive work, enabling focus on higher-level problems.
-
•
Continuous feedback loops and community engagement are critical for evolving and maintaining design systems.
-
•
Governance, including documented decision records, helps preserve institutional knowledge and guide future changes.
-
•
Design system work shifts organizational culture by bridging disparate teams and breaking down silos.
-
•
Managing design debt is an intentional and ongoing part of design system maintenance and growth.
-
•
Humility and a servant-leadership mindset are essential for those stewarding the design system.
Notable Quotes
"It’s how you think about the relationships between people and these artifacts that makes a design system."
"Everyone seems to have a design system, but many don’t understand why they need one."
"Often you can tell people just don’t talk, and design systems need that interpersonal stuff to work."
"A centralized model for design systems can be problematic because it distances the team from end users."
"Design systems are not a straight jacket, they free you from repetitive work to focus on bigger problems."
"The value of a design system looks different depending on if you’re a developer, designer, or stakeholder."
"If you don’t continually check whether people are benefiting, the system’s reputation can quickly suffer."
"Design system decision records prevent knowledge being stuck in one person’s head."
"A design system is never a done thing, it’s a continuous evolution of best practices."
"Our job is to help others do great work, not to create perfect components for our own ego."
Or choose a question:
More Videos
"You might know us from the 70 or so UX and product design books we've published over the past two decades."
Louis RosenfeldAbout the Rosenverse
March 15, 2026
"Whoever has been and might continue to be the most negatively impacted absolutely needs to be centered and have their voices at the table."
Ilana LipsettAnticipating Risk, Regulating Tech: A Playbook for Ethical Technology Governance
December 10, 2021
"Data is power; find your eigen metric, the one or two things that prove your hypothesis."
Aletheia DelivreNew Shapes and Emerging Identities for Design Ops
September 11, 2025
"SmartSheet magic is really just frosty if statement formulas connecting 75 columns of metadata."
Kristin Sundermeyer Tygre MorehartDesign Ops Metrics
September 30, 2021
"Slack is the way you ask questions to the speakers, and it’s where most of the community interaction happens."
Bria AlexanderOpening Remarks
March 28, 2023
"Standardization lives deep in my heart partially because of the teams that I’ve worked on and also because I’ve just had so many domains under the umbrellas of my teams over time."
Candace MyersStandardizing Design at Scale
September 9, 2022
"We created onboarding camps that helped new hires become impactful faster and packaged that across teams."
Courtney KaplanTaking it to the next level: Career paths in DesignOps
November 8, 2018
"Before AI, research teams spent over a quarter of their time consulting about research questions, often repeating themselves."
Mike OrenImproving Democratized Research with CustomGPTs and Gems
February 25, 2026
"The Investiture Framework is a doctrine enforcing a vector.md file that encodes personas, jobs to be done, pain points, and more."
Erika FlowersThe Handoff is Dead: Design-Led Engineering with AI Agents
March 4, 2026
