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
"Acknowledging that you can’t get other people to do things is truly the path to freedom."
Matt LeMayYou Don’t “Get” Anyone to Do Anything
December 6, 2022
"We could create a sustainable culture of design and use it as our leading edge weapon of transformation."
Phil GilbertA Consistent Culture of Design
May 14, 2015
"If you don’t do this work ethically and thoughtfully, nobody else may."
Louis RosenfeldWelcome / Housekeeping
June 6, 2023
"Slowing down is not inefficiency; it is a commitment to dignity and trust."
Rachael Dietkus, LCSWThe power to heal and harm
March 13, 2025
"You can't just expect insights to solve themselves if people don't know about them."
Jake BurghardtFinding More Inroads into Research Impact
February 20, 2026
"Research operations is the people, mechanisms and strategies that set user research in motion."
Fatimah RichmondThe Future of ReOps as a Strategic Function: A Roadmap for Getting There
March 25, 2024
"Language is imprecise; banning crutch words like MVP forces people to clarify real meaning."
Joshua GravesWe Need To Talk: Managing Ludicrous Requests at Work (Part 3 of 3)
May 12, 2025
"Establishing a shared vision with your boss or team helps align goals, even amid conflict."
Joshua GravesWe Need To Talk: Navigating Conversations with Your Boss (Part 1 of 3)
April 14, 2025
"If we could do everything that was important, we would just do it."
Harry MaxPriority Zero: Some Things are More Equal than Others
June 9, 2016
Latest Books All books
Dig deeper with the Rosenbot
What strategies help reframe the difficult business development work when going independent?
What is continuity architecture and why is it important across AI-driven journeys?
How can organizations prevent design system knowledge from being an undocumented API surface reliant on specific individuals?