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
"SAFe’s Agile Release Train is a long-lived team of agile teams that incrementally deliver solutions in sync like a train leaving the station."
Jack MoffettSAFe or Sorry? (Videoconference)
May 29, 2019
"When you look at the target too closely, you miss what’s around it; focus longer term to avoid target fixation."
Tricia WangSCALE: Discussion
June 15, 2018
"Great user experience is not a goal. You need specific, measurable goals like reducing training time by four."
Fredrik MathesonFirst-time users, longtime strategies: Why Parkinson’s Law is making you less effective at work – and how to design a fix.
June 8, 2016
"Our career competencies are not a checklist or promotion; it's not an expectation that directs get excelling scores across their level to advance."
Laine Riley ProkayHow DesignOps can Drive Inclusive Career Ladders for All
September 30, 2021
"We went from 100 to 200 people but still had the muscle of a 50 person company—it was chaos for product managers."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Slowing down with research can help us move faster overall."
Kristen Guth, Ph.D.Out of the FOG: A Non-traditional Research Approach to Alignment
March 28, 2023
"When organizations have diverse voices driving agendas at the top, earnings increase by 8% for every 10% increase in gender diversity."
Joi FreemanA New Vantage Point: Building a Pipeline for Multifaceted Research(ers)
March 30, 2020
"A product roadmap is a living document, it evolves with the market and users."
Victor UdoewaTheme One Intro
March 27, 2023
"Product managers and engineers are now recognizing the need to organize teams around customers and their experiences."
Peter MerholzCustomer-Centered Design Organizations
June 8, 2017