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
"You want to catch accessibility defects early through automated testing in your CI/CD pipeline, what we call shifting left."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"Feature bloat kills usability because it clouds the core value proposition."
Prayag Narula Hannah HudsonEmpowering Designers to do Good Research
March 11, 2022
"Inclusive research means building for diverse people, not just for ourselves or a narrow segment."
Janelle EstesUX Research Trends
January 28, 2021
"A single line of UI text might be a small ask but can have massive impact on customer understanding and experience."
Craig Brookes Andreas Huebner Morgan Quinn"Just Make it Look Good" and Other Ways We're Misunderstood
June 11, 2021
"High quality personal connections mean you can engage on a level playing field with serious professionals."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"The issue is not research ops being more organized researchers — the problems and scale are very different."
Kate TowseyThe State of ResearchOps: More Than Just Theory
June 20, 2019
"Psychological safety is the foundation; without it you get a culture of transaction and silence."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 9, 2022
"Designers contribute experimental patterns back to the design system early, making their work visible even before full validation."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"You have to look two or three steps ahead so you're not chasing what's right in front of you — avoid target fixation."
Tricia WangSCALE: Discussion
June 15, 2018
Latest Books All books
Dig deeper with the Rosenbot
How does healthcare UX balance creativity with strict regulatory compliance and safety requirements?
Where can UX researchers find reliable, up-to-date information and recommendations on research tool options?
How can organizations manage the noise created by non-expert researchers conducting user research?