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.
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 about the relationships between people, components, and contexts, not just UI artifacts.
-
•
Many teams adopt design systems by default without clearly defining the problems they intend to solve.
-
•
Measuring design system success by consistency or efficiency is challenging without baseline metrics.
-
•
People and interpersonal communication are the hardest and most critical part of design system success.
-
•
Centralized, federated, and hybrid design system team structures each have unique challenges around responsibility and resourcing.
-
•
A design system requires continuous community engagement and feedback loops to stay relevant and valuable.
-
•
Governance through documented decisions (like architecture decision records) prevents repeated mistakes and confusion over time.
-
•
Design debt is inevitable and must be intentionally managed and communicated within the context of the design system.
-
•
Design systems enable creativity by offloading repetitive work, freeing teams to solve higher-level problems.
-
•
Successful design systems depend on humility and a focus on empowering users rather than the ego of creators.
Notable Quotes
"Design systems aren’t just artifacts, it’s about the relationships between people and those artifacts."
"Everyone seems to have a design system, but it’s rarely clear why or what problem they’re really solving."
"You can’t just drop a design system in and expect everything to magically get better."
"The hardest part of design systems is always the people bit, the interpersonal stuff."
"A centralized design system team further removed from product teams creates difficult resourcing and responsibility questions."
"Communities around design systems need ongoing engagement; it’s not a one-off project."
"Your job with a design system is not to make the best components, it’s to help your peers do great work."
"Design debt is not a dirty word, but it must be recognized, managed, and paid off."
"Governance means capturing decisions transparently so you don’t repeat the same mistakes."
"If the people using your design system aren’t enjoying it, the system has already failed."
Dig deeper—ask the Rosenbot:
More Videos
"We changed the language to revolve around assumptions, hypotheses, experiments, and making sense of data."
Monty HammontreeThe Future of UX Research (Videoconference)
December 3, 2020
"Hope is not passive; it is proactive and must be facilitated carefully, especially where optimism is scarce."
Liz EbengoThe Burden on Children: The Cost of Insufficient Post-Conflict Services and Pathways Forward
December 4, 2024
"Staying in low fidelity throughout early concept development lets you focus strictly on the problem and solution space."
Billy CarlsonTips to Utilize Wireframes to Tell an Effective Product Story
June 6, 2023
"The better question is who are we excluding when we talk about inclusive design."
Saara Kamppari-MillerInclusive Design is DesignOps
September 29, 2021
"Why don’t we do what we do for our careers? Designers should design their own career as a project."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"People assumed Facebook was always listening to their conversations because we didn’t clearly explain how and why the feature worked."
Jonathon ColmanHow to Maximize the Impact of Content Design
January 8, 2024
"We need processes that accommodate design instead of designers becoming the hamster in the agile wheel."
Maria SkaadenContinuous Design: One eye on the horizon and the other on the next wave
November 8, 2018
"I learned from Molly that the lunatic asylum is now called the Austin State Hospital, and I've encoded that in a Python script."
Bryce Benton[Demo] AI-powered UX enhancement: Aligning GitHub documentation with USWDS at Austin Public Library
June 4, 2024
"You have to apply multiple perspectives to the data so you don’t oversimplify or misinterpret the patterns."
Marc FonteijnFirst Insights from the 2025 Service Design Salary(+) Report
December 4, 2024
