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
"Democratization is not research anarchy where anybody can talk to any customer for any reason with no oversight."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024
"Design systems are not just UI components but people and culture working together."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"When you have a success, measure time saved and reduction in bugs to build your internal business case for the system."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"We had to be creative measuring accessibility success because we cannot detect screen reader use or certain disabilities directly."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"There isn’t one single formula that works every time for a re-platforming journey."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"The System Usability Scale is a powerful benchmarking tool, and reducing it to two questions makes it easier to collect."
Mackenzie Cockram Sara Branco Cunha Ian FranklinIntegrating Qualitative and Quantitative Research from Discovery to Live
December 16, 2022
"You can change the time zone to whatever works for you on the conference site to avoid ambiguity."
Bria AlexanderOpening Remarks
June 9, 2021
"Many product teams have never come face to face with their revenue numbers before."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
"We need to relentlessly ask: technology is the answer, but what is the question?"
Dan HillDesigning for the infrastructures of everyday life
June 4, 2024