The Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
Summary
Amidst the success stories, there are risks, challenges, and failures bound to accompany their implementation and adoption. Why do some design organisations thrive despite it, and others fail miserably?
Because of the pandemic of productisation, strategic product decisions are driven by product managers who want to build fast and break things, and user advocates are cut off from discovery, becoming mere feature producers who pass on unvalidated requirements to the design system. Designers working on the product side claim that the design system hinders their creative process and stifles innovation, when it should enable it, while the design system team prides itself on setting standards of excellence that has become a purpose on its' own. The pace at which the design system can deliver upon product requirements often leads to it being perceived as a bottleneck by both designers and product managers, and testing their outputs with end users is a no man’s land. So what is the true role of design systems? How can we use them to drive change?
Embarking on a design systems journey is a rollercoaster ride for the entire organisation, not to mention the team that runs it. The success of a design system will depend on many factors beyond the UI inventory or tech stack — they will manifest themselves differently in each organisation, by amplifying communication and collaboration patterns for better or worse.
As an experienced design systems leader, I will share practical insights from my own journey, wins and mistakes, on how to manage design systems that add tangible value to the organisation and initiate positive and transformative changes in our approach to collaboration, design, development and UX. I will share how we can use design systems to drive meaningful conversations, build bridges and create new paradigms.
Key Insights
-
•
People and culture are the most critical yet intangible parts of successful design systems.
-
•
Four driving forces—clear objectives, executive sponsorship, peer buy-in, dedicated teams—must be balanced for a design system’s success.
-
•
Design systems are not one-off projects but continuous operating systems combining product, service, and community management.
-
•
Creating a shared language across silos prevents fragmentation and builds consistent user experiences.
-
•
Involving stakeholders meaningfully requires understanding their goals, fears, and incentives through tools like stakeholder maps.
-
•
Demonstrating impact to product managers through efficiency case studies and metrics is crucial for adoption buy-in.
-
•
Regular rituals—design critiques, office hours, workshops—are essential for co-creating and prioritizing design system updates.
-
•
Encouraging contribution from users can be supported with formal agreements, OKRs, and hands-on support to ease onboarding.
-
•
Design systems support larger organizational goals by connecting design maturity, user research, and business outcomes.
-
•
Focusing on the design of value beyond monetization fosters innovation and empowers excellence across organizations.
Notable Quotes
"Customers are rarely asking us to fix inconsistencies. What we really need to do is examine indirect indicators like activation rates and how confusing our products are."
"Having a design system is not an end goal. It’s about what the design system enables us to do in our unique company context."
"Sponsorship must come from all corners of the company—not just top executives but peers and stakeholders too."
"Involving designers means treating them like precious individuals who value autonomy and collaboration, not imposing rules."
"A design system team often has to wear multiple hats—diplomat, facilitator, architect, community manager—to keep momentum."
"Design system is a continuous process—product development, service to educate, and creating adoption conditions."
"Without shared ownership and participation, design systems risk becoming isolated and irrelevant."
"Design system contributors need help along the way—think of it like training wheels before they ride independently."
"Great design does not happen in isolation; it’s subject to power dynamics inside companies and requires cross-functional collaboration."
"Focus on the design of value that moves people and drives change, not just financial gains."
Or choose a question:
More Videos
"Design ops has the opportunity to set a new default future, not follow the path set by the past."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"We use Alexa’s personification for good, fun, and delight, but we don’t advertise, especially because there may be kids listening."
Amy MarquezINVEST: Discussion
June 15, 2018
"Visualizing data in a way executives can interpret is key to shifting from I think to I know."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"Dedicated staffing gives designers deep vertical mastery but limits horizontal experience."
Alicia MootyDesign Staffing Models
September 30, 2021
"I believe there's really no such thing as a boring place at the state of mind."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"Simply asking stakeholders what success looks like for them in a project is a powerful way to start meaningful conversations."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"The legacy of folders and nested structures causes real problems in finding research and scaling repositories."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Please don’t chop off that engine until the new one is built because you are not the only one on this plane."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"My playlist changed drastically when my son was born, but data alone wouldn’t explain why."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
