Summary
In this talk, Dawn Russell, a design leader at Intuit, articulates the evolution of design systems from traditional pattern libraries to front-end component libraries, and ultimately to full-stack widgets that encapsulate both UI and backend functionality. She explains how Intuit leveraged widgets to unify disparate products within their ecosystem, enabling tasks like identity management and account recovery to scale efficiently across multiple teams and products. By focusing on reusable, code-based solutions, Intuit improved user experience, reduced support costs, and accelerated time to market. Dawn shares specific examples, such as the successful adoption of account recovery widgets by Accounting, TurboTax, and QuickBooks teams, highlighting measurable improvements. She stresses the importance of collaboration between designers and engineers—starting with user needs, not technology constraints—and emphasizes finding designers who are systems thinkers and domain experts. Finally, she provides pragmatic advice on adoption strategies, testing, and aligning with business goals, underscoring that design impact is only realized when it is implemented in production code.
Key Insights
-
•
Pattern libraries alone are insufficient as true design systems due to enforcement and interpretation challenges among large engineering teams.
-
•
Component libraries containing reusable UI code improve consistency by embedding designs directly into products.
-
•
Widgets represent the next evolution, combining UI and backend services to encapsulate complete user tasks for reuse across applications.
-
•
A single source of truth in code is essential for scalable, sustainable design systems in enterprise environments.
-
•
Intuit’s One and Two Identity project unified user identity across products, boosting product connectivity and user experience.
-
•
Account recovery widgets improved success rates by double digits and significantly reduced support costs at Intuit.
-
•
Collaborating closely with engineers, focusing on problem space not technical solutions, unleashes innovation and buy-in.
-
•
Not every UI challenge should become a widget; reuse potential and domain fit must be judged carefully.
-
•
Successful widget design requires designers who think systemically and dive deeply into specific functional domains.
-
•
Widgets complement, rather than replace, component libraries by consuming different style guides and enabling cohesive experiences.
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 true design system must have a single source of truth in code."
"Widgets encapsulate a user task with associated user interface and back end service functionality."
"Users immediately assumed that a single identity meant our products would work together naturally, even before we proposed product connectivity."
"By adopting our account recovery widget, QuickBooks saw a 13% increase in success rate overnight and a 52% reduction in support calls in one year."
"Designers’ medium is code; until your great design is in production code, your design is a figment of your imagination."
"Start with the problem, not the solution when partnering with engineers."
"Find out what motivates your engineering partners and tie your project goals to that motivation."
"Widgets are more than UI; they combine front end code, back end services, and analytics into a reusable package."
"It takes roughly one and a half times more investment to build reusable widgets, so we aim for a minimum of three adoptions to ensure ROI."
Or choose a question:
More Videos
"Qualitative data is data. It’s okay to be informal and human when designing complex systems."
Alison Rand Sarah BrooksScaling Impact with Service Design
March 25, 2021
"The biggest problem was to solve the engagement problem first with the sponsor, then the team, then external stakeholders."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"System diagrams are a nice level of abstraction over something that is really complicated underneath."
Sarah FlamionComplex Problem? Add Clarity by Combining Research and Systems Thinking
March 31, 2020
"Design ops is actually all about fragility. We do stability, security, planning, but can we add more experimentation and comfort with ambiguity?"
Silke Bochat5 Antifragile Strategies for a DesignOps 2.0
September 23, 2024
"The grownups’ table is where we talk about business problems and organizational complexity, not just sketching."
Uday Gajendar Lada Gorlenko Dave Malouf Louis Rosenfeld Dan Willis10 Years of Enterprise UX: Reflecting on the community and the practice
June 18, 2025
"I’m worried you aren’t up to it, frankly."
Dan WillisEnterprise Storytelling Sessions
June 8, 2017
"Scaling training happened by finding people in the community who could run sessions independently."
Kara KaneCommunities of Practice for Civic Design
April 7, 2022
"I believed we could do more — more for the company, customers, stakeholders, and ourselves if we had more agency."
Nalini KotamrajuResearch After UX
March 25, 2024
"Lauren Cantor works with companies to create new business strategies by tackling human-centered design."
Bria AlexanderOpening Remarks
October 1, 2021
