Summary
Designers need to work with developers. One of the core ways they have learned to do this is by taking something from the designer’s playbook—pattern languages—and mapping that against one of the chief learnings from contemporary engineering: componentization. By using design systems and associated object based documentation systems, design leaders have helped to reshape the designer/developer universe and improve operations within the software development lifecycle. Facilitated by Dave Malouf.
Key Insights
-
•
Design system governance works best when balancing clear ownership with open contribution and advocacy, rather than rigid enforcement of rules, as demonstrated by Shopify’s Polaris.
-
•
Treating a design system as a product with a dedicated team, agile planning, and rigorous testing ensures scalability and reliability, as seen in GE’s fourth-generation system.
-
•
Usability directly impacts customer value; effective design systems enable designers to focus on solving meaningful problems rather than reinventing UI elements.
-
•
Co-creation with cross-functional teams fosters better alignment and adoption of design systems, minimizing the disconnect between abstract design and real product needs.
-
•
Accessibility and responsiveness are core usability targets that must be integrated into design system components, supported by close designer-developer collaboration.
-
•
Design constraints imposed by design systems can boost creativity by freeing designers from trivial stylistic decisions, allowing focus on higher-level user experience problems.
-
•
Design systems need flexible patterns to avoid frustrating designers and ensure the system supports diverse applications, avoiding overly narrow, product-specific constraints.
-
•
Operationalizing design systems requires tooling that synchronizes design assets (e.g., code libraries, sketch symbols) and automation that facilitates contributions and usage feedback.
-
•
Automated enforcement tools like Shopify’s 'worry bot' can improve content consistency by providing real-time feedback, supplementing but not replacing documentation.
-
•
Stress-testing components in real product environments exposes limitations early, guiding improvements and preventing broken experiences when deployed at scale.
Notable Quotes
"We hadn’t really thought about governance up front at all, which is not the ideal way to do something like that."
"A design system that isn’t dynamic and doesn’t allow for contribution across the company is probably going to become stale very quickly."
"Our mantra is tools, not rules. Make it easier for people to do their jobs and they’ll use the design system."
"We started talking about creating alignment through co-creation, and we’ve found that to be the single best way to get people to really buy into the ideas."
"Usability is like the bottom of Maslow’s hierarchy of needs of a product experience."
"Design system’s job is to enable designers and developers to rapidly iterate through ideas to solve real user problems."
"Constraints are a key element to creativity. Without constraints design can turn into something ungrounded."
"For every component, we start with its purpose to emergent need, grounding us in the user experience."
"We have to make it super easy for developers, because if developers find it easier, then designers will automatically like using it."
"Break your design system components; stress test them to see where they break before they go out into the wild."
Or choose a question:
More Videos
"Doctors hate using EHRs because it turns them into clerks, interacting more with machines than patients."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"Most strategy today is guesswork based on what others are doing, not based on situational awareness."
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 Jeff’s concerns and asking questions, I was able to show empathy and focus on the problem rather than get defensive."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"We mitigated data privacy risks by subscribing to the corporate plan for ChatGPT, which offers enhanced security."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Craft cultivates customer satisfaction, loyalty, and even forgiveness when functional issues arise."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Trust is often underestimated but is critical when designers face public critique and feedback."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"You won’t know what success looks like until you put something out there and see how it works in practice."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Most of us in design are very process-oriented, but traditional devops tools are task and issue-centric, making collaboration hard."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022