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
"No tracking is perfect because numbers tell you what likely happened, but not why it happened."
Erin WeigelUX Lessons from running more than 1,200 A/B Tests
July 10, 2024
"New ideas and changes to business trajectories rank pretty far down at only 18% of business leaders seeing it as a value of design."
Mike OrenWhy Pharmaceutical's Research Model Should Replace Design Thinking
March 28, 2023
"Understanding how assistive technology evolves is crucial because it foretells the future of interface design."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"We need secure defaults that protect users out of the box without them having to figure it out."
Heidi TrostWhen AI Becomes the User’s Point Person—and Point of Failure
August 7, 2025
"Design thinking at IBM is not just for designers; it’s how we want all 380,000 people to think about problems."
Adam CutlerPeople + Places + Practices = Outcomes
June 8, 2016
"Buttons should be sized 48 pixels and above to avoid fat finger errors for seniors."
Rittika BasuAge and Interfaces: Equipping Older Adults with Technological Tools
February 23, 2023
"Accessibility is a program, not just a single project; starting small and scaling efforts builds momentum."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"Every talk you hear today couldn’t get more personal to our community."
Bria AlexanderTheme Two Intro
October 3, 2023
"Regular face time, honest conversations, and working sessions help keep connection and momentum with new practitioners."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
