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
"We had to convince our director and executives by showing how the repository added real value for the product team."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"There are over 7 billion futures of right now."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"The team that comes up with the winning idea leaves the studio with equity and carries the idea forward."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"One superpower of ops humans is making problems and gaps visible to build awareness and drive change."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"There’s a lot of pressure on ops people and managers to make everything perfect all the time for staff."
Tess DixonC'mon Get Happy
September 29, 2021
"We ran ambient workshops so folks could contribute on their own time and remove the friction of synchronous meetings."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"Your career is a design project. It’s the only one you own, so own it like you would a product."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"If you make rules, put numbers in them, and say them confidently, sometimes people actually do them."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"Slowing down is hard in a capitalist economy that values speed, but patience and self-care are necessary."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
