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
"As researchers, we stand on the shoulders of many before us; attribution helps us honor that lineage and curiosity."
Eduardo Ortiz Robin Beers Rachael Dietkus, LCSW Bruce Gillespie Jess Greco Marieke McCloskey Renee ReidDay 3 Theme Panel
March 13, 2025
"Intuition is the ability to see a connection so important that you could build a system out of it."
Richard BuchananCreativity and Principles in the Flourishing Enterprise
June 15, 2018
"We think with things; our brain is part of us but we extend our cognition into our environments and tools."
Jorge ArangoThe Best of Both Worlds: How to Integrate Paper and Digital Notes (1st of 3 seminars)
April 5, 2024
"With great power comes great responsibility; we shouldn’t abandon using motivation techniques, or others will use them poorly."
Cheryl PlatzEmbrace Your Fun Factor: Game Development Best Practices for Product Design
January 9, 2026
"Every small initiative can lead to significant change when multiplied across communities."
Ash BrownSilver Linings: What DesignOps Learned in the Shift to WFH
October 23, 2020
"Tech industry layoffs are basically an instance of social contagion—companies imitate what others are doing."
Angelos ArnisNavigating the Rapid Shifts in Tech's Turbulent Terrain
October 2, 2023
"If you don’t tell teams what to make, they need a product discovery process to decide what to build."
Jeff GothelfWho does what by how much?
November 20, 2025
"Apple solved the problem of making touchscreens accessible by inventing VoiceOver and providing rich APIs for developers."
Sam ProulxTo Boldly Go: The New Frontiers of Accessibility
September 9, 2022
"What does it mean to be a design ops person? That question matters and we must revisit it often."
Brendan JarvisIt was the Best of Times. It was the Worst of Times.
September 25, 2024
