Summary
In this talk, the panelists explore how to identify critical inflection points in product development marked by growing complexity and user confusion, as highlighted by the consultant who often joins after chaos has emerged. Uday emphasizes the importance of aligning the highest representatives from marketing, engineering, and UX teams using the three-in-the-box model, supplemented by a wild card from orthogonal domains to spark innovation. Dave shares his traditional, people-first approach to understanding complex domains by deeply engaging with long-tenured subject matter experts. He details how his team manages their design system through enterprise agile practices, prioritizing impactful features and balancing stakeholder needs. Dave also addresses challenges like superficial adoption of design frameworks (IIDX washing) and stresses that their team invests more effort in facilitating workshops and teaching proper use of the system than just maintaining it, underscoring the synergy between conversations and prototyping tools for innovation.
Key Insights
-
•
Inflection points often become evident when users display confusion during usability testing, even with familiar tools.
-
•
Hiring an external consultant usually happens after an inflection point has caused chaos and complexity.
-
•
The three-in-the-box model—marketing, engineering, and UX leaders—is crucial for aligning diverse opinions around a common goal.
-
•
Introducing a ‘wild card’ from an orthogonal domain can spark innovative thinking in product teams.
-
•
Deep domain understanding comes from engaging with end users and long-tenured subject matter experts rather than relying solely on system mapping.
-
•
Design systems should be treated like living software products with backlogs, QA, and prioritized feature requests.
-
•
‘IIDX washing’ occurs when teams superficially use a design framework to claim UX improvements without real change, which requires both confrontation and letting user adoption reveal the truth.
-
•
More effort is often spent teaching people how to use design systems effectively than on maintaining the systems themselves.
-
•
Combining creative workshops with prototyping tools accelerates feedback cycles and innovation.
-
•
In large ecosystems with many developers, contextual understanding is key to selecting the appropriate design components or 'LEGOs'.
Notable Quotes
"One sign of evidence that you've passed an inflection point is when you hire me as a consultant."
"When I see users saying, oh my goodness, I didn’t know it did that, that’s a clear sign of too much complexity."
"The three-in-the-box model means having marketing, engineering, and UX leaders working collaboratively."
"I always like to try to introduce a wild card from a slightly orthogonal field to spark the thinking."
"I start by going and talking to the people, the end users, and the subject matter experts who have been working in the field for decades."
"We treat the design system like a software product with a backlog, QA, and a product owner prioritizing feature requests."
"IIDX washing is when people replicate button by button and checkbox by checkbox, then claim better UX."
"Usually, the users not adopting the product alerts the organization that deeper issues exist beyond UI."
"We’ve put much more effort into workshop facilitation and teaching how to use the space effectively than on the design system itself."
"Creative conversations combined with material for quick prototyping let you get fast feedback on messy whiteboard ideas."
Or choose a question:
More Videos
"Many companies view design operations as a nice to have, rather than essential, making these roles prime targets in layoffs."
Angelos ArnisNavigating the Rapid Shifts in Tech's Turbulent Terrain
October 2, 2023
"It takes an experienced researcher to be able to wrangle AI prompts to have any chance of getting good work."
Dr. Jamika D. Burge Nick Fine Alexandra Jayeun Lee Greg Nudelman Bo WangHow UX researchers can partner with (and not be replaced by) AI [Advancing Research Community Workshop Series]
August 31, 2023
"Before, we never really looked holistically at decades of UX data—now we use it to be proactive and avoid duplicative studies."
Kristin WisnewskiMeasuring What Matters
October 23, 2019
"Activating insights multiple times can be necessary before teams truly internalize and act on them."
Jake BurghardtStop wasting research: Create new value with insight summaries
July 9, 2025
"It’s better to err on the side of kindness and emotional support toward colleagues who might be struggling."
Louis RosenfeldWelcome / Housekeeping
June 7, 2023
"Consistency is so important that sometimes even consistency in failure works if it means I only have to learn the workaround once."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
"You don’t think of raising a child or teaching a student as solving a problem, it’s an ongoing process—and so is design today."
Hugh DubberlyProblems with Problems: Reconsidering the Frame of Designing as Problem-Solving
June 19, 2019
"Co-creating operating models with our teams helps us remain resilient even when things get a little hairy and squirrely."
Bria AlexanderTheme 1 Intro
September 23, 2024
"The code starts to follow the outcomes and might even start to write itself at some level."
Greg PetroffSoftware as Material—A Redux
June 6, 2023
