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
"I have to triangulate socially because Yorkshire folks are quite reserved; they won't openly admit issues."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Sometimes the director is the most senior design person in the org and ends up playing the executive role without the title or support."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"If you haven’t designed who your teams are and who your players are, expecting people to comply with standards won’t work."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"The solutions are out there; we just need the will to implement them."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"If you get a perfect score on your OKRs, it means you didn’t set your sights high enough."
Brenna FallonLearning Over Outcomes
October 24, 2019
"It’s human infrastructure—community organizing, unions, activists—that saves the day when other infrastructures break down."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Delivering research in small, lean increments allowed us to iterate fast and reduce bias."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Successful operations must have a well-laid-out and transparent process and documentation, but that process must become invisible in its application."
Designing Systems at Scale
November 7, 2018
"The conversion design process creates collective knowledge, which gets reinfused to strengthen future experiments."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
