Summary
Design systems have become an integral part of product-driven organisations, promising consistency, efficiency, and improved collaboration. 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
-
•
Four forces—clear objective, executive sponsorship, peer buy-in, and a dedicated team—must be balanced for design system success.
-
•
Design systems are living products requiring continuous evolution through collaboration and co-creation.
-
•
Silos lead to fragmented experiences and tech/design debt, making design systems crucial for shared language and alignment.
-
•
Stakeholder mapping enables better understanding of hidden agendas and bridges communication gaps.
-
•
Adopting a contribution model requires cultural shifts and can be encouraged by incentives like OKRs and guided handholding.
-
•
Regular rituals such as design critiques, roadmap meetings, and office hours help maintain engagement and alignment.
-
•
Technical challenges like limited engineering resources can be mitigated by rotation programs or ‘boot camps’.
-
•
Measuring adoption alone is insufficient; true impact links to design influence on product strategy and user outcomes.
-
•
Frequent advocacy and education via newsletters, workshops, and hackathons increase adoption and user satisfaction.
-
•
Strong chemistry between designers and engineers and cultural values like shared ownership underpin long-term sustainability.
Notable Quotes
"Design systems are not just UI components but people and culture working together."
"Customers rarely ask us to fix inconsistencies directly; we must watch activation rates and confusion instead."
"Having a design system is not the end goal; it enables radical cost cuts, reduces tech debt, and improves workflows."
"You need sponsorship from senior leadership but also buy-in from all corners of the company to succeed."
"Designers are rebels; to get their buy-in, involve them and treat them as precious collaborators."
"Our design system team became less builders and more librarians and facilitators over time."
"We ran a design system bootcamp to rotate engineers and prevent bottlenecks and burnout."
"It’s a constant balancing act wearing multiple hats like diplomat, facilitator, architect, and community manager."
"Great design doesn’t happen in isolation; it’s subject to power dynamics within organizations."
"The work of the design system is constant change management, raising awareness, and fostering common language."
Or choose a question:
More Videos
"You’re born on third base but think you hit a triple — that’s the enterprise software delusion."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"The Red Queen effect means if others adapt, you must adapt or lose."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"There’s a gap between intentions and impact; humility is needed to close it."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"By observing, appealing to interests, and promoting accountability, we can build empathy and respect to combat toxicity."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Having conversations with stakeholders before sharing AI-generated recommendations validates their legitimacy and relevance."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Nobody wants to buy or use a sloppy product, especially when enterprise users engage daily for hours."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"There is no design team responsible for the overarching experience across the entire company."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"Once cash prizes were gone, people stopped feeling ownership of the design system."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Product managers feel design is a black box; they want visibility, transparency, and accountability on timelines."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
