Summary
Dawn Russell, a design leader at Intuit, explores the evolution and future of design systems, moving beyond traditional pattern or component libraries toward full-stack widgets—self-contained, reusable units that encapsulate UI and backend functionality. She contrasts design systems as mere documentation or front-end code with widgets that enable scalable, cohesive, and consistent product experiences across Intuit’s ecosystem. Dawn shares Intuit’s transition from siloed desktop products to cloud-based interconnected offerings, highlighting the One and Two at Identity project that created shared identity widgets used across 150 products, yielding a 10-13% increase in account recovery success and significant cost savings. She stresses the importance of cross-disciplinary collaboration, especially between designers and engineers, and the distinct skill set required for design system work, including ecosystem thinking and social influence. Practical tips include starting with a motivated team, iterating with feedback, and tying design systems to business and technical strategies. Dawn closes by urging designers to move their work into production code, defining code as their true medium to impact users.
Key Insights
-
•
Pattern libraries are documentation and not full design systems because they rely on individual interpretation without code enforcement.
-
•
Component libraries are UI code only and form part of design systems but lack backend integration.
-
•
Widgets represent the next evolution by packaging UI and backend services to deliver entire user tasks reusable across applications.
-
•
A single source of truth codified in code is vital for scalable and cohesive design systems in large enterprises.
-
•
Intuit’s One and Two at Identity project unified user experience and data sharing across siloed products via widgets.
-
•
Adopting standardized widgets like the account recovery widget improved success rates by up to 13% and reduced support costs drastically.
-
•
Widgets enable faster innovation by freeing product teams from reinventing common functionality and spreading best practices.
-
•
Effective widget design requires both broad ecosystem thinking and deep domain expertise.
-
•
Collaboration with engineers should start with user problems, not technology solutions, to unlock innovation and buy-in.
-
•
Not every design problem warrants a widget; reuse potential and context specificity must guide widget creation.
Notable Quotes
"In the enterprise, how quickly and easily your design system can scale is directly proportionate to the amount of impact it can have."
"A UI component contains styling code but no backend business logic."
"Widgets encapsulate a user task with associated UI and backend service functionality."
"Our users immediately assumed our products would work together naturally just by proposing a single identity."
"We improved the Account Recovery Success Rate by 10% after a year of iterating on the widget."
"QuickBooks saw a 13% increase in Account Recovery Success overnight by running an A/B test of our widget."
"If you don’t use our widgets, that extra engineering work is on you when we upgrade technology."
"Designing widgets is about both thinking broadly and deeply about the ecosystem and the domain."
"You want to start with the problem space and what the user needs are; don’t start with the how."
"As designers, our medium is code. Until your design is in production code, your design is just a figment of your imagination."
Or choose a question:
More Videos
"The hardest part about remote is making design reviews feel collaborative and team-based."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Playing politics in UX leadership is about maximizing relationships ethically to advance your agenda, not about being underhanded."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Human biases are the real problem behind algorithmic bias, not the algorithms themselves."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"The time for action is now, and it must be collaborative."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"Growth and learning is your long term change management plan."
Brenna FallonLearning Over Outcomes
October 24, 2019
"We are all experiencing a spatial collapse, a disruption of our mental models of how we navigate physical and virtual spaces."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"We used a Python algorithm with a correlation matrix to identify meaningful clusters from survey responses."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Service lines bridge the gaps between product lines through information flows to provide the right knowledge at the right time."
Designing Systems at Scale
November 7, 2018
"A lot of developers are way too confident they write perfect code; testing bug fixes often reveals hidden issues."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
