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
"Screen reader users scored significantly lower in usability tests, reflecting the most effort in interpreting content."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"You don’t want so much governance that people can’t be creative, but you need just enough to help their process."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"I spent too much time trying to change company culture and should have focused more on just getting things done."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Leadership doesn’t only mean managing; it can be mentoring, product leadership, or technical influence."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The trusted partnership between the chief of staff and the executive is critically important."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Controls like insurance qualifiers and legal agreements were necessary guardrails for this new way of working."
Amy EvansHow to Create Change
September 25, 2024
"Teleportation lets us move throughout the organization by building tools that gather disparate data for real-time decision making."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"Beliefs are habits of action; they are the rules that guide how we decide to act."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"What if the atomic unit of research wasn’t the reports, but it was the insight within those reports?"
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
