Discussion
Summary
In this session, Sam, Frederick, and Russ explore the complexities of enterprise design and product development. They stress beginning with personal hypotheses and proving them right or wrong, as Sam advocates starting with oneself. Society-wide culture change, rather than just design work, is central to successful enterprise transformation, noted especially by Sam and reinforced by others referencing the role of art, comedy, and social networks. Frederick highlights the challenge of delivering complex system improvements under tight time constraints, advising honesty and aligning project scope accordingly. The panel discusses the tension between radical and incremental innovation, with Sam emphasizing that most changes occur through networked connections rather than disruptive reinventions, though radical innovation requires culturally ready organizations, as noted with Honeywell's example. Russ explains how large audiences, like federal agencies, can adopt shared style guides while retaining customization for their unique needs. The importance of managing legacy systems alongside future-focused teams is highlighted, with the Atari example illustrating structural separation benefits. The panelists warn about technical and organizational debt as long-term obstacles. Sam underscores that culture trumps strategy and suggests embedding user experience improvements into an organization's social fabric, using regular communication channels to build momentum. Overall, the talk stresses that enterprise UX requires patience, cultural sensitivity, incremental progress, and a networked approach to change.
Key Insights
-
•
Start enterprise design projects with yourself to form testable hypotheses before engaging others.
-
•
Enterprise UX work is often more about culture change than just design or technology.
-
•
Transparency about time constraints and realistic scope is crucial when organizations demand rapid delivery.
-
•
Radical innovation in enterprise requires a culturally ready organization; otherwise, incremental improvements are more feasible.
-
•
Complex legacy systems require maintaining separate teams focused on current operations and future innovation to avoid stagnation.
-
•
Technical and organizational debt are major causes of prolonged pain during system migrations or upgrades.
-
•
Shared design standards can coexist with agency-level customization to balance familiarity and unique needs, as Russ explains with 18F.
-
•
Users can derive a sense of status or accomplishment from mastering complex legacy systems, making change socially challenging.
-
•
Embedding UX progress into an organization involves building strategic support and grassroots momentum through social networks and storytelling.
-
•
Measuring software like employee performance—reviewing and retiring underperforming systems—is essential to avoid wasted resources.
Notable Quotes
"Start with yourself. It’s a great place to get a hypothesis, and then prove yourself wrong or right."
"What we underestimate is that enterprise work is essentially culture change, not just design work."
"Do what you can, where you are, with what you have — that’s how you show you can deliver."
"Only work with companies willing to invest the time required; otherwise, deliver what you can and be honest about it."
"Radical innovation isn’t the main form of change; the main form is connections, like open APIs with massive downstream effects."
"If you create a separate team to work on the future, make sure they stay focused on the future, or you’ll never get out of the trap."
"The moment you spend more on maintaining legacy than creating the future, you’re probably doing the wrong thing."
"Users sometimes enjoy the complexity of old systems because mastery grants them elite social status internally."
"Culture trumps strategy. When culture derails your best plans, you need both strategic air cover and grassroots momentum."
"Building a distribution list of user-centered design success stories created a groundswell with 1,200 subscribers hungry for more."
Or choose a question:
More Videos
"AI is ambiguous at best because we’re fully in the realm of probabilistic rather than deterministic programming."
Sarah BarrettAI in Real Life: Using LLMs to Turbocharge Microsoft Learn
February 13, 2025
"Great practices help you do more with less and work smarter, not harder."
Michelle MorrisonPractice What You Preach
January 8, 2024
"Through the expertise of our speakers and your engagement, we forge the future of our industry."
Bria AlexanderTheme Two Intro
September 8, 2022
"You’re going to absolutely love using the Rosenbot, our chatbot, and hey, it’s free."
Louis RosenfeldHow to use the Rosenbot
March 16, 2026
"In synthesis sessions, it’s a pretty unstructured discussion focused on facts rather than interpretation."
Jesse ZolnaInviting the Whole Org to Come See For Yourself
March 30, 2020
"What the hell is a portal? That sounds like a solution without knowing the problem."
Jemma Ahmed Jon Fukuda Abby Covert Stefanie Hutka Louis RosenfeldTake Back those Words! Reclaiming and Reenergizing the Vocabulary of UX
August 21, 2026
"Executives don’t care about process or how we got there, they care about what happened and why it matters."
Rich MironovHow Can Product Managers and UXers Help Each Other (and Why are Product Folks so Annoying Sometimes)?
December 6, 2022
"We have to create human-centered organizations where people thrive by trust and recognition, grow with influence, and want to make a difference."
Christian BasonInnovating With People: Unleashing the Potential of Civic Design
December 8, 2021
"Alternative navigation users might use voice commands, head mice, or grid coordinates to access elements."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
June 9, 2021
